From: Eric Blake <eblake@redhat.com>
To: Gary Jordan <jordgary@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu only uses a Qemu File to communicate in two hosts?
Date: Mon, 30 Jun 2014 16:30:57 -0600 [thread overview]
Message-ID: <53B1E521.2010207@redhat.com> (raw)
In-Reply-To: <CAF8TkMLw11i=LGzYhAV0UwX+c8_OGAH9VW-Cd9pxrnE39v7ngg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
On 06/30/2014 03:58 PM, Gary Jordan wrote:
> Hi Eric,
[please don't top-post in technical lists]
>
> Could I find a way for two guests in two hosts to communicate? Like qemu
> starts one vm in Host 1 and qemu also starts a vm in Host 2, the vm can
> share their memory. Is there some existed way to do that, like remote IPC
> in qemu?
How would you communicate between two bare-metal hosts? Emulate that
same setup in your two guests.
You appear to be intent on setting up shared memory solutions, when I
think the better thing is to focus on setting up efficient emulated
network device solutions. Then your code will be portable no matter how
the network device frontend is hooked up to the host backend (and it may
be possible to have a host backend that uses shared memory for a very
efficient network device emulation when two VMs are on the same host,
but which can also be ported to work between VMs on different hosts by
using regular networking - and that's what virtio-net is focusing on
defining).
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2014-06-30 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 21:02 [Qemu-devel] Qemu only uses a Qemu File to communicate in two hosts? Gary Jordan
2014-06-30 21:08 ` Eric Blake
2014-06-30 21:58 ` Gary Jordan
2014-06-30 22:30 ` Eric Blake [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=53B1E521.2010207@redhat.com \
--to=eblake@redhat.com \
--cc=jordgary@gmail.com \
--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).