The one that issues the message is at
#0 bdrv_check_perm (bs=bs@entry=0x55ca4c7a7150, q=0x0,
q@entry=0xf9574d6356918c00, cumulative_perms=3, cumulative_shared_perms=23,
ignore_children=ignore_children@entry=0x0, errp=errp@entry=0x7ffdba216258)
at ./block.c:1645
#1 0x000055ca4a0645b5 in bdrv_check_update_perm (bs=bs@entry=0x55ca4c7a7150,
q=0xf9574d6356918c00, q@entry=0x0,
new_used_perm=new_used_perm@entry=3,
new_shared_perm=new_shared_perm@entry=23,
ignore_children=ignore_children@entry=0x0,
errp=errp@entry=0x7ffdba216258) at ./block.c:1841
#2 0x000055ca4a064d47 in bdrv_root_attach_child
(child_bs=child_bs@entry=0x55ca4c7a7150,
child_name=child_name@entry=0x55ca4a204ae2 "root",
child_role=child_role@entry=0x55ca4a701b80 <child_root>, perm=3,
shared_perm=23, opaque=opaque@entry=0x55ca4c832c60, errp=0x7ffdba216258)
at ./block.c:2041
#3 0x000055ca4a0a5796 in blk_insert_bs (blk=blk@entry=0x55ca4c832c60,
bs=bs@entry=0x55ca4c7a7150, errp=errp@entry=0x7ffdba216258)
at ./block/block-backend.c:728
#4 0x000055ca4a0c6347 in nbd_export_new (bs=bs@entry=0x55ca4c7a7150,
dev_offset=dev_offset@entry=0, size=size@entry=-1,
nbdflags=<optimized out>, close=close@entry=0x0,
writethrough=writethrough@entry=false, on_eject_blk=0x55ca4c7a6ef0,
errp=0x7ffdba216258)
at ./nbd/server.c:1091
#5 0x000055ca49e7be85 in qmp_nbd_server_add (device=0x55ca4c8501b0
"drive-virtio-disk0", has_writable=<optimized out>,
writable=<optimized out>, errp=0x7ffdba216258) at ./blockdev-nbd.c:192
#6 0x000055ca49e89625 in qmp_marshal_nbd_server_add (args=<optimized out>,
ret=<optimized out>, errp=0x7ffdba2162c8) at qmp-marshal.c:2198
#7 0x000055ca4a11e387 in do_qmp_dispatch (errp=0x7ffdba2162c0,
request=0x55ca4cd57c70, cmds=0x55ca4a78aee0 <qmp_commands>)
at ./qapi/qmp-dispatch.c:104
#8 qmp_dispatch (cmds=0x55ca4a78aee0 <qmp_commands>,
request=request@entry=0x55ca4cd57c70) at ./qapi/qmp-dispatch.c:131
Lets extract the nbd call and try to do this without a migration.
qemu-system-x86_64 -S -enable-kvm -m 512 -no-user-config -nodefaults -monitor
stdio -drive
file=/var/lib/uvtool/libvirt/images/kvmguest-bionic-normal.qcow,format=qcow2,if=none,id=drive-virtio-disk0
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
qemu-system-x86_64: -drive
file=/var/lib/uvtool/libvirt/images/kvmguest-bionic-normal.qcow,format=qcow2,if=none,id=drive-virtio-disk0:
Failed to get "write" lock
Haaaaaaar - I know whats going on.
This is not properly unshared anymore.
The two containers use the same backing FS and therefore the second can't lock
it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764373
Title:
copy-storage migrations fail on nbd-server-add
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1764373/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
