From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=57380 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PjRMA-0001Oi-TX for qemu-devel@nongnu.org; Sun, 30 Jan 2011 02:05:55 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PjRM6-0004Tp-68 for qemu-devel@nongnu.org; Sun, 30 Jan 2011 02:05:54 -0500 Received: from adelie.canonical.com ([91.189.90.139]:54975) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PjRM5-0004Tl-Sz for qemu-devel@nongnu.org; Sun, 30 Jan 2011 02:05:50 -0500 Received: from loganberry.canonical.com ([91.189.90.37]) by adelie.canonical.com with esmtp (Exim 4.71 #1 (Debian)) id 1PjRM4-0006Gn-I0 for ; Sun, 30 Jan 2011 07:05:48 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 6602F2E80CD for ; Sun, 30 Jan 2011 07:05:48 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Wed, 26 Jan 2011 22:19:19 -0000 From: Zhiyuan-lv <688085@bugs.launchpad.net> Sender: bounces@canonical.com References: <20101209150919.20263.50551.malonedeb@wampee.canonical.com> Message-Id: <20110130070108.29048.34926.launchpad@loganberry.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 688085] 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 Ubuntu 10.10 will update kernel to contain a back ported kvm fix, which probably in the next version after 2.6.35.24. Meanwhile, it is possible to manually build newer version of kvm to have the problem fixed. The tar ball of kvm source code could be downloaded from below: http://sourceforge.net/projects/kvm/files/kvm-kmod/2.6.37/ I tried the package on my Ubuntu 10.10 (kernel 2.6.35.23) T61 laptop with Intel Core 2 due 32-bit CPU. Using the new kvm, I could boot up meego kernel successfully. Hope that could help. Thanks! -- = 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: In Progress 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: Fix Committed 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 Status in =E2=80=9Ckvm=E2=80=9D source package in Maverick: New Status in =E2=80=9Clinux=E2=80=9D source package in Maverick: New Status in =E2=80=9Cqemu=E2=80=9D source package in Maverick: New Status in =E2=80=9Cqemu-kvm=E2=80=9D source package in Maverick: New 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/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.