> 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=&quot;ThinkStation P300&quot;,serial=S4M62281,uuid=1ecefe02-f1b6-4bf8-a925-c9f4ae512209,sku=LENOVO_MT_30AH,family=P300'/> </qemu:commandline> </domain>

On Mon, May 15, 2023 at 20:14:58 +0200, lejeczek wrote: > > On 15/05/2023 19:14, Marc wrote: >>> 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=&quot;ThinkStation P300&quot;,serial=S4M62281,uuid=1ecefe02-f1b6-4bf8-a925-c9f4ae512209,sku=LENOVO_MT_30AH,family=P300'/> >> </qemu:commandline> >> </domain> > yes, for those who might stumble upon this/similar - it turns out to be the > structure declaration in xml >   <qemu:commandline> > VS >   <commandline> > of whose the latter _works_ ! on centos 9 with > libvirt-daemon-9.0.0-7.el9.x86_64 but not the former. > > @devel - should this go as BZ report into bugzilla? Did you declare the appropriate XML namespace?: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> https://www.libvirt.org/drvqemu.html#pass-through-of-arbitrary-qemu-commands

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