Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1780936

Summary: Graphical Console remains enabled when VM type is set as HP VM with the rest API. Please implement
Product: [oVirt] ovirt-engine Reporter: Polina <pagranat>
Component: BLL.VirtAssignee: Liran Rotenberg <lrotenbe>
Status: CLOSED NOTABUG QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.3.7.0CC: ahadas, bugs, lrotenbe, rbarry, rdlugyhe
Target Milestone: ovirt-4.4.1Flags: pm-rhel: ovirt-4.4+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, if you used the REST API to set the VM Type to `high_performance`, it failed to enable `Headless Mode`. The current release fixes this issue: Using the REST API to set the VM Type to `high_performance` enables headless mode where the virtual machine has no video type or graphics protocol.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-03 13:02:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 1 Steven Rosenberg 2019-12-24 17:15:51 UTC 
Notes for testing:

There were many scenarios that did not work concerning HP, console disabling and Graphics Devices availability.

These were the following scenarios handled and tested:

1. Creating an HP VM from the Webadmin
2. Creating an HP VM from the REST API
3. Creating a non-HP VM from the Webadmin
4. Creating a non-HP VM from the REST API
5. Update the VM Type from the Webadmin from HP to non HP
6. Update the VM Type from the Webadmin from non HP to HP
7. Update the VM Type from the REST API from HP to non HP
8. Update the VM Type from the REST API from non HP to HP
9. Tested Template creation and Make VM with HP VM Type
10. Tested Template creation and Make VM with non HP VM Type 

Expected results are:

1. For HP the console should stay disabled when launching a VM and no Graphics Devices should be listed in the Device Lists, while the opposite would be valid for non HP VMs such as server and desktop.
Comment 2 Steven Rosenberg 2019-12-30 08:20:35 UTC 
Feature pages for headless [1] and High Performance [2] provide for a manual solution.

Further discussion on whether to automate, warn, or keep the manual approach is welcome.

[1] https://www.ovirt.org/develop/release-management/features/virt/headless-vm.html

[2] https://www.ovirt.org/develop/release-management/features/virt/high-performance-vm.html
Comment 3 Liran Rotenberg 2020-06-03 13:02:07 UTC 
Hi,
According to comment #2, and further discussions, we are not going to change the behavior of the API for High Performance VM.
The reason is, with the API you can send partial VM configuration.
As such, it may cause unwanted changes to VMs if we will make the API changing something that is not set in the API call(for example, making the VM headless).

For safety, by design it was decided to split the API calls. Making it automated can bring more harm than use.
Comment 4 Arik 2020-06-07 07:13:01 UTC 
Just to emphasis on comment 3, the need to issue multiple calls from REST-API in order to create a headless HP VM is by design.
The inability to run non-headless HP VMs on PPC is addressed by bz 1839398.