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 On the destination host, it reports: 2017-05-16T10:33:29.598425Z qemu-kvm: Unknown combination of migration flags: 0 2017-05-16T10:33:29.599524Z qemu-kvm: error while loading state section id 2(ram) 2017-05-16T10:33:29.601978Z qemu-kvm: load of migration failed: Invalid argument 2017-05-16 10:33:29.808+0000: shutting down In the engine log: 2017-05-16 11:57:28,675+01 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler5) [f8aa18b3-97b9-48e2-a681-cf3aaed330a5] VM '4921c5f5-7748-47eb-a90c-8e9ecbd91bcf'(pete_win7) was unexpectedly detected as 'MigratingTo' on VDS '424e6317-ad68-459b-bf88-7292e26710ae'(kvm-ldn-02) (expected on 'e050c27f-8709-404c-b03e-59c0167a824b') It stays in 'preparing for maintenance mode' on the GUI for the host, and reports errors on the status pane below, but then it reports that the host has successfully been put into maintenance mode, even though the VM is still showing as in migration. After more time has elapsed, it reports a failure again, and then eventually the host will again report it is in maintenance mode, and so on. When I hit 'cancel migration' it reports that the migration has been successfully cancelled in the status pane at the bottom, but then shows it still in migration in the upper window. When I select the VM itself, it reports it is "Migrating From: 99%". If I cancel the migration here, it actually does cancel the migration properly. The VM itself is up and running ok. Version of oVirt is 4.1.0.4-1.el7 Thanks in advance for any help. Please let me know if you need any full logs. Regards, Cam _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
