[Qemu-devel] [Bug 688085] Re: Guest kernel hang during boot when KVM is active on i386 host - Zhiyuan-lv

From: Zhiyuan-lv <688085@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 688085] Re: Guest kernel hang during boot when KVM is active on i386 host
Date: Thu, 27 Jan 2011 06:10:49 -0000	[thread overview]
Message-ID: <20110127061049.27301.31114.malone@wampee.canonical.com> (raw)
In-Reply-To: 20101209150919.20263.50551.malonedeb@wampee.canonical.com

I verified the fix on kernel 2.6.35. After rebuilding kernel with the
patch, I could boot MeeGo image with qemu-kvm successfully. Can I know
when the kernel update will be available for Ubuntu 10.10? 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 “kvm” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Fix Committed
Status in “qemu” package in Ubuntu:
  Invalid
Status in “qemu-kvm” package in Ubuntu:
  Invalid
Status in “kvm” source package in Maverick:
  New
Status in “linux” source package in Maverick:
  New
Status in “qemu” source package in Maverick:
  New
Status in “qemu-kvm” 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/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.