[ovirt-users] migration of a VM: fails

[Francesco Romani]

On 05/16/2017 01:06 PM, cmc wrote:
> Hi,
>
> Just trying to place in maintenance mode for a version upgrade, and
> one VM fails to migrate. The other 20-odd move over successfully. In
> /var/log/libvirt/qemu/, the VM's log on the source reports:
>
> 2017-05-16 09:48:06.339+0000: initiating migration
> 2017-05-16T09:52:25.498932Z qemu-kvm: socket_writev_buffer: Got err=32
> for (131328/18446744073709551615)
> 2017-05-16 09:52:47.311+0000: initiating migration
> 2017-05-16T09:57:06.755402Z qemu-kvm: socket_writev_buffer: Got err=32
> for (69776/18446744073709551615)
> 2017-05-16 09:57:55.109+0000: initiating migration
> 2017-05-16T10:02:14.143221Z qemu-kvm: socket_writev_buffer: Got err=32
> for (69776/18446744073709551615)
> 2017-05-16 10:02:59.497+0000: initiating migration
> 2017-05-16T10:07:18.542872Z qemu-kvm: socket_writev_buffer: Got err=32
> for (69776/18446744073709551615)
> 2017-05-16 10:08:03.896+0000: initiating migration
> 2017-05-16T10:12:23.206731Z qemu-kvm: socket_writev_buffer: Got err=32
> for (69776/18446744073709551615)
> 2017-05-16 10:13:08.941+0000: initiating migration
> 2017-05-16T10:17:27.861843Z qemu-kvm: socket_writev_buffer: Got err=32
> for (69776/18446744073709551615)
> 2017-05-16 10:18:13.690+0000: initiating migration
> 2017-05-16T10:22:32.929689Z qemu-kvm: socket_writev_buffer: Got err=32
> for (69803/18446744073709551615)
> 2017-05-16 10:23:19.846+0000: initiating migration
> 2017-05-16T10:27:39.175724Z qemu-kvm: socket_writev_buffer: Got err=32
> for (69776/18446744073709551615)
> 2017-05-16 10:28:25.141+0000: initiating migration
> 2017-05-16T10:28:35.620070Z qemu-kvm: socket_writev_buffer: Got err=32
> for (65753/18446744073709551615)
> 2017-05-16 10:29:10.678+0000: initiating migration
> 2017-05-16T10:33:29.718527Z qemu-kvm: socket_writev_buffer: Got err=32
> for (53477/18446744073709551615)
> 2017-05-16 10:38:35.517+0000: initiating migration
>

Hi,
it seems either qemu issue or misconfiguration. To investigate, we need
more data; so could you please share:
1. the domain XML (virtsh -r dumpxml ...) and/or the qemu command line
of the affected VM, on the source side
2. the version of QEMU and libvirt that you are running

Thanks and bests,

-- 
Francesco Romani
Senior SW Eng., Virtualization R&D
Red Hat
IRC: fromani github: @fromanirh