Hi guys. I have a domain definition with this: ... ? <qemu:commandline> ??? <qemu:arg value='-fw_cfg'/> ??? <qemu:arg value='name=opt/com.coreos/config,file=/00-VMs/oshift1node.ign'/> ? </qemu:commandline> </domain> at the bottom of xml. 'virsh' creates domain a okey but in VM I do not see ignition happened - it's fedora coreos - and when I dumpxml running domain, then indeed those bits, show above, are not there. I'd grateful for any/all thoughts shared on - what is not/happening there. Is there something else which is a prerequisite to 'qemu:commandline' but if yes and I'm missing those, why would not then 'virsh' and/or 'virtqemud' say something? many thanks, L. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20230515/3db63f71/attachment.htm>
> Is there something else which is a prerequisite to 'qemu:commandline' > but if yes and I'm missing those, why would not then 'virsh' and/or > 'virtqemud' say something?No what you have looks ok, this is what I have as a test and is working ok. You can try and these to see if something is shown in the guest. <qemu:commandline> <qemu:arg value='-cpu'/> <qemu:arg value='host,hv_time,-hypervisor'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=0,vendor=LENOVO,version=FBKTB4AUS,date=07/01/2015,release=1.180'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=1,manufacturer=LENOVO,product=30AH001GPB,version="ThinkStation P300",serial=S4M62281,uuid=1ecefe02-f1b6-4bf8-a925-c9f4ae512209,sku=LENOVO_MT_30AH,family=P300'/> </qemu:commandline> </domain>
On 5/15/23 19:07, lejeczek wrote:> Hi guys. > > I have a domain definition with this: > ... > ? <qemu:commandline> > ??? <qemu:arg value='-fw_cfg'/> > ??? <qemu:arg > value='name=opt/com.coreos/config,file=/00-VMs/oshift1node.ign'/> > ? </qemu:commandline> > </domain> > > at the bottom of xml. > 'virsh' creates domain a okey but in VM I do not see ignition happened - > it's fedora coreos - and when I dumpxml running domain, then indeed > those bits, show above, are not there. > > I'd grateful for any/all thoughts shared on - what is not/happening there. > Is there something else which is a prerequisite to 'qemu:commandline' > but if yes and I'm missing those, why would not then 'virsh' and/or > 'virtqemud' say something? > > many thanks, L.No need for using <qemu:commandline/> as this is well configurable via domain XML (for ~3 years): https://libvirt.org/formatdomain.html#smbios-system-information <sysinfo type='fwcfg'> <entry name='opt/com.example/name'>example value</entry> <entry name='opt/com.coreos/config' file='/tmp/provision.ign'/> </sysinfo> Michal