From: Christian Theune <ct@gocept.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Selective block migration (still on 0.13)
Date: Thu, 13 Sep 2012 16:58:23 +0200 [thread overview]
Message-ID: <k2ssad$6v6$1@ger.gmane.org> (raw)
Hi,
we're currently still on 0.13, looking forward to a large update soon. :)
We haven't been using live migration up until now, but are
investigating it to multiple downtimes (restarting updated hosts and
restarting updated guests) when doing system updates. So, we're trying
to find out whether we can get this into a usable shape while still
running 0.13.
I saw that 0.13 does have block migration available. However, looking
at the code, it's an "either or" situation: migrate all block devices
or none.
In our case we have the root disks on iSCSI (through virtio-blk) and
two additional local disks (for /tmp and swp).
Now, the iSCSI shouldn't be migrated but the local disks should.
Reading up in the current code, it doesn't look like this would be
feasable. Can someone prove me wrong? Please? :)
Even the earlier discussion regarding live block copy which included a
reference to using libvirt sounds like it would have a problem
instrumenting the live migration correctly: how do you get the
migration atomic if you need to copy the block devices independent of
the VM migration? Maybe, I'm missing something.
Cheers,
Christian
next reply other threads:[~2012-09-13 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 14:58 Christian Theune [this message]
2012-09-13 17:11 ` [Qemu-devel] Selective block migration (still on 0.13) Eric Blake
2012-09-14 11:07 ` Kevin Wolf
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='k2ssad$6v6$1@ger.gmane.org' \
--to=ct@gocept.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).