On Wed, Sep 3, 2014 at 2:12 PM, Eric Blake <eblake@xxxxxxxxxx> wrote:
On 09/03/2014 01:05 PM, Gary Hook wrote:This command does not default to migrating storage,...
>
> root@huey:/tmp# virsh migrate --live --p2p
Oh, you mean like this?
error: Failed to open file '/mnt/store01/virt/e7f75b9b-9ed4-4f7e-aa86-e481ab911d6f.qcow2': No such file or directory
Apologies; I should have used this one in the first place. Too many attempts in the command history....
I'm guessing I"m still missing something...
...therefore, this error message is expected if the storage is not
> (huey is 10.10.11.203, dewey is 10.10.11.204; DNS works, but I thought to
> eliminate that as a source of this problem.) As can be seen, the .qcow2
> files exists on the source system, and does not exist on the target system.
already present on the destination.
Migration requires either that you have shared storage (both source and
destination can see THE SAME FILE, and if one side sees the file via
NFS, then both sides must see the file via NFS [you can't mix local and
NFS]). OR, you have to tell migration that you want to migrate storage
as well as machine state, by adding the --copy-storage-all flag to your
command line.
Understood; perfectly sensible. See above.
http://libvirt.org/migration.html should document useful information
such as this; would you like to submit a patch to help improve that web
page? The sources are in libvirt.git under docs/migration.html.in.
Yep, read that page (several times). At such point I have anything of substance to add, absolutely, yes, I very much want to contribute. I am just starting out building my skills on KVM and libvirt (background is with PHYP on Power) but fully intend to become conversant with the packages.
_______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
