I assume it constructs some "drive_add" command like "drive_add 0 if=none,file=/tmp/test.img,format=raw,id=drive-virtio-disk1" but for the rbd device.
There are examples here: https://wiki.ubuntu.com/QemuDiskHotplug#A.27drive_add.27_example 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672367 Title: libvirtError: internal error: unable to execute QEMU command 'device_add': Property 'virtio-blk-device.drive' can't find value 'drive-virtio-disk1' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1672367/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
