From: Eric Blake <eblake@redhat.com>
To: siddharth srivastava <akssps011@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Qemu Live Migration: File Descriptor
Date: Mon, 16 Jul 2012 09:29:03 -0600 [thread overview]
Message-ID: <5004333F.1020705@redhat.com> (raw)
In-Reply-To: <CAHuvxeVG-VzcN4OD7uojMUNhLB1uQGBni8BpcCBzX1chYc7fvw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
On 07/14/2012 08:45 AM, siddharth srivastava wrote:
> Hi
>
> I have been exploring various live migration ways that qemu supports.
> In the Qemu Migration documentation at: [1], it is only mentioned how
> to invoke tcp and exec migration schemes.
> But there is no mention of unix and fd migration schemes.
>
> In the code I see that the argument for tcp, fd,unix and exec goes
> into uri. But neither in the code nor in the docs/migration, it is
> mentioned what it expects as uri.
> So how do you start migration with these schemes ?
The libvirt code base exposes all of these migration schemes (although
it currently favors fd: migration wherever possible). Starting a
migration requires a Unix socket on the monitor command, and passing in
the file descriptor via SCM_RIGHTS via the 'getfd' monitor command prior
to using the 'migrate' monitor command to use that new fd.
--
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: 620 bytes --]
prev parent reply other threads:[~2012-07-16 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-14 14:45 [Qemu-devel] Qemu Live Migration: File Descriptor siddharth srivastava
2012-07-16 15:29 ` 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=5004333F.1020705@redhat.com \
--to=eblake@redhat.com \
--cc=akssps011@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).