Bug 1995455
| Summary: | Increase the maximum number of CPU sockets | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Arik <ahadas> |
| Component: | BLL.Virt | Assignee: | Milan Zamazal <mzamazal> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Nisim Simsolo <nsimsolo> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.4.7 | CC: | bugs, emarcus, nsednev, nsimsolo |
| Target Milestone: | ovirt-4.5.0 | Keywords: | ZStream |
| Target Release: | 4.5.0 | Flags: | sbonazzo:
ovirt-4.5+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-03 06:46:19 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: | |||
|
Description
Arik
2021-08-19 07:34:15 UTC
git tag --contains a4c08581377d669300ee35d1cd6406f0b37f25f0 ovirt-engine-4.5.0 ovirt-engine-4.5.0_alpha1 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. Created attachment 1876455 [details]
4.5 cluster level supports up to 16 vCPUs
Created attachment 1876456 [details]
4.6 and above cluster level is unlimited to 16 vCPUs
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. 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. |