qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Problem with speed
Date: Tue, 10 Aug 2004 09:14:56 +1200	[thread overview]
Message-ID: <1092086096.2772.5.camel@unixadmindazfc2.chh.co.nz> (raw)
In-Reply-To: <41179539.3070302@student.tue.nl>

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

Hi Marjin,

FWIW I also run into the same sorts of problems on Fedora Core 2 host
with 2.6.7 kernel and the latest qemu-snapshots.  With a Windows
NT-based guest (like win2k3) the too-fast system clock causes problems
with services not starting properly at boot-time, because they time out
before having a chance to execute correctly.  I thought about using NTP
to solve this problem, but it just isn't fine-grained enough to solve
things nicely, and moreover it doesn't start early enough in the boot
process to solve my problem with other services failing.

So, no solutions from me, but rest assured it's not something inherently
wrong in your configuration that is unique to you :)

Any qemu-devs care to shed light on this?  It doesn't seem to be tied to
/proc/sys/dev/rtc/max-user-freq at all, unfortunately; I have set it for
both 32 and 10240 without any seeming change in the guest OS clock's
behaviour...


D


On Tue, 2004-08-10 at 03:16, Marijn Kruisselbrink wrote:

> I've installed Win98 inside qemu 0.6.0. Almost everything works fine, but the clock is running way too fast, causing network-packets to time-out before they are even send...
> My host OS is SuSE 9.1 with a 2.6.4 kernel. With linux as guest OS everything seems to work fine.
> Any ideas what i might be doing wrong?
> 
> Marijn Kruisselbrink




Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>

[-- Attachment #2: Type: text/html, Size: 1922 bytes --]

      reply	other threads:[~2004-08-09 21:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 15:16 [Qemu-devel] Problem with speed Marijn Kruisselbrink
2004-08-09 21:14 ` Darryl Dixon [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=1092086096.2772.5.camel@unixadmindazfc2.chh.co.nz \
    --to=esrever_otua@pythonhacker.is-a-geek.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).