From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: William Lima Reiznautt <willreli@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: Live Migration (L2 network)
Date: Mon, 27 Jul 2020 20:09:09 +0100 [thread overview]
Message-ID: <20200727190909.GA29172@work-vm> (raw)
In-Reply-To: <CAO4s5Y90ZTYLbt1M_JDOJx1wmOY43PEu+cFSw0SHY5BOEqk3pA@mail.gmail.com>
* William Lima Reiznautt (willreli@gmail.com) wrote:
> Hi folks,
>
> I hope everything is well.
Hi,
> Sorry about that doubt in this channel.
No, it's the right place to ask!
> I have a doubt about live migration interacting with layer 2 network, when
> the live migration is running. How does the qemu signal the switch network
> that the qemu instance changes port ? Because when the qemu migration to
> another port switch, the switch has a time to understand that flow is
> changed.
>
> I saw the dump traffic in live migration and I noticed that one packet
> (RARP). "This packet is created by qemu."
>
> Does anyone know if there is documentation on this?
I'm not sure we have documentation, but the code is in net/announce.c in
recent qemu.
When the migration has finished we send an ARP and then, when it starts
running, we tell the guest to send a RARP; we send those a few times
to make sure we don't miss it.
Those are normally enough for the switch to realise that the VM
has moved port; some very complex switch setups are less forgiving - in
recent qemu's you can send the announce again later and/or change the
timing of it.
Dave
> Thanks
>
> - - -
> William Lima Reiznautt
> willreli@gmail.com
> www.ic.unicamp.br/~william
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2020-07-27 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 11:05 Live Migration (L2 network) William Lima Reiznautt
2020-07-27 19:09 ` Dr. David Alan Gilbert [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=20200727190909.GA29172@work-vm \
--to=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=willreli@gmail.com \
/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).