[Pkg-libvirt-maintainers] Bug#878299: Bug#878299: libvirt-daemon: Live migration with qemu - not working with copy-storage-xx on stretch

[Guido Günther]

Hi,
On Thu, Oct 12, 2017 at 02:01:45PM +0200, Jan Sechovec wrote:
> Package: libvirt-daemon
> Version: 3.0.0-4
> Severity: normal
> 
> Dear Maintainer,
> 
> after dist-upgrade from jessie to stretch live migrations with --copy-storage-all stopped working.
> There is no usable error/warning log message, migration process waits for something, that will not 
> happen (until killed).
> 
> example: 
> virsh migrate --live virtual qemu+ssh://dest-host/system --verbose --persistent --copy-storage-all
> 
> We're using local LVM logical volumes for virtuals:
> 
> <disk type='block' device='disk'>
>   <driver name='qemu' type='raw' cache='none' io='native'/>
>   <source dev='/dev/data/sys-virtual'/>
>   <target dev='vda' bus='virtio'/>
>   <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
> </disk>
> 
> Volumes exists on both source and target side (no problems with this setup until upgrade to stretch, 
> it worked fine on squeeze/wheezy/jessie distros.
> 
> Migration without copying of data finishes successfuly, problem appears only with --copy-storage-all 
> and --copy-storage-inc. 
> 
> When running with LIBVIRT_DEBUG=1, last executed action is Perform3 in virDomainMigrateVersion3Full,
> then only waiting. Transmitting of storage data never starts. I've tried migration between 
> stretch->jessie, stretch->stretch, jessie-> stretch  hosts, none of these worked. When migrating from 
> jessie to stretch, it gets even worse - after a while, the migrated virtual freezes until the 
> migration virsh process is killed (after killing it starts responding again).
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796122#59

That's why I've merged them. Thanks for adding the above details and
trying various combinations! I currently don't have the resources to
work on migration related bugs (although it's on my todo list since
quite some tme) so if somebody wants do dig into this (maybe checking
upstream commit logs and trying patches) that would be great.
 -- Guido