If you can track down the command it executes we could take a deeper look via.
$ virsh qemu-monitor-command --hmp <domain> '<command> [...]'
Syntax would be like:
device_add driver[,prop=value][,...] -- add device, like -device on the command line
Something like this maybe (still incomplete):
virsh qemu-monitor-command --hmp zesty-test-log 'device_add virtio-blk-device,file=/tmp/test.img,format=raw,id=drive-virtio-disk1'
Sorry this is far from human friendly as it is not meant for humans.
But if you can intercept what your tooling is submitting we could eliminate all of the stack from the equation and take a look.
I assume it constructs some "drive_add" command like file=/tmp/ test.img, format= raw,id= drive-virtio- disk1" but for the rbd device.
"drive_add 0 if=none,
There are examples here: https:/ /wiki.ubuntu. com/QemuDiskHot plug#A. 27drive_ add.27_ example
If you can track down the command it executes we could take a deeper look via. command --hmp <domain> '<command> [...]'
$ virsh qemu-monitor-
Syntax would be like: ,prop=value] [,...] -- add device, like -device on the command line
device_add driver[
Something like this maybe (still incomplete): command --hmp zesty-test-log 'device_add virtio- blk-device, file=/tmp/ test.img, format= raw,id= drive-virtio- disk1'
virsh qemu-monitor-
Sorry this is far from human friendly as it is not meant for humans.
But if you can intercept what your tooling is submitting we could eliminate all of the stack from the equation and take a look.