Hi,
[ ... back online now ... ]
/var/tmp/portage/app-emulation/qemu-kvm-0.14.0/work/qemu-kvm-0.14.0/qemu-kvm.c:1724:
kvm_mutex_unlock: Assertion `!cpu_single_env' failed.
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
On 2011-04-26 10:53, Gerd Hoffmann wrote:
Hi,
[ ... back online now ... ]
/var/tmp/portage/app-emulation/qemu-kvm-0.14.0/work/qemu-kvm-0.14.0/qemu-kvm.c:1724:
kvm_mutex_unlock: Assertion `!cpu_single_env' failed.
That's a spice bug. In fact, there are a lot of
On Tue, Apr 26, 2011 at 10:53:04AM +0200, Gerd Hoffmann wrote:
Hi,
[ ... back online now ... ]
/var/tmp/portage/app-emulation/qemu-kvm-0.14.0/work/qemu-kvm-0.14.0/qemu-kvm.c:1724:
kvm_mutex_unlock: Assertion `!cpu_single_env' failed.
That's a spice bug. In fact, there are a lot of
On 04/26/11 11:06, Jan Kiszka wrote:
On 2011-04-26 10:53, Gerd Hoffmann wrote:
Two general issues with dropping the global mutex like this:
- The caller of mutex_unlock is responsible for maintaining
cpu_single_env across the unlocked phase (that's related to the
abort above).
