vdsm-hook-cpuflags hook is sort-of-supported (the hook is, not a random flag of course) and so it does deserve a predefined property in webadmin Alternatively, we can keep it the way it is and just update doc of that hook (it doesn't have a README today at all)
*** Bug 1563812 has been marked as a duplicate of this bug. ***
So if I want to enable the cpuflags hook and also account for the specific SAP flags, I have to do both "cpuflags" -> "SAP" and "sap_agent" -> "true" under "VM" -> "Edit" -> "Custom Properties"? In other words, it won't suffice to set only one of these properties?
It is sufficient, if the hook is installed, to only set "sap_agent". If additional cpu flags are specified (or some of them are duplicated), the hook calculates the proper subset to add to the VM.
Verified on: vdsm-4.20.26-1.el7ev.x86_64 vdsm-hook-cpuflags-4.20.26-1.el7ev.noarch ovirt-engine-4.2.3.2-0.1.el7.noarch Steps: 1. install vdsm-hook-cpuflags on the host 2. create a vm. 3. set the vm custom properties with sap_agent - true. 4. start the vm. Result: The vm started on the desired host in virsh dumpxml it shows: <ovirt-vm:custom> <ovirt-vm:sap_agent>true</ovirt-vm:sap_agent> </ovirt-vm:custom> and from vdsm-client VM getInfo: "custom": { "sap_agent": "true" }, under devices: "iface": "ide", "name": "hdc", "vm_custom": { "sap_agent": "true" }, "name": "vda", "vm_custom": { "sap_agent": "true" }, "name": "vdzz", "vm_custom": { "sap_agent": "true" },
This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.3 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.