[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 1787505] Re: Solaris host: no network connection, mous

From: Michele Denber
Subject: [Qemu-devel] [Bug 1787505] Re: Solaris host: no network connection, mouse pointer mismatch
Date: Sat, 18 Aug 2018 17:22:37 -0000

Thank you very much.  The following invocation fixed the mouse problem
(mostly) and made the Ethernet device available to the guest:

./qemu-system-x86_64 -m 2047 -boot d  -usb -device usb-tablet -smp 3
-netdev user,id=n0 -device rtl8139,netdev=n0 -hda
/bkpool/qemuimages/XP.img -cdrom /bkpool/qemuimages/xp.iso

There is one minor problem with the mouse.  Without the "-usb" qemu
displays the guest cursor position with an arrow, and the host cursor
position with a four pixel-wide box, separated by a distance that varies
with position on the screen.  After adding "-usb", the guest cursor
correctly tracks the host mouse, but the little box remains displayed,
speared on the tip on the guest cursor arrow.

Also, while the guest now has a network device it still can't talk to
any destination.  Oddly, if I try to ftp to some server it says
"connected" but then nothing else.  Web pages all come back as
"unreachable" even when requested by IP rather than name.  Even pinging
the router fails (though the documentation states that ping won't work
anyway).  The guest shows packets beign sent, but none received.  I
tried various other options listed in the documentation without success,

# qemu-system-x86_64: Host doesn't belong to network
 ./qemu-system-x86_64 -m 2047 -boot d  -usb -device usb-tablet  -smp 3 -netdev 
user,id=n0,host=, \
> hostname=canadiceq,dns=,net= -device 
> rtl8139,netdev=n0 -hda  /bkpool/qemuimages/XP.img -cdrom 
> /bkpool/qemuimages/xp.iso &
# qemu-system-x86_64: Host doesn't belong to network

My best guess also didn't work:

./qemu-system-x86_64 -m 2047 -boot d  -usb -device usb-tablet  -smp 3 -netdev 
> net= -device rtl8139,netdev=n0 -hda  /bkpool/qemuimages/XP.img 
> -cdrom /bkpool/qemuimages/xp.iso &

That at least starts up, but no communication.

I guess I just don't understand what needs to be listed where in the
qemu invocation.  My guest TCP parameters are set up the same way as a
different working XP system.  I can't tell what I need to get the guest
to talk to the Internet.  I have a host IP (, guest IP
(, router IP (, and DNS IP (
What goes where?  Do I need to set up anything special on the Solaris
end?  I've read over the documenation but still can't figure it out.

"If you have access to a Linux box, I'd definitely recommend testing the
same setup there."

I do, but I only have one legit XP license.

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  Solaris host: no network connection, mouse pointer mismatch

Status in QEMU:

Bug description:
  This is probably a bit far afield but on a Solaris 10 SPARC host (Sun
  M3000) running a Windows XP guest like this:

  ./qemu-system-x86_64 -m 1024 -boot d  -smp 3 -net nic -net user -hda
  /bkpool/qemuimages/XP.img -cdrom /bkpool/qemuimages/xp.iso &

  the vnc server starts up and Windows boots normally.  However, there
  is no network connectivity.  There are no network devices visible in
  XP's Networking tab of Control Panel and a ping of the local router
  reports "unreachable".

  Also, the keyboard works fine but the guest mouse pointer is offset
  from the host mouse position by an amount that varies by screen
  position.  This makes it impossible to point to locations near the
  edge of the qemu window.  This seems to be a previously reported
  problem, but the suggested fix, " -device usb-tablet", prevents qemu
  from even starting:

  qemu-system-x86_64: -device usb-tablet: No 'usb-bus' bus found for
  device 'usb-tablet'

  The physical mouse is connected to the USB port of a Sun Ray 2fs
  controlling the M3000 via Sun Ray server.  I apologize if this is a
  configuration issue and not a bug but I don't know where else to
  report it and have been unable to find a solution in the

To manage notifications about this bug go to:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]