From: Troy Benjegerdes <hozer-TBByXz/9jYzYtjvyW6yDsg@public.gmane.org>
To: Cam Macdonell <cam-edFDblaTWIyXbbII50Afww@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Using VMChannel to communicate with the host.
Date: Fri, 7 Sep 2007 19:51:23 -0500 [thread overview]
Message-ID: <20070908005122.GB6764@narn.hozed.org> (raw)
In-Reply-To: <46E1D44E.90509-edFDblaTWIyXbbII50Afww@public.gmane.org>
On Fri, Sep 07, 2007 at 04:44:30PM -0600, Cam Macdonell wrote:
>
> Hi,
>
> I'm trying to get a better understanding of VM-to-host communication
> that doesn't involve going over virtual networks. I understand there
> are a couple of developments underway, but I just want to play around a
> better sense of things. I think the current hypercall mechanism is the
> current way to do this using the -vmchannel option. But, I'm not very
> experienced with PCI devices and their drivers so I need some help. All
> I want to do is to communicate across a unix domain socket on the host.
> Besides loading the hypercall module in the guest how do things needs
> to be configured on the host?
>
> Is there a simple tutorial or just a webpage with examples for how to do
> this?
I'm going to suggest that a better way to do VM-to-host or VM-to-VM
communication would be to write an OpenFabrics (www.openfabrics.org)
driver that uses hypercalls. There is probably some gotcha I am not
aware of, but I think this would allow direct userspace to userspace
communication between a process running on a host, and a process running
on a VM, while still maintaining isolation.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-09-08 0:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 22:44 Using VMChannel to communicate with the host Cam Macdonell
[not found] ` <46E1D44E.90509-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-09-08 0:51 ` Troy Benjegerdes [this message]
[not found] ` <20070908005122.GB6764-na1kE3HDu0idQnJuSAr7PQ@public.gmane.org>
2007-09-09 8:38 ` Dor Laor
2007-09-09 9:56 ` Dor Laor
[not found] ` <46E3C345.9090305-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-10 16:01 ` Cam Macdonell
[not found] ` <46E56A71.50102-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-09-11 7:09 ` Dor Laor
[not found] ` <46E63F46.2040707-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-11 14:36 ` Cameron Macdonell
[not found] ` <FFFA58AC-4040-4E6D-A28F-BBBDD78F8722-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-09-11 20:21 ` Dor Laor
[not found] ` <64F9B87B6B770947A9F8391472E032160D95E340-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-09-11 22:57 ` Cam Macdonell
[not found] ` <46E71D72.7000901-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-09-15 22:47 ` Dor Laor
[not found] ` <46EC60FF.60209-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-17 16:00 ` Cameron Macdonell
[not found] ` <07D7C2A1-A29D-4CED-9B97-5C0071C75AF8-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-09-17 22:42 ` Dor Laor
[not found] ` <46EF02C7.1000904-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-18 22:27 ` Cam Macdonell
[not found] ` <46F050BB.9040801-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-09-19 10:31 ` Dor Laor
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=20070908005122.GB6764@narn.hozed.org \
--to=hozer-tbbyxz/9jyzytjvyw6ydsg@public.gmane.org \
--cc=cam-edFDblaTWIyXbbII50Afww@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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