[Qemu-devel] Timing/Clock problem with a Windows Host

[Qemu-devel] Timing/Clock problem with a Windows Host

[vdr]

[-- Attachment #1: Type: text/plain, Size: 241 bytes --]

Hi List,
I am working with a Linux client ( kernel 2.6.12 ) on a Win2K QEMU Host.
On the client the clock is "crawling" with factor 0.1 (it takes about 10 seconds for a "sleep 1"). Any hints how to correct this behaviour ?
Bye
Helmut

Re: [Qemu-devel] Timing/Clock problem with a Windows Host

[Andreas Mohr]

Hi,

On Thu, Aug 25, 2005 at 09:50:16AM +0200, vdr@helmutauer.de wrote:
> Hi List,
> I am working with a Linux client ( kernel 2.6.12 ) on a Win2K QEMU Host.
> On the client the clock is "crawling" with factor 0.1 (it takes about 10 seconds for a "sleep 1"). Any hints how to correct this behaviour ?

Could be APIC: try "noapic" boot parameter. Also try the troubleshooting
mentioned in various Linux dynticks discussions, e.g. the CK kernel list.

Toggling ACPI/APM use ("acpi=on/off", "apm=on/off"?) on boot might also help.

Time factor 10 sounds familiar to me, from recent discussions somewhere.

A modern PC has various timer sources (PIT, ACPI timers, CPU timers, ...),
so you need to make sure to experiment with Linux using different ones,
in the kernel configuration.

Andreas Mohr

Re: [Qemu-devel] Timing/Clock problem with a Windows Host

[Stefan Kisdaroczi]

[-- Attachment #1: Type: text/plain, Size: 942 bytes --]

Hi,

AFAIK, the linux clocktick changed from linux 2.4 to 2.6 from 100hz to 1khz, but im not sure.
However, there is a patch[2] on a japanese site[1], which worked for me for a other OS where i had the same problem.
You have to start qemu with the option "-hitimer" after you patched and built it.

[1] http://www.h7.dion.ne.jp/~qemu-win/
[2] http://www.h7.dion.ne.jp/~qemu-win/download/qemu-200412xx-w32pit1ms-test4.patch

bye kisda

vdr@helmutauer.de wrote:
> Hi List,
> I am working with a Linux client ( kernel 2.6.12 ) on a Win2K QEMU Host.
> On the client the clock is "crawling" with factor 0.1 (it takes about 10 seconds for a "sleep 1"). Any hints how to correct this behaviour ?
> Bye
> Helmut
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]

Re: [Qemu-devel] Timing/Clock problem with a Windows Host

[vdr]

[-- Attachment #1: Type: text/plain, Size: 732 bytes --]

> Hi,
> 
> AFAIK, the linux clocktick changed from linux 2.4 to 2.6 from 100hz to 1khz, but im not sure.
> However, there is a patch[2] on a japanese site[1], which worked for me for a other OS where i had the same problem.
> You have to start qemu with the option "-hitimer" after you patched and built it.
> 
> [1] http://www.h7.dion.ne.jp/~qemu-win/
> [2] http://www.h7.dion.ne.jp/~qemu-win/download/qemu-200412xx-w32pit1ms-test4.patch
> 
> bye kisda
> 
>

Thanks that did the trick. Unfortunately that causes a cpu load of 99 percent, so it's not really useful. I also tried some other kernel parameters like noapic or acpi but without sussess. It looks like the BIOS is not able to deal with ACPI.

ByeHelmut

Re: [Qemu-devel] Timing/Clock problem with a Windows Host

[Adrian Smarzewski]

Stefan Kisdaroczi wrote:
> AFAIK, the linux clocktick changed from linux 2.4 to 2.6 from 100hz to 1khz, but im not sure.

Maybe that's why my winxp host timer goes much faster than original?
even taskbar-clock time is incorrect.
how can I fix it? I'm using -localtime option.

-- 
Pozdrowienia,
Adrian Smarzewski