From: Paolo Bonzini <pbonzini@redhat.com>
To: Matt Lupfer <mlupfer@ddn.com>, Alex Bligh <alex@alex.org.uk>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] CentOS 5.x intermittently fails to boot on QEMU 1.7.0
Date: Sat, 22 Feb 2014 09:59:58 +0100 [thread overview]
Message-ID: <5308670E.7050301@redhat.com> (raw)
In-Reply-To: <5307F614.3060204@ddn.com>
Il 22/02/2014 01:57, Matt Lupfer ha scritto:
> Thanks for the response. The hpet_timer() callback calls timer_mod()
> every 1 ms. That timerlist has no notify callback so it in turn calls
> qemu_notify_event().
>
> The guest kernel is only enabling the HPET timer and looking for
> timer interrupts.
FWIW, the HPET implementation is not very high precision (it has a large
latency because it is implemented in userspace) and it is also very
slow. I suggest running always with -no-hpet.
Paolo
prev parent reply other threads:[~2014-02-22 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 4:34 [Qemu-devel] CentOS 5.x intermittently fails to boot on QEMU 1.7.0 Matt Lupfer
2014-02-21 6:30 ` Paolo Bonzini
2014-02-21 13:27 ` Alex Bligh
2014-02-22 0:57 ` Matt Lupfer
2014-02-22 8:55 ` Alex Bligh
2014-02-22 8:59 ` Paolo Bonzini [this message]
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=5308670E.7050301@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex@alex.org.uk \
--cc=mlupfer@ddn.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).