From: Sheng Yang <sheng@linux.intel.com>
To: kvm@vger.kernel.org
Cc: Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: 2.6.27.5 guest boot failure using in-kernel PIT
Date: Fri, 21 Nov 2008 11:05:26 +0800 [thread overview]
Message-ID: <200811211105.26595.sheng@linux.intel.com> (raw)
In-Reply-To: <20081120220517.GB30825@blackpad>
On Friday 21 November 2008 06:05:17 Eduardo Habkost wrote:
> On Thu, Nov 20, 2008 at 12:22:53PM -0200, Eduardo Habkost wrote:
> > Hi,
> >
> > When using a kvm.git kernel as host, I am getting guest boot failures
> > when booting Fedora Rawhide kernel (2.6.27.5-117.fc10.x86_64). Guest
> > stops booting at:
> >
> > ENABLING IO-APIC IRQs
> > ..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...
> > ..... failed.
> > ...trying to set up timer as ExtINT IRQ...
>
> I've just found out this problem happens because the guest has HZ=1000
> and the host had HZ=250 and no CONFIG_HIGH_RES_TIMERS.
>
> With this setup, the host is not managing to inject enough timer
> interrupts during the mdelay() loop on timer_irq_works().
So, do we need to depend on CONFIG_HIGH_RES_TIMERS? I think most modern
machine should have this.
--
regards
Yang, Sheng
next prev parent reply other threads:[~2008-11-21 3:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 14:22 2.6.27.5 guest boot failure using in-kernel PIT Eduardo Habkost
2008-11-20 22:05 ` Eduardo Habkost
2008-11-21 3:05 ` Sheng Yang [this message]
2008-11-21 7:54 ` Jan Kiszka
2008-11-21 13:17 ` Eduardo Habkost
2008-11-21 15:41 ` Jan Kiszka
2008-11-21 16:39 ` Eduardo Habkost
2008-11-21 17:06 ` Eduardo Habkost
2008-11-24 17:02 ` hrtimer_forward() semantics when using non-high-res timers Eduardo Habkost
2008-11-21 17:10 ` 2.6.27.5 guest boot failure using in-kernel PIT Marcelo Tosatti
2008-11-24 14:33 ` Glauber Costa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200811211105.26595.sheng@linux.intel.com \
--to=sheng@linux.intel.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox