Since the debian bug has been marked as fixed and there wasn't any
response to the question in my last comment, I assume this has been
fixed in upstream QEMU, too. So closing this ticket accordingly...
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug
The bug in Debian has been marked as "Fix released", so I assume this
has been fixed in upstream QEMU, too? Or is there still anything left to
do here?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
** Changed in: qemu-kvm (Debian)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/899961
Title:
qemu/kvm locks up when run 32bit userspace with 64bit kernel
Forgot to mention: tcg appears to be unaffected - so far anyway.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/899961
Title:
qemu/kvm locks up when run 32bit userspace with 64bit kernel
Status in
After some more digging I found out that qemu also has this very issue,
but it happens a bit differently. In particular, this very same winXP
test guest freezes in upstream qemu with -enable-kvm on _shutdown_, not
on restart. In qemu-kvm it happens on restart but not on shutdown.
And bisecting
I tried bisecting it today, again. I think you did mean
145e11e840500e04a4d0a624918bb17596be19e9 as the M point (the large
merge), not b195043003d90ea4027ea01cc7a6c974ac915108 (which is the first
commit in that merge) ;) Actually I did the same already, just didn't
post to the bugreport. But
** Changed in: qemu-kvm (Debian)
Status: Unknown = Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/899961
Title:
qemu/kvm locks up when run 32bit userspace with 64bit kernel
Status
** Bug watch added: Debian Bug tracker #652329
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652329
** Also affects: qemu-kvm (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652329
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Description changed:
- Applies to both qemu and qemu-kvm 1.0, but only when kernel is 64bit and
+ Only applies to qemu-kvm 1.0, and only when kernel is 64bit and
userspace is 32bit, on x86. Did not happen with previous released
versions, such as 0.15. Not all guests triggers this issue -
On 12/04/2011 07:45 PM, Michael Tokarev wrote:
Actually after trying to do lots of experiments and finally a git
bisection, it turned out that the issue only affects qemu-kvm, not
upstream qemu. Bisection between qemu-kvm 0.15.0 and 1.0 lead to this
commit:
commit
Actually after trying to do lots of experiments and finally a git
bisection, it turned out that the issue only affects qemu-kvm, not
upstream qemu. Bisection between qemu-kvm 0.15.0 and 1.0 lead to this
commit:
commit 145e11e840500e04a4d0a624918bb17596be19e9
Merge: ce967f6 b195043
Author: Avi
And some more info. Debugging with gdb shows this:
(gdb) info threads
Id Target Id Frame
2Thread 0xf6d4eb70 (LWP 28697) qemu-system-x86 0xf7711425 in
__kernel_vsyscall ()
* 1Thread 0xf6f50700 (LWP 28694) qemu-system-x86 0xf7711425 in
__kernel_vsyscall ()
(gdb) bt
#0
12 matches
Mail list logo
