From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=46057 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PaVYr-0000ci-G0 for qemu-devel@nongnu.org; Wed, 05 Jan 2011 10:46:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PaVYp-0008Lg-Qz for qemu-devel@nongnu.org; Wed, 05 Jan 2011 10:46:05 -0500 Received: from adelie.canonical.com ([91.189.90.139]:43430) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PaVYp-0008LQ-Dl for qemu-devel@nongnu.org; Wed, 05 Jan 2011 10:46:03 -0500 Received: from loganberry.canonical.com ([91.189.90.37]) by adelie.canonical.com with esmtp (Exim 4.71 #1 (Debian)) id 1PaVYn-0006hE-3P for ; Wed, 05 Jan 2011 15:46:01 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 924DF2E8190 for ; Wed, 5 Jan 2011 15:45:55 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Wed, 05 Jan 2011 15:40:28 -0000 From: Serge Hallyn <688085@bugs.launchpad.net> Sender: bounces@canonical.com References: <20101209150919.20263.50551.malonedeb@wampee.canonical.com> Message-Id: <20110105154029.1084.78210.launchpad@wampee.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 688085] Re: Guest kernel hang during boot when KVM is active on i386 host Reply-To: Bug 688085 <688085@bugs.launchpad.net> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ** Description changed: Binary package hint: qemu = Guest kernel hang during boot when KVM is active on i386 host = - See the patch. = + See the patch. http://www.spinics.net/lists/kvm/msg40800.html = How to reproduce: 1. install Maversick x86 (not amd64) 2. ensure you have kvm support in processor 3. kvm -kernel /boot/initrd.img-2.6.35-24-generic-pae 4. kvm -no-kvm -kernel /boot/initrd.img-2.6.35-24-generic-pae works OK. + = + SRU Justification: + Impact: Users cannot boot KVM guests on i386 hosts + 2. How bug addressed: The upstream commit at http://www.spinics.net/list= s/kvm/msg40800.html fixed it + 3. Patch: A kernel patch is attached to this bug. + 4. Reproduce: boot an i386 kernel on a kvm-capable host. Try to boot a k= vm guest. + 5. Regression potential: since this is cherrypicking a commit from a futu= re upstream which had already been changed, regression is possible. Howeve= r if there is a regression, it should only affect users of KVM on i386 host= s, which currently fail 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/688085 Title: Guest kernel hang during boot when KVM is active on i386 host Status in meego project: Unknown Status in QEMU: Fix Released Status in qemu-kvm: Fix Released Status in =E2=80=9Ckvm=E2=80=9D package in Ubuntu: Invalid Status in =E2=80=9Clinux=E2=80=9D package in Ubuntu: In Progress Status in =E2=80=9Cqemu=E2=80=9D package in Ubuntu: Invalid Status in =E2=80=9Cqemu-kvm=E2=80=9D package in Ubuntu: Invalid Bug description: Binary package hint: qemu Guest kernel hang during boot when KVM is active on i386 host See the patch. http://www.spinics.net/lists/kvm/msg40800.html How to reproduce: 1. install Maversick x86 (not amd64) 2. ensure you have kvm support in processor 3. kvm -kernel /boot/initrd.img-2.6.35-24-generic-pae 4. kvm -no-kvm -kernel /boot/initrd.img-2.6.35-24-generic-pae works OK. SRU Justification: Impact: Users cannot boot KVM guests on i386 hosts 2. How bug addressed: The upstream commit at http://www.spinics.net/lists/= kvm/msg40800.html fixed it 3. Patch: A kernel patch is attached to this bug. 4. Reproduce: boot an i386 kernel on a kvm-capable host. Try to boot a kvm= guest. 5. Regression potential: since this is cherrypicking a commit from a future= upstream which had already been changed, regression is possible. However = if there is a regression, it should only affect users of KVM on i386 hosts,= which currently fail anyway.