With the patch from Stefan and your debug applied source and target I still run into the same issue I'd say. Id's are slightly off, but they are different on every try anyway.
Still looks the same for me: bdrv_inactivate_recurse: entry for drive-virtio-disk0 bdrv_inactivate_recurse: entry for #block184 bdrv_inactivate_recurse: entry for #block319 bdrv_inactivate_recurse: entry for #block218 bdrv_inactivate_recurse: exit end good for #block218 bdrv_inactivate_recurse: exit end good for #block319 bdrv_inactivate_recurse: entry for #block092 bdrv_inactivate_recurse: exit end good for #block092 bdrv_inactivate_recurse: exit end good for #block184 bdrv_inactivate_recurse: exit end good for drive-virtio-disk0 bdrv_inactivate_recurse: entry for #block1905 bdrv_inactivate_recurse: entry for #block1889 bdrv_inactivate_recurse: exit end good for #block1889 bdrv_inactivate_recurse: exit end good for #block1905 bdrv_inactivate_recurse: entry for drive-virtio-disk1 bdrv_inactivate_recurse: entry for #block551 bdrv_inactivate_recurse: entry for #block423 bdrv_inactivate_recurse: exit end good for #block423 bdrv_inactivate_recurse: exit end good for #block551 bdrv_inactivate_recurse: exit end good for drive-virtio-disk1 bdrv_inactivate_recurse: entry for #block2246 bdrv_inactivate_recurse: entry for #block2106 bdrv_inactivate_recurse: exit end good for #block2106 bdrv_inactivate_recurse: exit end good for #block2246 bdrv_inactivate_recurse: entry for drive-virtio-disk0 bdrv_inactivate_recurse: exit 2(-1) for drive-virtio-disk0 -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
