From: Avi Kivity <avi@redhat.com>
To: Peter Lieven <pl@dlh.net>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: disable clocksource=kvm-clock
Date: Tue, 01 Jun 2010 16:17:46 +0300 [thread overview]
Message-ID: <4C05087A.9090803@redhat.com> (raw)
In-Reply-To: <4C050743.3030603@dlh.net>
On 06/01/2010 04:12 PM, Peter Lieven wrote:
> hi,
>
> is it possible to avoid detection of clocksource=kvm_clock in a linux
> guest by
> patching the qemu-kvm binary?
> i would like to be able to avoid a guest detecting kvm-clock until bug
> #584516
> is fixed without modifying all guest systems and reverting that later.
>
Newer qemu-kvm's will have this feature (using -cpu ...,-kvmclock).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-06-01 13:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 13:12 [Qemu-devel] disable clocksource=kvm-clock Peter Lieven
2010-06-01 13:17 ` Avi Kivity [this message]
2010-06-01 13:57 ` [Qemu-devel] " Peter Lieven
2010-06-01 14:01 ` Avi Kivity
2010-06-01 14:06 ` Peter Lieven
2010-06-01 14:10 ` Avi Kivity
2010-06-01 14:17 ` Peter Lieven
2010-06-02 9:58 ` Peter Lieven
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=4C05087A.9090803@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pl@dlh.net \
--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).