Hello, I also tryed to unprotect "libvirt driver options for images" and "instance config data" metadata definitions Then I associated them to flavors. With the above configuration I can define . os_require_quiesce='yes' and hw_qemu_guest_agent='yes' in a flavor bu starting an instance from a volume using that flavor did not solved the issue: qemu-guest agent did not work. It works only when an instance is created from an image with the above metadata. Ignazio Il giorno gio 7 feb 2019 alle ore 12:53 Sean Mooney <smooney@redhat.com> ha scritto:
Hello, is it possible to force metadata for instances like the following ? hw_qemu_guest_agent='yes' os_require_quiesce='yes'
I know if an instance is created from an image with the above metadata
On Thu, 2019-02-07 at 12:22 +0100, Ignazio Cassano wrote: the quemu-guest-agent works, but sometimes
instances can start from volumes ( for example after a cnder backup). if you are using a recent version of cinder/nova the image metadata is copied to the volume. i don't know if that is in queens or not but the only other way to force it that i can think of would be via the flavor. unfortunately the guest agnet is not supported in the flavor
https://github.com/openstack/glance/blob/master/etc/metadefs/compute-libvirt...
Regards Ignazio