From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] migration network requirements
Date: Wed, 20 May 2015 10:21:19 +0100 [thread overview]
Message-ID: <20150520092118.GB2148@work-vm> (raw)
In-Reply-To: <555C10A7.4050008@ozlabs.ru>
* Alexey Kardashevskiy (aik@ozlabs.ru) wrote:
> Hi!
>
> Recent bugreports from our testers at IBM about failed migration across USA
> (for example, from NY to TX) made me wonder - what are the actual basic
> requirements/expectations for migration?
Oh that's fun.
> In what network is it normally tested (I use 1Gb/10Gb local network without
> routers)?
That's also my main test, but in the end it's just a TCP stream, so lots of bandwidth,
not that fussy about latency.
> Is there any reconnect/restart mechanism if the connection dropped (libvirt,
> qemu)?
No; one unbroken TCP connection; if you want some reconnect/restart
then tunnel the TCP oversomething that handles that.
> Is there any document describing network requirements (libvirt, qemu)?
Don't think so; libvirt has lots of different modes where it can
tunnel stuff as well, see:
http://www.libvirt.org/migration.html#transporttunnel
> Any ideas are appreciated :) Thanks!
How is it failing?
Dave
>
> --
> Alexey
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2015-05-20 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 4:42 [Qemu-devel] migration network requirements Alexey Kardashevskiy
2015-05-20 9:21 ` Dr. David Alan Gilbert [this message]
2015-05-20 14:07 ` Alexey Kardashevskiy
2015-05-20 14:18 ` Dr. David Alan Gilbert
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=20150520092118.GB2148@work-vm \
--to=dgilbert@redhat.com \
--cc=aik@ozlabs.ru \
--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).