Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"
On Thu, Jun 06, 2013 at 09:42:40AM +0300, Gleb Natapov wrote:
> On Wed, Jun 05, 2013 at 02:51:19PM +0200, Stefan Pietsch wrote:
> > On 05.06.2013 14:10, Gleb Natapov wrote:
> > > On Wed, Jun 05, 2013 at 01:57:25PM +0200, Stefan Pietsch wrote:
> > >> On 19.05.2013 14:32, Gleb Natapov wrote:
> > >>> On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote:
> > >>>> Dear KVM maintainers, it appears that there is a gap in x86 emulation,
> > >>>> at least on a 32-bit host. Stefan found this when running GRML, a live
> > >>>> distribution which can be downloaded from:
> > >>>> <http://download.grml.org/grml32-full_2013.02.iso>. His original
> > >>>> reported is at <http://bugs.debian.org/707257>.
> > >>>>
> > >>> Can you verify with latest linux.git HEAD? It works for me there on
> > >>> 64bit. There were a lot of problems fixed in this area in 3.9/3.10 time frame,
> > >>> so it would be helpful if you'll test 32bit before I install one myself.
> > >>
> > >>
> > >> Kernel version 3.9.4-1 (linux-image-3.9-1-686-pae) made things worse.
> > >>
> > >> The virtual machine tries to boot the kernel, but stops after a few
> > >> seconds and the kern.log shows:
> > > At what point does it stop?
> >
> >
> > The machine stops at:
> >
> > Performance Events: Broken PMU hardware detected, using software events
> > only.
> > Failed to access perfctr msr (MSR c1 is 0)
> > Enabling APIC mode: Flat. Using 1 I/O APICs
> Timer initialization is what comes next.
>
> I tried 32bit kernel compiled from kvm.git "next" (3.10.0-rc2+) branch and upstream
> qemu and I cannot reproduce the problem. The guest boots fine.
>
Actually the branch I tested is "master" not "next", but this should not
make a difference.
--
Gleb.
Reply to: