On 3/28/19 6:22 PM, Dev Ops wrote:
Figured out that Ovirt doesn't allow for virsh to edit XML files and have them
be persistent through reboots. I needed to edit the SMBIOS settings in an XML
of a VM. Once the VM is off the XML is gone. VDSM apparently builds the XML's
out on boot up. To get this working this has to be done with VDSM hooks and
that only took me 8 hours to figure out and sort out. :)
...snip
Refresh the Capabilities in the UI for the host in question. I could then build
out a VM and set the Custom Properties for smbios to this:
{'product': 'KVM'}
You know, my VM shows SMBIOS 0x0100 System Information Manufacturer:
oVirt and Product Name: oVirt Node
Without me doing anything.
Not saying you don't have a particular need, just saying in case
somebody wanted to know.
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/4VHZHYFBOGDUTH2V3SYWSC77DQ35MJK2/
