[ovirt-users] Re: Correct workflow for modifying engine vm.conf file

Hello, I would like to know a way to interact and modify in a "supported"/working way the vm.conf file on shared storage that contains details for the engine vm and I think is the base to dynamically generate the /var/run/ovirt-hosted-engine-ha/vm.conf In the past it was possible to temporarily modify the file under /var/run (or copy to another location) and start engine with it, but now it seems it doesn't work and that the file is continuously updated/refreshed Eg on engine storage domain on a lab with oVirt 4.4. beta4 I have the tar file [root@novirt2 ~]# tar tvf /rhev/data-center/mnt/glusterSD/novirt2st.storage.local\:_engine/7c9397f5-859b-4fba-bcc5-4ecbd454a189/images/530490b0-935e-46a8-84f6-6cd6618c6f0d/2e0f414c-2589-4545-a0a4-3bfed24ef3fc -rw-r--r-- root/root 181 2020-04-19 15:04 broker.conf -rw-r--r-- root/root 2777 2020-04-19 15:04 fhanswers.conf -rw-r--r-- root/root 1076 2020-04-19 15:04 hosted-engine.conf -rw-r--r-- root/root 6 2020-04-19 15:04 version -rw-r--r-- root/root 1359 2020-04-19 15:04 vm.conf [root@novirt2 ~]# And its vm.conf has: cpuType=Cascadelake-Server,+md-clear,+mds-no,-hle,-rtm,+tsx-ctrl,+arch-capabilities I would like to modify it and remove the "+tsx-ctrl" flag. Is there anything in the database that generates modification in the file on shared storage and then on the directory under /var/run? Or how is all the workflow managed to generate at the end the xml file to use to start the engine vm? What is that initially determines how to populate the cpuType in vm.conf at all? Thanks, Gianluca