Hi, there is kind of a minefield of non-supported configuration options around this so we might first need to clarify what exactly you use to get an idea - depending on that we have to then search for a breaking change or fix OR otoh might just report/discuss a feature request upstream.
Saying "created as volume in LVM group" really isn't uniqe. Could be either of: 1. LVM "group" manually set up and using /dev/mapper/foo or such in the guest XML 2. LVM pool managed by libvirt 3. LVM volumes, but actually with FS and image files on it and those used in the guest XML 4. As above but with or without shared storage of some kind, if so which 5. the exact type of LVM configuration - is it a LUN or a block device for the libvirt/qemu config? ... In summary, please describe in detail the setup of your LVM, your (potentially cross system) storage and the guest configuration (I recommend adding a guest XML of the good and the bad case). Furthermore you didn't post the exact error message, there are more than one way migrations can fail, so it will be useful to see Command+ConsoleOutput+Log. About the Log please consider on sending and receiving end to enable libvirt debug [1] - attach both logs and tell us here a timestamp when the migration was tried (the log is rather noisy and a timestamp helps to find things). And finally is this something that worked in former versions and now got broken by an update or is this just you wondering that in this combination it doesn't work? [1]: https://libvirt.org/kbase/debuglogs.html ** Changed in: libvirt (Ubuntu) Status: New => Incomplete -- 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
