Hi, that makes sense. Due to the fail to connect on the drive_add (which matches the -drive) the "drive" ID was not populated. So later when something wants to refer to that ID it gets that issue. BTW - is your error on boot or later on hotplug?
The converted command looks reasonable to me, at least from just reading it. Did you try $ virsh qemu-monitor-command --hmp zesty-test-log 'info block' on the guest booted that way if it had the drive with the id drive-virtio-disk1? Hmm I need to setup a rbd setup. Lets hope there is something simple for me ... You are driving this from openstack/ceph right? -- 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
