From: Zachary Amsden <zamsden@redhat.com>
To: "Thomas Løcke" <thomas.granvej6@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: qemu-kvm 0.12.3, Slackware 13 host and Windows XP guest - time drift a lot
Date: Wed, 17 Mar 2010 12:45:10 -1000 [thread overview]
Message-ID: <4BA15B76.2080203@redhat.com> (raw)
In-Reply-To: <1f0fa7ae1003171517hec6bf0fj1f9bdc17b2566290@mail.gmail.com>
On 03/17/2010 12:17 PM, Thomas Løcke wrote:
> On Wed, Mar 17, 2010 at 8:33 PM, Zachary Amsden<zamsden@redhat.com> wrote:
>
>> What's your host CPU load get up to. You only have a single core?
>>
> Dual core.
>
> If I only run a single Windows VM, the host load is pretty low. Sure
> it goes up a bit when for example copying a file, but it's nothing
> serious. It's not getting hammered in any way.
>
>
>> Including -rtc-td-hack ?
>>
> Yup, tried that as per suggested by one of the #kvm users. Didn't fix
> it. But come to think of it, I didn't change any of the other options.
> Should I have dropped -localtime and/or -tdf options? I will try again
> tomorrow.
>
-rtc localtime
is required for Windows to get the proper RTC time, and -tdf should have
no effect on Windows guests.
You might try
-rtc localtime,clock=host,driftfix=slew
>
>
>> As always, make sure you are running the latest and greatest modules, those
>> matter even more than the kernel, and check for any warning messages in
>> dmesg and qemu output.
>>
>
> But don't the latest kvm modules come with the kernel? So if I compile
> a new kernel, the kvm modules should be updated too, yes?
>
> I will try the latest qemu-kvm.
>
I use git://git.kernel.org/pub/scm/virt/kvm/kvm-kmod.git and track a 2.6
kernel branch directly so I always have latest module source regardless
of host kernel.
Zach
prev parent reply other threads:[~2010-03-17 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 19:22 qemu-kvm 0.12.3, Slackware 13 host and Windows XP guest - time drift a lot Thomas Løcke
2010-03-17 19:33 ` Zachary Amsden
2010-03-17 22:17 ` Thomas Løcke
2010-03-17 22:45 ` Zachary Amsden [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=4BA15B76.2080203@redhat.com \
--to=zamsden@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=thomas.granvej6@gmail.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