All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Chris Wright <chrisw@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Gleb Natapov <gleb@redhat.com>, Dor Laor <dlaor@redhat.com>,
	Avi Kivity <avi@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Eric Van Hensbergen <ericvanhensbergen@us.ibm.com>,
	kvm-devel <kvm@vger.kernel.org>
Subject: Re: A new direction for vmchannel?
Date: Fri, 23 Jan 2009 11:37:34 -0600	[thread overview]
Message-ID: <497A005E.8000701@codemonkey.ws> (raw)
In-Reply-To: <20090123171251.GB3622@x200.localdomain>

Chris Wright wrote:
> * Anthony Liguori (aliguori@us.ibm.com) wrote:
>   
>> The userspace configuration aspects of the current implementation of  
>> vmchannel are pretty annoying.  Moreover, we would like to make use of  
>> something like vmchannel in a kernel driver and I fear that it's going  
>> to be difficult to do that.
>>     
>
> What's the use for vmchannel from kernel driver?
>   

Well, it doesn't exactly have to be vmchannel, but the desire is to have 
the management tools to be able to communicate directly with a kernel 
driver.  We could certainly just use virtio and route it through QEMU to 
the management tool.  It would be useful to just use vmchannel though.

>> Thoughts?
>>     
>
> Heh, works for me ;-)  Last time I suggested an fs it got shot down due to
> the burden it puts on the guest implementation (notably windows and
> other guests and ease of adding a new fs implementation).
>
> Doesn't directly solve addressing (IOW, easy to do with hierarchical
> namespace, but if vmchannel ever talks guest-to-guest...).  Clearly not
> a huge issue.
>
> Should handle the reliable messaging bit (one big push for using tcp),
> and has advantage of being a structured protocol.
>
> Has the similar ABI issue that we see in Linux with sysfs, namely it's
> easy to screw up...but that is manageable.
>
> BTW, what ever happened to just using a serial device (granted needs
> some protocol layered on top...)?
>   

I think you end up having a lot of the same issues with respect to 
making it transparent to the guest.  You could still do 9p over serial 
and still use a synthetic file system in the guest.  In fact, this is a 
pretty reasonable thing to do for older kernel guests and even Windows.

Regards,

Anthony Liguori

> thanks,
> -chris
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   


WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: Chris Wright <chrisw@redhat.com>
Cc: Eric Van Hensbergen <ericvanhensbergen@us.ibm.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	kvm-devel <kvm@vger.kernel.org>, Gleb Natapov <gleb@redhat.com>,
	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 11:37:34 -0600	[thread overview]
Message-ID: <497A005E.8000701@codemonkey.ws> (raw)
In-Reply-To: <20090123171251.GB3622@x200.localdomain>

Chris Wright wrote:
> * Anthony Liguori (aliguori@us.ibm.com) wrote:
>   
>> The userspace configuration aspects of the current implementation of  
>> vmchannel are pretty annoying.  Moreover, we would like to make use of  
>> something like vmchannel in a kernel driver and I fear that it's going  
>> to be difficult to do that.
>>     
>
> What's the use for vmchannel from kernel driver?
>   

Well, it doesn't exactly have to be vmchannel, but the desire is to have 
the management tools to be able to communicate directly with a kernel 
driver.  We could certainly just use virtio and route it through QEMU to 
the management tool.  It would be useful to just use vmchannel though.

>> Thoughts?
>>     
>
> Heh, works for me ;-)  Last time I suggested an fs it got shot down due to
> the burden it puts on the guest implementation (notably windows and
> other guests and ease of adding a new fs implementation).
>
> Doesn't directly solve addressing (IOW, easy to do with hierarchical
> namespace, but if vmchannel ever talks guest-to-guest...).  Clearly not
> a huge issue.
>
> Should handle the reliable messaging bit (one big push for using tcp),
> and has advantage of being a structured protocol.
>
> Has the similar ABI issue that we see in Linux with sysfs, namely it's
> easy to screw up...but that is manageable.
>
> BTW, what ever happened to just using a serial device (granted needs
> some protocol layered on top...)?
>   

I think you end up having a lot of the same issues with respect to 
making it transparent to the guest.  You could still do 9p over serial 
and still use a synthetic file system in the guest.  In fact, this is a 
pretty reasonable thing to do for older kernel guests and even Windows.

Regards,

Anthony Liguori

> thanks,
> -chris
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   

  reply	other threads:[~2009-01-23 17:37 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23 14:45 A new direction for vmchannel? Anthony Liguori
2009-01-23 14:45 ` [Qemu-devel] " Anthony Liguori
2009-01-23 17:12 ` Chris Wright
2009-01-23 17:12   ` [Qemu-devel] " Chris Wright
2009-01-23 17:37   ` Anthony Liguori [this message]
2009-01-23 17:37     ` Anthony Liguori
2009-01-23 20:43 ` Gleb Natapov
2009-01-23 20:43   ` [Qemu-devel] " Gleb Natapov
2009-01-23 20:58   ` Anthony Liguori
2009-01-23 20:58     ` [Qemu-devel] " Anthony Liguori
2009-01-24  0:02     ` Dor Laor
2009-01-24  0:02       ` Dor Laor
2009-01-24 10:22       ` Alexander Graf
2009-01-24 10:22         ` Alexander Graf
2009-01-24 22:28         ` Dor Laor
2009-01-24 22:28           ` Dor Laor
2009-01-24 17:19 ` Daniel P. Berrange
2009-01-24 17:19   ` [Qemu-devel] " Daniel P. Berrange
2009-01-24 17:52   ` Anthony Liguori
2009-01-24 17:52     ` [Qemu-devel] " Anthony Liguori
2009-01-24 18:39     ` Gleb Natapov
2009-01-24 18:39       ` [Qemu-devel] " Gleb Natapov
2009-01-24 18:47       ` Anthony Liguori
2009-01-24 18:47         ` [Qemu-devel] " Anthony Liguori
2009-01-24 19:30       ` Anthony Liguori
2009-01-24 19:30         ` [Qemu-devel] " Anthony Liguori
2009-01-24 21:00         ` Jamie Lokier
2009-01-24 21:00           ` Jamie Lokier
2009-01-24 21:22           ` Anthony Liguori
2009-01-24 21:22             ` Anthony Liguori
2009-01-25 14:16     ` Daniel P. Berrange
2009-01-25 14:16       ` [Qemu-devel] " Daniel P. Berrange
2009-01-25 17:58       ` Anthony Liguori
2009-01-25 17:58         ` [Qemu-devel] " 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=497A005E.8000701@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=aliguori@us.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.