From: Gleb Natapov <gleb@redhat•com>
To: Evgeniy Polyakov <zbr@ioremap•net>
Cc: virtualization@lists•linux-foundation.org, kvm@vger•kernel.org,
linux-kernel@vger•kernel.org, netdev@vger•kernel.org
Subject: Re: Host<->guest channel interface advice needed
Date: Wed, 26 Nov 2008 15:20:06 +0200 [thread overview]
Message-ID: <20081126132006.GD3521@redhat.com> (raw)
In-Reply-To: <20081126130701.GB8921@ioremap.net>
On Wed, Nov 26, 2008 at 04:07:01PM +0300, Evgeniy Polyakov wrote:
> On Wed, Nov 26, 2008 at 02:39:19PM +0200, Gleb Natapov (gleb@redhat•com) wrote:
> > The interfaces that are being considered are netlink socket (only datagram
> > semantics, linux specific), new socket family or character device with
> > different minor number for each channel. Which one better suits for
> > the purpose? Is there other kind of interface to consider? New socket
> > family looks like a good choice, but it would be nice to hear other
> > opinions before starting to work on it.
>
> What about X (or whatever else) protocol running over host-guest network
> device, which are in the kernel already?
>
I should have mentioned that in my original mail. We don't want to
use IP stack for communication between host and guest for variety of
reasons. User of the VM may interfere with our communication by mis
configuring firewall for instance (and he/she may even not be aware
that an OS running inside a VM). We also want be able to communicate
with agent inside a guest even when guest's network is not yet configured.
--
Gleb.
prev parent reply other threads:[~2008-11-26 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 12:39 Host<->guest channel interface advice needed Gleb Natapov
2008-11-26 13:02 ` Arnd Bergmann
2008-11-26 13:07 ` Evgeniy Polyakov
2008-11-26 13:20 ` Gleb Natapov [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=20081126132006.GD3521@redhat.com \
--to=gleb@redhat$(echo .)com \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=virtualization@lists$(echo .)linux-foundation.org \
--cc=zbr@ioremap$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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