Hi Krešimir, thanks for the clarifications! To be clear the common setup is to use migration with some kind of shared storage which can be anything from a clusterFS of any kind with image files to a shared FCP infrastructure. Therefore while --copy* can be handy it is not the common case and has some constraints.
Here a snippet from the man page: "--copy-storage-all indicates migration with non-shared storage with full disk copy, --copy-storage-inc indicates migration with non-shared storage with incremental copy (same base image shared between source and destination). In both cases the disk images have to exist on destination host, the --copy-storage-... options only tell libvirt to transfer data from the images on source host to the images found at the same place on the destination host." In your case I want to emphasize on "In both cases the disk images have to exist on destination host" - I know this applies to image files which need to exist on the path, but it might very well be true for an LVM as well. And since you report that after creating the entry on the target things work that seems to confirm this. I'm leaning towards "works as expected" on this one but I'm open for a discussion if needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943847 Title: virsh migrate with LVM volume as disk fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1943847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
