From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Sheng Yang <sheng@linux.intel.com>,
kvm@vger.kernel.org, Gleb Natapov <gleb@redhat.com>
Subject: Re: Make QEmu HPET disabled by default for KVM?
Date: Thu, 11 Mar 2010 16:08:07 -0300 [thread overview]
Message-ID: <20100311190807.GD17264@amt.cnet> (raw)
In-Reply-To: <4B98A294.7010104@redhat.com>
On Thu, Mar 11, 2010 at 09:58:12AM +0200, Avi Kivity wrote:
> On 03/11/2010 09:52 AM, Sheng Yang wrote:
> >I think we have already suffered enough timer issues due to this(e.g. I can't
> >boot up well on 2.6.18 kernel)...
>
> 2.6.18 as guest or as host?
>
> >I have kept --no-hpet in my setup for
> >months...
>
> Any details about the problems? HPET is important to some guests.
As Gleb mentioned in the other thread, reinjection will introduce
another set of problems.
Ideally all this timer related problems should be fixed by correlating
timer interrupts and time source reads.
Since one already has to use special timer parameters (-rtc-td-hack,
-no-kvm-pit-reinjection), using -no-hpet for problematic Linux
guests seems fine?
next prev parent reply other threads:[~2010-03-11 19:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 7:52 Make QEmu HPET disabled by default for KVM? Sheng Yang
2010-03-11 7:58 ` Avi Kivity
2010-03-11 8:23 ` Sheng Yang
2010-03-11 8:28 ` Avi Kivity
2010-03-11 8:31 ` Gleb Natapov
2010-03-11 8:36 ` Avi Kivity
2010-03-11 8:38 ` Sheng Yang
2010-03-11 8:42 ` Gleb Natapov
2010-03-11 8:46 ` Avi Kivity
2010-03-11 10:23 ` Gleb Natapov
2010-03-11 11:56 ` Avi Kivity
2010-03-11 11:56 ` Avi Kivity
2010-03-11 19:08 ` Marcelo Tosatti [this message]
2010-03-14 7:05 ` Avi Kivity
2010-03-14 7:10 ` Gleb Natapov
2010-03-14 10:23 ` Dor Laor
2010-03-14 10:27 ` Avi Kivity
2010-03-14 12:51 ` Dor Laor
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=20100311190807.GD17264@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=sheng@linux.intel.com \
/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