From: Paolo Bonzini <pbonzini@redhat.com>
To: Ruben Kerkhof <ruben@rubenkerkhof.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block-migration: deprecate block migration for the 1.2 release
Date: Mon, 20 Aug 2012 10:23:45 +0200 [thread overview]
Message-ID: <5031F411.4020105@redhat.com> (raw)
In-Reply-To: <CAPed3OGhTati8dLVwUpg3hzvkwv+yUY7cGB2cV7Cn600+e-=vA@mail.gmail.com>
Il 19/08/2012 10:13, Ruben Kerkhof ha scritto:
>> > That's correct. Live block migration will use two ports, both served by
>> > the destination, one using NBD and one for RAM/device migration data.
>> > It will be a little more complicated than just migrate -b, but nothing
>> > that libvirt cannot orchestrate.
> Will I still be able to cap the migration bandwidth?
Yes, though you will have to cap the two bandwidths separately.
> And how about security? Libvirt can tunnel the data, I believe by
> passing an fd to qemu, and encrypting the connection with TLS.
Libvirt can do the same on the NBD connection.
Paolo
next prev parent reply other threads:[~2012-08-20 8:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 13:32 [Qemu-devel] [PATCH] block-migration: deprecate block migration for the 1.2 release Anthony Liguori
2012-08-14 13:48 ` Kevin Wolf
2012-08-14 14:52 ` Luiz Capitulino
2012-08-14 15:02 ` Kevin Wolf
2012-08-14 15:48 ` Luiz Capitulino
2012-08-14 15:59 ` Kevin Wolf
2012-08-14 14:42 ` Stefan Hajnoczi
2012-08-15 8:12 ` Ruben Kerkhof
2012-08-15 12:38 ` Stefan Hajnoczi
2012-08-16 7:37 ` Ruben Kerkhof
2012-08-18 19:08 ` Paolo Bonzini
2012-08-19 8:13 ` Ruben Kerkhof
2012-08-20 8:23 ` Paolo Bonzini [this message]
2012-08-20 8:47 ` Ruben Kerkhof
2012-08-18 19:10 ` Paolo Bonzini
2012-08-14 14:49 ` Luiz Capitulino
2012-08-14 19:45 ` Anthony Liguori
2012-08-14 20:25 ` Markus Armbruster
2012-08-14 20:32 ` Luiz Capitulino
2012-08-14 20:26 ` Luiz Capitulino
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=5031F411.4020105@redhat.com \
--to=pbonzini@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ruben@rubenkerkhof.com \
--cc=stefanha@linux.vnet.ibm.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).