qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Brad Campbell <brad@wasp.net.au>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] /dev/rtc
Date: Fri, 28 Jul 2006 19:08:38 +0400	[thread overview]
Message-ID: <44CA2876.8030308@wasp.net.au> (raw)

G'day all,

Been playing with multiple vm's on linux and hacking around my suspend/resume dropped interrupt issues.

I just noticed the /dev/rtc interface appears to be very single use oriented. If I run multiple vm's
simultaneously on the same machine, the 1st one picks up the interrupt driven timer and the rest 
must revert to userspace based timers.

open("/dev/rtc", O_RDONLY|O_LARGEFILE)  = -1 EBUSY (Device or resource busy)

Not having investigated this much further as I'm testing on a fairly low powered device, but I 
wonder how this impacts server applications where we desire to run several qemu instances concurrently.

(I have already played with dropping the timer interrupt rate back from 1024 to 256 and it really 
does not appear to impact my linux guests, but it makes my windows guests audio unusable. Still 
experimenting with that)

Just fishing for comments really.. wondering about some form of shared interrupt timing device to 
allow multiple instances to run with full timer resolution or if it really even matters.

Brad
-- 
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams

                 reply	other threads:[~2006-07-28 15:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=44CA2876.8030308@wasp.net.au \
    --to=brad@wasp.net.au \
    --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).