Am 23.07.13 15:22, schrieb Eric Blake:
[please don't commandeer unrelated threads - when starting a new
topic,
make sure you are NOT setting in-reply-to]
I'm sorry. You're right.
On 07/23/2013 06:33 AM, Thomas Stein wrote:
> Hello.
>
> Can someone shed some light on the copy-storage-all feature? There are
> many hits on google. My current questions are.
>
> 1. is it possible to do a migrate --live --copy-storage-all .... without
> shared storage?
Yes, that's the point of --copy-storage-all.
> 2. Do i need to have a preexisting image on the destination node?
I know there has been some work to get to the point of not having to
pre-create images on the destination, but am not sure of the current
state of that work. Fastest might be to just try it and see; the error
message should be sane if it still isn't implemented.
> 3. Is this still true:
>
> The current implementation of --copy-storage-all uses a qemu interface
> that upstream qemu developers are reluctant to support, and risks
> running into problems. We have patches under review to use a new NBD
> server for migration when targeting qemu 1.4 with libvirt 1.0.2, with
> much less risk
What version of libvirt and qemu are you using? Newer libvirt is indeed
able to use NBD migration for a much cleaner result.
qemu-1.4.2 and libvirt-1.1.0. Do i have to use specific options for nbd
migration?
thank you
thomas