From: Brad Campbell <brad@wasp.net.au>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu Guest Tools
Date: Thu, 03 Mar 2005 08:24:12 +0400 [thread overview]
Message-ID: <4226916C.8050706@wasp.net.au> (raw)
In-Reply-To: <20050302143856.GA4688@jbrown.mylinuxbox.org>
Jim C. Brown wrote:
> On Wed, Mar 02, 2005 at 01:44:35PM +0100, Oliver Gerlich wrote:
>
>>Planned features are:
>>-Notification of guest when it is loaded with loadvm
>
>
> Why?
>
>
>>-Time synchronisation between host and guest (currently guest time is
>>wrong when loadvm is used)
>
>
> Technically this is a qemu bug and should be fixed in qemu.
>
> Of course, any way to set the time in qemu guest w/o having to patch qemu
> source is welcome.
I run an ntp client inside windows.
>
> I am against mouse grabbing myself. I just use the no-sdl-grab patch and deal
> with a desyncing guest mouse pointer (sometimes I can work around it by
> turning mouse acceleration off in the guest).
I was thinking about a little guest app to keep them in sync. This is how win4lin does it and it
works very well. It is dead easy to do under windows as mouse manipulation from userspace is a
doddle, don't know about linux though.
>>Copy/paste and time sync could be done by external programs (Joshua
>>mentioned mpcb; ntp, ...).
>
>
> I'm not sure if ntp would work for qemu guest. The way qemu works, guest changes
> to the RTC are overridden by qemu. Of course if the guest kept its own time
> independent of the hardware clock, that wouldn't be a problem.
It does. I use anachron for windows.
>
>>I've decided against some special i/o port or such because I don't know
>>anything about these things :) and because it would require a driver on
>>the guest side (is that correct?).
>
>
> Unfortuantly, yes. However, the magic instruction set would not. (You would
> probably need to reimplement a new one for each arch qemu supports/will be
> ported to though.)
>
This was my thought. Networking is not always available. A couple of IO ports would always be there.
Regards,
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
next prev parent reply other threads:[~2005-03-03 4:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 23:07 [Qemu-devel] Qemu Guest Tools olig9
2005-03-01 23:15 ` Joshua Kugler
2005-03-02 1:32 ` Jim C. Brown
2005-03-02 2:49 ` Mark Williamson
2005-03-02 12:44 ` Oliver Gerlich
2005-03-02 13:23 ` Mark Williamson
2005-03-02 14:38 ` Jim C. Brown
2005-03-02 21:08 ` olig9
2005-03-02 23:07 ` Jim C. Brown
2005-03-03 4:24 ` Brad Campbell [this message]
2005-03-03 5:09 ` Jim C. Brown
[not found] <MC3-F26ZAIxpmV2kER60005c293@mc3-f26.hotmail.com>
2005-03-05 3:50 ` Nathan Kunkee
2005-03-05 4:22 ` Herbert Poetzl
2005-03-05 10:44 ` Oliver Gerlich
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=4226916C.8050706@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).