qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Gleb Natapov <gleb@redhat.com>
Cc: Eric Van Hensbergen <ericvanhensbergen@us.ibm.com>,
	Chris Wright <chrisw@redhat.com>, kvm-devel <kvm@vger.kernel.org>,
	Dor Laor <dlaor@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] Re: A new direction for vmchannel?
Date: Fri, 23 Jan 2009 14:58:56 -0600	[thread overview]
Message-ID: <497A2F90.3050405@codemonkey.ws> (raw)
In-Reply-To: <20090123204347.GC17445@redhat.com>

Gleb Natapov wrote:
> On Fri, Jan 23, 2009 at 08:45:33AM -0600, Anthony Liguori wrote:
>   
>> Thoughts?
>>
>>     
> Looks good, but I am not to much familiar with p9. Will it provide us
> with stream semantics?

Sure.  It has read and write operations.  You just have to implement 
them in the same sort of way you'd implement them for a character device.

>  How much work is needed to support this in
> Windows (what is your estimation)?

If you structure your guest applications to use a library, sort of like 
libsysfs, then on Windows, you could implement a 9P client in 
userspace.  I have a 9P client that can be used for this.  You just need 
some way to get the stream to userspace.  You could write a virtio 
windows driver that exposed the stream down to userspace.  You could 
also use an alternative transport for Windows (like a serial port).

>  Will migration be transparent to
> in guest users?
>   

There's no better migration story for vmchannel backends implemented 
outside of QEMU.  For the ones in QEMU, migration should be transparent.

Regards,

Anthony Liguori

> --
> 			Gleb.
>   

  reply	other threads:[~2009-01-23 20:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23 14:45 [Qemu-devel] A new direction for vmchannel? Anthony Liguori
2009-01-23 17:12 ` [Qemu-devel] " Chris Wright
2009-01-23 17:37   ` Anthony Liguori
2009-01-23 20:43 ` Gleb Natapov
2009-01-23 20:58   ` Anthony Liguori [this message]
2009-01-24  0:02     ` Dor Laor
2009-01-24 10:22       ` Alexander Graf
2009-01-24 22:28         ` Dor Laor
2009-01-24 17:19 ` Daniel P. Berrange
2009-01-24 17:52   ` Anthony Liguori
2009-01-24 18:39     ` Gleb Natapov
2009-01-24 18:47       ` Anthony Liguori
2009-01-24 19:30       ` Anthony Liguori
2009-01-24 21:00         ` Jamie Lokier
2009-01-24 21:22           ` Anthony Liguori
2009-01-25 14:16     ` Daniel P. Berrange
2009-01-25 17:58       ` Anthony Liguori

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=497A2F90.3050405@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=dlaor@redhat.com \
    --cc=ericvanhensbergen@us.ibm.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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).