virsh edit vm not saving after reboot
I am trying to get Cisco ISE installed into Ovirt. I was told I needed to do a virsh edit on the vm and change a line in the smbios settings. This is all simple enough. After a reboot or shutdown/restart the settings revert back to what they were before. A dump of the XML in fact shows the original settings that I had changed. Since I can't edit the file while the VM is off I am not sure how to save this config change. My issue is similar to this: https://access.redhat.com/discussions/2720821 I have been reading and digging around with no luck. I just can't seem to make this change static. Thanks!
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. :) If it helps I had to do the following on the engine: engine-config -s "UserDefinedVMProperties=smbios=.*" systemctl restart ovirt-engine.service KVM hosts I did this: yum -y localinstall https://buildlogs.centos.org/centos/7/virt/x86_64/ovirt-4.2/vdsm-hook-smbios... 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'} https://www.ovirt.org/documentation/admin-guide/appe-VDSM_and_Hooks.html https://www.ovirt.org/develop/developer-guide/vdsm/hook/smbios.html https://www.ovirt.org/develop/developer-guide/vdsm/hooks.html
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.
participants (2)
-
Christopher Cox -
Dev Ops