Hi Pavel, I've found a blog post, which claims otherwise, here's excerpt from it:
The <qemu:commandline> domain XML tagThere is a special namespace for QEMU-specific tags in libvirt domain XML. You cannot use QEMU-specific tags without first declaring the namespace. To enable it use the following: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> Now you can *add command-line arguments* to the QEMU invocation. For example, to load an option ROM with -option-rom: <qemu:commandline> <qemu:arg value='-option-rom'/> <qemu:arg value='path/to/my.rom'/> </qemu:commandline> It is also possible to *add environment variables* to the QEMU invocation: <qemu:commandline> <qemu:env name='MY_VAR' value='my_value'/> </qemu:commandline> Can you please comment regarding this approach? Regards Narunas On Tue, Jun 20, 2017 at 10:44 AM, Pavel Hrdina <[email protected]> wrote: > On Tue, Jun 20, 2017 at 10:20:01AM +0100, Narunas Krasauskas wrote: > > Is there a way to load *fw_cfg* file in *virt-manager* (v1.4.1)? > > > > On the plain *QEMU* command line I can do it like so: > > > > -fw_cfg name=opt/com.coreos/config,file=some/file.json > > > > I cannot find equivalent option in the *virt-manager*. > > > > Thanks, Narunas > > Hi, no there is no way to use *fw_cfg* in virt-manager. Virt-manager > controls libvirt an this is not even implemented in libvirt. > > To allow setting it via virt-manager/virt-xml/virt-install it needs > to be implemented in libvirt as well. > > Feel free to create a Bug to track this feature, both libvirt and > virt-manager uses this site to track bugs [1]. As a product you should > select "Virtualization Tools" and component is libvirt or virt-manager. > > Pavel >
_______________________________________________ virt-tools-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-tools-list
