For providing high performance VMs, a new Profile is requested for adding a configuration for this type of VMs.
The idea is to have VMs that have performance metrics as close to bare metal as possible for running huge VMs.
This profile should be able to check available and configured hugepages and run the VM in these Hugepages, if possible.
Initial thoughts on the needed functionality in the High Performance Profile:
- Headless (Serial Console or VNC only)
- Disable Soundcard
- Host CPU passthrough
- Backed by Hugepages (2M or 1G as configured at Hypervisor Boot Time)
- 1 IOThread pinned to the CPU doing the IO on the Host
alternatively pinned to CPU#0 as this is typically the one.
- emulatorpin should also be pinned to the same CPU(s) as the iothread
- If CPU supports it, forward also the invtsc flag to the VM
- Disable KSM and Ballooning for a cluster running these types of VMs.
- Do vNUMA with appropriate NUMA pinning according to the Host NUMA topology.
This VM will no longer be migratable. For adding this feature another BZ will be opened.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
profile == a user configurable preset in New/Edit VM dialog in addition to current Server/Desktop
see also https://trello.com/c/MHRDD8ZO
The hugepages part of the feature is ready in master - please start working on a test plan.
(In reply to Martin Polednik from comment #4)
> The hugepages part of the feature is ready in master - please start working
> on a test plan.
All issues are in except io + emulator threads pinning which is posted but not merged yet (waiting for code review), so I will mark this bug as MODIFIED so that all other issues will be tested.
Please don't test iothread + emulator threads pinning yet.
Verified on rhvm-4.2.0-0.5.master.el7.noarch
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.
Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.
If the solution does not work for you, please open a new bug report.