On Tue, May 25, 2021 at 4:50 PM Don Dupuis <
dondster@gmail.com> wrote:
>
> I created a high performance vm and everything is fine. I stop the virtual machine and make edits to it and again runs correctly. I shutdown the vm and click the edit tab to look at what I changed and it is now back to the defaults and my edits are gone. Is this now the intended result. I was using the same settings in 4.3 and never exhibited this behavior. What I have observed so for is that I disabled Headless, disabled cpu pinning, and changed numa config. When I shutdown the vm, they revert to default of Headless enabled, cpu pinning is set and the numa config changed. This is not what I expect to happen. Has anyone else noticed this behavior?
>
Hi,
I tried to reproduce it (without update):
1. Create a VM with HP type.
2. Set it with console.
3. Edit the VM again, click OK.
4. Edit the VM to see the configuration.
Everything sticks to the first configuration.
Note that if you change the VM type to server/desktop and move it again to High Performance, some configurations will change.
In 4.4.5 we added the auto pinning feature, to high performance VMs we automatically set it to existing - which overrides the cpu pinning and numa configuration of the VM.
This behavior executed each time you edited the VM in the UI, it wouldn't change the headless, only the CPU pinning and NUMA.
However, in 4.4.6.6, we fixed a bug[1] to prevent this behavior to some extent. If you change the type, it will change the policy, but if the VM is already configured as High Performance and you didn't change it, it will leave it as is.
The question would be if you change the VM type? If so, it is expected.