On Wed, Feb 13, 2008 at 06:07:36PM +0100, Koen Vermeer wrote:
> On Wed, 2008-02-13 at 17:55 +0200, Dan Kenigsberg wrote:
> > On Wed, Feb 13, 2008 at 02:00:38PM +0100, [EMAIL PROTECTED] wrote:
> > However, as Uri mentioned earlier, this is useful only with newer KVMs.
> > I assume that your host runs the kvm from 2.6.23 which is pretty old in
> > kvm timescale. Try downloading kvm-60, insmod it to your host and try
> > running your guest.
>
> OK, I installed both version 60 of both kvm and kvm-source (Debian
> Lenny), ran m-a a-i kvm and just to be sure I removed and reloaded the
> kvm and kvm-amd modules. modinfo kvm and modinfo kvm-amd shows that
> these are indeed version 60.
>
> I then restarted the guest (which is exactly the same as before) and I
> tried the 'sleep 10' test again. Same result: It takes about 17 or 18
> seconds for the prompt to return again.
>
> I assume that clocksource=tsc isn't useful as it is already using the
> tsc. So, what else can I try? Any command line parameter I can add to
> the kvm call? Kernel parameters in the guest? Update the guest OS to a
> newer kernel (2.6.22 to 2.6.24)? Update the host OS to a newer kernel
> (2.6.23 to 2.6.24)?
Frankly, I'm running out of ideas.
Are you using kvm-60 userspace, too?
You may also try adding -tdf -no-kvm-irqchip options to the command line of
qemu. If the guest is using the old-fashioned pit for some reason, it
should correct its time drift.
Regards,
Dan.
>
> Thanks for the help!
>
> Koen
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
