From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Jun Koi <junkoi2004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: inter-VM communication?
Date: Thu, 30 Nov 2006 12:21:31 +0200 [thread overview]
Message-ID: <456EB0AB.30508@qumranet.com> (raw)
In-Reply-To: <fdaac4d50611300217t1e667ad6gd7224cd3a0be8314-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Jun Koi wrote:
> On 11/30/06, Dor Laor <dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
>
>>> Hi,
>>>
>>> Do we have any inter-VM communication technique in KVM (something for
>>> example like event-channel in Xen) ?
>>>
>>> Thanks,
>>> Jun
>>>
>> Currently there is full isolation of the guests.
>> Such mechanism would not be complicated to add since we anyway map
>> memory from user space & inject interrupt from there also.
>> Do you have any specific interest in inter VM channel?
>>
>
> I want to exchange some data between a VM and hypervisor. One solution
> is to map some memory of that VM (from hypervisor), and read/write
> data thru that memory area. However, I need to a mechanism to notify
> the other partner when data is ready to read/write.
>
> Without any inter-VM communication mechanism, I dont see any clean way
> to achieve this. Any idea?
>
Write a pci device for qemu to do what you want. The pci device can
communicate through a unix domain socket, shared memory, or any other
ipc mechanism with any other process on the host (including other
virtual machines).
Guest->host communication is performed by writing the device's mmio
registers. Host->guest communications are done by raising a virtual
interrupt.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-11-30 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 6:35 inter-VM communication? Jun Koi
[not found] ` <fdaac4d50611292235p79633d2cn21970e4b28455882-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2006-11-30 7:09 ` Dor Laor
[not found] ` <64F9B87B6B770947A9F8391472E03216094CB08C-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2006-11-30 10:17 ` Jun Koi
[not found] ` <fdaac4d50611300217t1e667ad6gd7224cd3a0be8314-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2006-11-30 10:21 ` Avi Kivity [this message]
[not found] ` <456EB0AB.30508-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-11-30 10:26 ` 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=456EB0AB.30508@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=junkoi2004-Re5JQEeQqe8AvxtiuMwx3w@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 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.