Re: More about slow clock in guest OS
Mulyadi Santosa <mulyadi.santosa <at> gmail.com>
2008-02-01 02:41:52 GMT
On 1/31/08, Sergey Bychkov <sergb <at> unichrom.com> wrote:
> As I can see, this document anything about what to do if qemu hung :)
reading always helps in some degree :)
> After some investigations I can say that with the latest (2008/01/30) qemu
> from cvs, compiled with gcc-3.4 on linux x86_64 host, guest OS win2k3 works
> not too good.
So, in other words "it works but not so well". may I interpret it as a progress?
> With "-clock dynticks" clock in OS is very slow - and windows time server
> can't adjust.
Probably due to cost of Qemu timer rearming. And maybe Windows 2003
does certain dyntick by its own...thus enlarging the timer rearming
> With "-clock rtc" hung periodically - for up to 5 minutes, 300 seconds.
pffff... too much timers get expired? lock contention somewhere...anybody?
> could happen at bootstrap - when no OS, only BIOS. Then it resumes and works
> for some random period of time, then hangs again, and so on. This behaviour
> doesn't depend on guest OS, and was reproduced with Knoppix live CD. Note
> that host should be periodically busy executing something like torrent
Thus..maybe it's Qemu's fault...