From: Bug Watch Updater <899961@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 899961] Re: qemu/kvm locks up when run 32bit userspace with 64bit kernel
Date: Tue, 12 Jun 2012 22:40:36 -0000 [thread overview]
Message-ID: <20120612224038.23511.75130.launchpad@loganberry.canonical.com> (raw)
In-Reply-To: 20111204161619.13512.72277.malonedeb@soybean.canonical.com
** 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
Status in QEMU:
New
Status in “qemu-kvm” package in Debian:
Fix Released
Bug description:
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 - so far,
only (32bit) windows 7 guest shows it, but does that quite reliable:
first boot of an old guest with new qemu-kvm, windows finds a new CPU
and suggests rebooting - hit "Reboot" and in a few seconds it will be
locked up (including the monitor), with no CPU usage whatsoever.
Killable only with -9.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/899961/+subscriptions
next prev parent reply other threads:[~2012-06-12 22:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 16:16 [Qemu-devel] [Bug 899961] [NEW] qemu/kvm locks up when run 32bit userspace with 64bit kernel Michael Tokarev
2011-12-04 17:45 ` [Qemu-devel] [Bug 899961] " Michael Tokarev
2011-12-06 12:36 ` Avi Kivity
2011-12-04 18:09 ` Michael Tokarev
2011-12-06 11:54 ` Michael Tokarev
2011-12-16 9:08 ` Michael Tokarev
2011-12-18 15:26 ` Bug Watch Updater
2012-03-15 19:29 ` Michael Tokarev
2012-03-16 15:31 ` Michael Tokarev
2012-03-16 15:34 ` Michael Tokarev
2012-06-12 22:40 ` Bug Watch Updater [this message]
2016-11-09 10:58 ` Thomas Huth
2017-09-13 7:40 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120612224038.23511.75130.launchpad@loganberry.canonical.com \
--to=899961@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).