Hmm, it gets further but can still not complete this kind of migration: $ virsh migrate --live --copy-storage-all kvmguest-artful-normal qemu+ssh://10.22.69.30/system
Source: 2017-08-23 16:49:23.022+0000: initiating migration Unexpected error in bdrv_check_perm() at /build/qemu-VjSgVJ/qemu-2.10~rc3+dfsg/block.c:1574: 2017-08-23T16:49:23.203181Z qemu-system-x86_64: Block node is read-only 2017-08-23 16:49:23.762+0000: shutting down, reason=crashed Target: 2017-08-23T16:49:23.495478Z qemu-system-x86_64: Failed to load virtio_pci/modern_state:modern_state 2017-08-23T16:49:23.495505Z qemu-system-x86_64: Failed to load virtio/extra_state:extra_state 2017-08-23T16:49:23.495510Z qemu-system-x86_64: Failed to load virtio-balloon:virtio 2017-08-23T16:49:23.495515Z qemu-system-x86_64: error while loading state for instance 0x0 of device '0000:00:06.0/virtio-balloon' 2017-08-23T16:49:23.496071Z qemu-system-x86_64: load of migration failed: Input/output error 2017-08-23 16:49:23.797+0000: shutting down, reason=crashed I was to eager to get this close-to-real so I don't have Davids fprintf's applied anymore - I'll build those and then run it in the debugger, but until then what I can see is that behavior slightly changes (worse). It now crashes the guest on the source as well when aborting the migration. I need to debug to confirm, but it seems it still aborts the migration -> qemu-system-x86_64: load of migration failed: Input/output error But then can't fall back to the source and crashes at -> qemu-system-x86_64: Block node is read-only -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711602 Title: --copy-storage-all failing with qemu 2.10 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1711602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
