On 16/05/2023 10:56, Michal Pr?vozn?k wrote:> 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
>
this gets more neat every minute one learns more of libvirt.
So, I'd take this chance and ask - can we pass paramas to
the kernel, like APPEND?
I'm thinking.. would be great co have net ifaces configured
that(some) way.
many thanks, L