Bug 1505927

Previously, it was difficult to configure a virtual machine (VM) to run with high performance workloads via the Administration Portal as it involved understanding and configuring a large number of settings. In addition, several features that were essential for improving the VM's performance were not supported at all, for example, huge pages and IO thread pinning.

In this release, a new optimization type called High Performance is available when creating VMs. It is capable of running a virtual machine with the highest possible performance with performance metrics as close to bare metal as possible. When the customer selects High Performance optimization, the VM is automatically configured with a set of recommended configuration settings for reaching the best efficiency. In addition, a set of recommended manual settings is displayed. 

Feature page: https://ovirt.org/develop/release-management/features/virt/high-performance-vm/

1. Add new "Optimized for" type to New VM window called High Performance
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html-single/virtual_machine_management_guide/#Virtual_Machine_General_settings_explained

2. A High Performance Template or Pool can be created in the same way as a VM. However not all fields are identical.

3. Document how configuration changed by the Instance Type may override the VM High Performance configuration.

4. Document list of changes that are displayed to the user upon creation:

- A list of validations and suggested manual configuration changes are displayed in a pop-up window on save and the user can choose if to accept and perform the changes before saving or ignore them. There are currently 4 settings. See feature page.

- A list of configuration changes will be applied automatically (and the user can cancel before saving via WebAdmin UI). Currently 12 settings. See feature page. User should know what has changed. 

5. A new icon is displayed for this new High Performance VM type, left to the VM name, and the VM type will also be displayed in the "General" sub-tab.

6. Limitations. This feature doesn't work on all cluster levels (since huge pages are not supported before oVirt 4.2). Plus other limitations not in feature page at time of writing.

7. a new 'High Performance' VM type should be added to VM/pool/Template creation/editing APIs. Each parameter must be configured manually - no automatic configuration.