In 5/5 tries this was on qemu_fill_buffer for my case.
But that was on the receiving side, and what you found is closer to the root
cause on the source of the migration.
I checked on qemu_file_set_error on the source and can confirm your finding
that on the source it is from bdrv_inactivate_all.
#0 qemu_file_set_error (f=f@entry=0x6b76b46c00, ret=ret@entry=-1) at
./migration/qemu-file.c:124
#1 0x0000006b727140cb in qemu_savevm_state_complete_precopy (f=0x6b76b46c00,
iterable_only=iterable_only@entry=false,
inactivate_disks=inactivate_disks@entry=true) at ./migration/savevm.c:1160
#2 0x0000006b7270c84b in migration_completion (start_time=<synthetic pointer>,
old_vm_running=<synthetic pointer>, current_active_state=4,
s=0x6b74ef53b0) at ./migration/migration.c:1858
#3 migration_thread (opaque=0x6b74ef53b0) at ./migration/migration.c:2023
#4 0x00007f61a740e74a in start_thread (arg=0x7f61467fc700) at
pthread_create.c:456
#5 0x00007f61a714acaf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97
Also as I outlined - what seems ages ago in comment #6 - if the source
is a qemu 2.8 the migration works for me which would kind of match
assuming the root cause is in the source.
--
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:
New
Status in libvirt package in Ubuntu:
Confirmed
Status in qemu package in Ubuntu:
Confirmed
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
