From: Gary R Hook <grhookatwork@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Network Migration in QEMU during Live Migration
Date: Wed, 04 Feb 2015 15:46:24 -0600 [thread overview]
Message-ID: <54D29330.8000605@gmail.com> (raw)
In-Reply-To: <54D27AF1.8020302@redhat.com>
On 2/4/15 2:02 PM, Eric Blake wrote:
> On 02/04/2015 12:01 PM, Azizul Hakim wrote:
>> Does QEMU support network migration so that the migration process is
>> transparent to users? For example if my VM has a web server, I would like
>> my user still be able to send request to the server after the migration
>> process is completed. But since migration causes a change of the physical
>> machine, the IP address is different. So how do I achieve this? I
>> understand that I've to create bridge network. What other things do I've to
>> take care off? Is it possible at all?
>
> The IP address of the host is different, but the IP address seen by the
> guest is the same. Live migration has been possible for several years
> with qemu, and people do it all the time. The guest sees very minimal
> downtime (a few milliseconds). If you use a higher-layer software, like
> libvirt, then triggering a live migration of a guest is quite easy.
What he said. The guest doesn't know, doesn't care, and doesn't change
its network configuration; external connections are maintained. Only the
host upon which the guest runs changes, and that is kind of irrelevant
from a guest perspective.
--
Gary R Hook
Senior Kernel Engineer
NIMBOXX, Inc
prev parent reply other threads:[~2015-02-04 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 19:01 [Qemu-devel] Network Migration in QEMU during Live Migration Azizul Hakim
2015-02-04 20:02 ` Eric Blake
2015-02-04 21:46 ` Gary R Hook [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=54D29330.8000605@gmail.com \
--to=grhookatwork@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).