[Top][All Lists]

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

[Qemu-devel] qemu svn r5281 on FreeBSD - slow usb, vmwarevga, screen upd

From: Juergen Lock
Subject: [Qemu-devel] qemu svn r5281 on FreeBSD - slow usb, vmwarevga, screen updates...
Date: Sun, 21 Sep 2008 22:40:25 +0200
User-agent: Mutt/1.5.17 (2007-11-01)


 I've been playing with qemu svn on FreeBSD again (new experimental
emulators/qemu-devel port update here:
), and want to note a few things:

 1. usb is still absymally slow, especially emulated disks (disk:imagefile)
and nics, both read/receive at about 30 KBytes/s here.  Is anyone working
on this?  I also got a report that its slow on Linux hosts too, so this
problem doesn't appear to be FreeBSD specific...

 2. -vmwarevga _seems_ to be less broken when run with 16 bpp, only 24
bpp seems to get the fifo errors that I posted about last time:
(maybe also the patch I posted there is only needed when running the guest
with 24 bpp.)  vmmouse seems to be broken too tho, the guest acts as if
the mouse is stuck in the bottom right corner.  (maybe I didn't actually
test this the last time, or it has something to do with the newer guest
that I used this time which also has a newer xorg version among other
announcement including mirror list is here:
)  The guest xorg crashes with -kernel-kqemu also still happen.

 Oh and that guest tries to use vmmouse by default if run with
-vmwarevga, to disable it you can boot to runlevel 3 (add a 3 to the
grub line), su, change vmmouse to mouse in /etc/X11/xorg.conf, then do
init 5 to start X.

 3. The screen update problem I mentioned seems to be intermittent,
sometimes I see it, sometimes not, and its also possible it only affects
the emulated vga console (vga=0 with linux guests.)  Sometimes when I see
it there are also partwise screen updates, like I see only some of the
lines scrolling.  Whenever it happens, moving the mouse over another
window fixes it for a few seconds, until it happens again.  Oh and the
guest keeps running all the time, only the screen doesn't update correctly
when it happens...

 4. There's one good news: completion in the monitor is back to working
order! :)  (I suspect because of the qemu_strdup fix.)


reply via email to

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