The following at least seems close to your error message, try to look around from there if you can: $ virsh qemu-monitor-command --hmp zesty-test-log 'device_add virtio-blk-pci,drive=drive-virtio-disk1,id=mydisk1' Property 'virtio-blk-device.drive' can't find value 'drive-virtio-disk1'
Of course I don't have anything like that device - so for me that is fine. This is not bad: https://wiki.ubuntu.com/QemuDiskHotplug#A.27drive_add.27_example An example would be: #1 create disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.img 1G $ sudo chown libvirt-qemu:kvm /var/lib/libvirt/images/test.img #2 add to qemu # you might need to either teach your apparmor about it, or disable it $ virsh qemu-monitor-command --hmp zesty-test-log 'drive_add 0 if=none,file=/tmp/test.img,format=raw,id=disk1' #3 add it to the guest $ virsh qemu-monitor-command --hmp zesty-test-log 'device_add virtio-blk-pci,drive=disk1,id=myvirtio1' #1 in your case certainly is rbd, #2/#3 commands is what you need to find and debug/analyze. A failing #3 like in your error might indicate a failing #2 (drive_add failed, so it can't be found). You can check the proper state if your device is there after #2 with $ virsh qemu-monitor-command --hmp zesty-test-log 'info block' -- 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
