This bug was fixed in the package qemu - 1:2.10~rc4+dfsg-0ubuntu1 --------------- qemu (1:2.10~rc4+dfsg-0ubuntu1) artful; urgency=medium
* Merge with Upstream 2.10-rc4; This fixes a migration issue (LP: #1711602); Remaining changes: - qemu-kvm to systemd unit - d/qemu-kvm-init: script for QEMU KVM preparation modules, ksm, hugepages and architecture specifics - d/qemu-kvm.service: systemd unit to call qemu-kvm-init - d/qemu-system-common.install: install systemd unit and helper script - d/qemu-system-common.maintscript: clean old sysv and upstart scripts - d/qemu-system-common.qemu-kvm.default: defaults for /etc/default/qemu-kvm - d/rules: install /etc/default/qemu-kvm - Enable nesting by default - set nested=1 module option on intel. (is default on amd) - re-load kvm_intel.ko if it was loaded without nested=1 - d/p/ubuntu/expose-vmx_qemu64cpu.patch: expose nested kvm by default in qemu64 cpu type. - d/p/ubuntu/enable-svm-by-default.patch: Enable nested svm by default in qemu64 on amd - libvirt/qemu user/group support - qemu-system-common.postinst: remove acl placed by udev, and add udevadm trigger. - qemu-system-common.preinst: add kvm group if needed - Distribution specific machine type - d/p/ubuntu/define-ubuntu-machine-types.patch: define distro machine types to ease future live vm migration. - d/qemu-system-x86.NEWS Info on fixed machine type defintions - improved dependencies - Make qemu-system-common depend on qemu-block-extra - Make qemu-utils depend on qemu-block-extra - let qemu-utils recommend sharutils - s390x support - Create qemu-system-s390x package - Include s390-ccw.img firmware - Enable numa support for s390x - ppc64[le] support - d/qemu-system-ppc.links provide usr/bin/qemu-system-ppc64le symlink - Enable seccomp for ppc64el - bump libseccomp-dev dependency, 2.3 is the minimum for ppc64 - arch aware kvm wrappers - update VCS-git to match the Artful branch - disable missing x32 architecture - d/rules: or32 is now named or1k (since 4a09d0bb) - d/qemu-system-common.docs: new paths since (ac06724a) - d/qemu-system-common.install: qmp-commands.txt removed, but replaced by qapi-schema.json which is already packaged (since 4d8bb958) - d/p/02_kfreebsd.patch: utimensat is no more optional upstream (Update to Debian patch to match qemu 2.10) - s390x package now builds correctly on all architectures (LP 1710695) * Added changes: - d/qemu-system-common.docs: adapt new path of live-block-operations.rst since 8508eee7 - d/qemu-system-common.docs: adapt q35 config paths since 9ca019c1 - make nios2/hppa not installed explicitly until further stablized - d/qemu-guest-agent.install: add the new guest agent reference man page qemu-ga-ref - d/qemu-system-common.install: add the now generated qapi/qmp reference along the qapi intro - d/not-installed: ignore further generated (since 56e8bdd4) files in dh_missing that are already provided in other formats qemu-doc, qemu-qmp-ref,qemu-ga-ref - d/p/ubuntu/define-ubuntu-machine-types.patch: update to match new changes in 2.10-rc4 -- Christian Ehrhardt <christian.ehrha...@canonical.com> Fri, 25 Aug 2017 07:49:30 +0200 ** Changed in: qemu (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1711602 Title: --copy-storage-all failing with qemu 2.10 Status in QEMU: Fix Committed Status in qemu package in Ubuntu: Fix Released Bug description: We fixed an issue around disk locking already in regard to qemu-nbd [1], but there still seem to be issues. $ virsh migrate --live --copy-storage-all kvmguest-artful-normal qemu+ssh://10.22.69.196/system error: internal error: qemu unexpectedly closed the monitor: 2017-08-18T12:10:29.800397Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) 2017-08-18T12:10:48.545776Z qemu-system-x86_64: load of migration failed: Input/output error Source libvirt log for the guest: 2017-08-18 12:09:08.251+0000: initiating migration 2017-08-18T12:09:08.809023Z qemu-system-x86_64: Unable to read from socket: Connection reset by peer 2017-08-18T12:09:08.809481Z qemu-system-x86_64: Unable to read from socket: Connection reset by peer Target libvirt log for the guest: 2017-08-18T12:09:08.730911Z qemu-system-x86_64: load of migration failed: Input/output error 2017-08-18 12:09:09.010+0000: shutting down, reason=crashed Given the timing it seems that the actual copy now works (it is busy ~10 seconds on my environment which would be the copy). Also we don't see the old errors we saw before, but afterwards on the actual take-over it fails. Dmesg has no related denials as often apparmor is in the mix. Need to check libvirt logs of source [2] and target [3] in Detail. [1]: https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02200.html [2]: http://paste.ubuntu.com/25339356/ [3]: http://paste.ubuntu.com/25339358/ To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1711602/+subscriptions