Steps to reproduce:
1) Edit VM in XML view
2) Set CPU count to anything other than 1 (that is 2, 3, 4 ... ) - will refer to this count as X bellow
3) Remove the cputune section - no cpu pinning (maybe not needed to reproduce, but needed in my setup)
4) Set cpu topology to <topology sockets='X' cores='1' threads='1'/> (maybe not needed to reproduce, but needed in my setup)
5) Save the config
6) Edit the VM again, but this time in form view
7) Set VNC password
8 ) Save the config
During second edit the CPU config has not been changed.
Expected results:
- CPU config should remain as configured in first edit
Actual results:
- CPU config is changed to
<vcpu placement='static'>1</vcpu>
<topology sockets='1' cores='1' threads='1'/>
This might be an existing issue and not specific to this release.
If the edits are reversed (first password, then cpu), the password is not present in the XML.
I see two possibilities:
1) Allow the form view to specify CPU configuration without pinning and also topology
or
2) If some section is not changed in form view, then don't update it when saving the VM config.
But in the end, you are the experts. 