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

Bug 1874519

Summary: Block CPU hotplug on UEFI
Product: [oVirt] ovirt-engine Reporter: Arik <ahadas>
Component: BLL.VirtAssignee: Liran Rotenberg <lrotenbe>
Status: CLOSED CURRENTRELEASE QA Contact: Beni Pelled <bpelled>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.4.2CC: bpelled, bugs
Target Milestone: ovirt-4.4.3Flags: pm-rhel: ovirt-4.4+
Target Release: 4.4.3.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.3.2-0.19 Doc Type: Bug Fix
Doc Text:
Previously, when hot-plugging CPU to a VM that uses UEFI BIOS, it would fail causing a VM reboot. Now, the engine will prevent the hot-plug CPU action in such case.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-11 06:42:10 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 2020-09-01 14:26:13 UTC
As long as CPU hotplug doesn't work (bz 1834250) we should block it on the engine side (even if it doesn't lead to VM crashes anymore).

Comment 1 Beni Pelled 2020-09-14 14:47:10 UTC
Verified with:
- ovirt-engine-4.4.3.2-0.19.el8ev.noarch
- libvirt-6.6.0-4.module+el8.3.0+7883+3d717aa8.x86_64
- vdsm-4.40.29-1.el8ev.x86_64


Verification steps:
1. Create a VM with UEFI and start it
2. Add CPU (hotplug)

Result:
- The CPU isn't added and the following message appears in Event logs: 'Failed to hot set number of CPUS to VM bpelled_uefi_vm. Underlying error message: Hot plugging a CPU is not supported for a guest with UEFI.'

Comment 2 Sandro Bonazzola 2020-11-11 06:42:10 UTC
This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.3 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.