Bug 1995455 - Increase the maximum number of CPU sockets
Summary: Increase the maximum number of CPU sockets
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.4.7
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.5.0
: 4.5.0
Assignee: Milan Zamazal
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-19 07:34 UTC by Arik
Modified: 2022-05-26 07:37 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-4.5.0
Doc Type: Enhancement
Doc Text:
The limit of maximum 16 CPU sockets has been removed in cluster versions >= 4.6. It is now possible to use any number of CPU sockets, up to the number of maximum vCPUs. Before using a high number of CPU sockets, check if the guest OS is compatible with such a configuration.
Clone Of:
Environment:
Last Closed: 2022-05-03 06:46:19 UTC
oVirt Team: Virt
Embargoed:
sbonazzo: ovirt-4.5+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-43063 0 None None None 2021-08-19 07:35:09 UTC
oVirt gerrit 116107 0 None None None 2021-08-19 07:35:05 UTC

Description Arik 2021-08-19 07:34:15 UTC 
Remove the limit of 16 CPU sockets on the guest CPU topology
Comment 1 Sandro Bonazzola 2022-03-16 15:46:12 UTC 
git tag --contains a4c08581377d669300ee35d1cd6406f0b37f25f0
ovirt-engine-4.5.0
ovirt-engine-4.5.0_alpha1
Comment 2 Nikolai Sednev 2022-05-02 11:32:03 UTC 


Tested the UI on latest ovirt-engine-setup-4.5.0.6-617.f240a1e6e1d7.3.el8ev.noarch:
- create a VM with cluster level < 4.6, set its vCPU count to 16, with topology 16 sockets - 1 core - 1 thread. the max vCPU count when the VM is started should be 16 (the old socket limit applies).
- when the VM is switched to cluster level >= 4.6 the max vCPU limit should raise to 32.

The UI responds fine, need to test if that works on host with at least 32 cores, moving back to Nisim.
Comment 3 Nikolai Sednev 2022-05-02 11:33:32 UTC 
Created attachment 1876455 [details]
4.5 cluster level supports up to 16 vCPUs
Comment 4 Nikolai Sednev 2022-05-02 11:34:41 UTC 
Created attachment 1876456 [details]
4.6 and above cluster level is unlimited to 16 vCPUs
Comment 5 Nisim Simsolo 2022-05-02 13:13:00 UTC 
Verified:
ovirt-engine-4.5.0.5-0.7.el8ev
vdsm-4.50.0.13-1.el8ev.x86_64
qemu-kvm-6.2.0-11.module+el8.6.0+14707+5aa4b42d.x86_64
libvirt-daemon-8.0.0-5.module+el8.6.0+14480+c0a3aa0f.x86_64

Verification scenario:
1. Run the next VMs with 64 virtual CPUs (2 virtual sockets, 16 cores per virtual socket and 2 threads per core):
- RHEL8 VM Q35/SecureBoot
- RHEL8 VM Q35/UEFI
- RHEL8 VM Q35/BIOS
- RHEL9 VM Q35/SecureBoot
- RHEL9 VM Q35/UEFI
- RHEL9 VM Q35/BIOS
- RHEL8 VM I400FX/BIOS
- Windows VM Q35/SecureBoot
- Windows VM Q35/UEFI
- Windows VM Q35/BIOS
- Windows VM I440FX/BIOS
2. For each VM running, verify console is showing boot screen and after boot it shows VM OS, mouse and keyboard are functioning and inside the VM verify that the correct CPUs (64, 2/16/2) are set.
Comment 6 Sandro Bonazzola 2022-05-03 06:46:19 UTC 
This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022.

Since the problem described in this bug report should be resolved in oVirt 4.5.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.