[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [fedora-virt] Guest kernel hanging at '...trying to set up timer as Virtual Wire IRQ...'



On Wed, 2009-05-13 at 10:20 +0100, Richard W.M. Jones wrote:
> On Wed, May 13, 2009 at 09:48:58AM +0100, Mark McLoughlin wrote:
> > On Tue, 2009-05-12 at 23:16 +0100, Richard W.M. Jones wrote:
> > > On Tue, May 12, 2009 at 10:48:41PM +0100, Daniel P. Berrange wrote:
> > > > On Tue, May 12, 2009 at 10:19:32PM +0100, Richard W.M. Jones wrote:
> > > > > 
> > > > > I've got the guest kernel hanging randomly at:
> > > > > 
> > > > >   ACPI: Core revision 20090320
> > > > >   ftrace: converting mcount calls to 0f 1f 44 00 00
> > > > >   ftrace: allocating 18780 entries in 37 pages
> > > > >   ..TIMER: vector=0x30 apic1=0 pin1=0 apic2=-1 pin2=-1
> > > > >   ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> > > > >   ...trying to set up timer (IRQ0) through the 8259A ...
> > > > >   ..... (found apic 0 pin 0) ...
> > > > >   ....... failed.
> > > > >   ...trying to set up timer as Virtual Wire IRQ...
> > > > > 
> > > > > This is the very latest on Rawhide.  Full packages, versions, etc in
> > > > > the build log here:
> > > > 
> > > > Last time I saw this error was due a KVM build problem causing it to 
> > > > use the wrong BIOS. ie it was using the plain QEMU bios, instead of the
> > > > KVM modified bios.
> > > 
> > > I've never had this error happening on my local machines.  However
> > > this situation is a bit confusing - this is running in Koji, where the
> > > kernel is RHEL 5.(?), I believe the whole thing is running in Xen, and
> > > the userspace is QEMU from Rawhide.
> > 
> > As Daniel says, I've seen this happen when /usr/share/qemu/bios.bin was
> > the stock bochs BIOS and not the KVM specific BIOS.
> > 
> > Sounds like the kvm-85 build recently pushed to devel/ is busted.
> 
> I installed that version of qemu-kvm and tested it, and it seems
> to be using:
> 
> /usr/share/qemu/bios.bin
> /usr/share/qemu/vgabios-cirrus.bin
> 
> which I'm guessing is the wrong one.  How does it choose the right
> BIOS to use? (assuming the -L flag is not set)

'readlink /usr/share/qemu/bios.bin' is more instructive; it points to
BIOS-bochs-kvm.

Glauber, does kvm-85 require some updates to BIOS-bochs-kvm?

> Also does it make a difference if qemu-kvm falls back to software
> emulation mode, which is likely to be the case for my Koji build.

That shouldn't be a problem.

Cheers,
Mark.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]