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 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
