When trying to start X (and it loads qxl driver) the kvm process just crashes.
qemu-kvm 0.14
startup line
/usr/bin/kvm -name spaceball,process=spaceball -m 1024 -kernel
/boot/bzImage-2.6.37.2-guest -append root=/dev/vda ro -smp 1 -netdev
type=tap,id=spaceball0,script=kvm-ifup-brloc,vhost=on
On 2011-02-26 12:43, xming wrote:
When trying to start X (and it loads qxl driver) the kvm process just crashes.
qemu-kvm 0.14
startup line
/usr/bin/kvm -name spaceball,process=spaceball -m 1024 -kernel
/boot/bzImage-2.6.37.2-guest -append root=/dev/vda ro -smp 1 -netdev
Oops forgot to send this to the list too, here we go
That's a spice bug. In fact, there are a lot of
qemu_mutex_lock/unlock_iothread in that subsystem. I bet at least a few
of them can cause even more subtle problems.
Just tried spice 0.7.3 (was using 0.6.x) and still the same, should I
file
I pulled the latest qemu-kvm code and configured it with disabled-kvm
and related options. Configuration finishes well, but the compilation
fails.
prasad@prasad-kvm:~/KVM/qemu-kvm$ ./configure --disable-kvm
--disable-kvm-device-assignment --disable-kvm-pit
...
...
During device assignment the memory pre-fetchable flag was discarded
as the IORESOURCE_PREFETCH was defined as 0x1000 when instead it
should have been 0x2000. Following small patch fixes the problem,
please apply.
Signed-off-by: Prasad Joshi prasadjoshi...@gmail.com
---
diff --git
Hi,
I understand that in order to improve performance by reducing vm
exits, kvm uses one shared page between kvm and guest. Now, guest can
map this page and access its fields using load, store instructions.
Then, it patches instructions with their paravirtualized versions
(inside
