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

Bug 2083302

Summary: CPU pinning not replaced when resuming hibernated VM with CPU policy 'Dedicated'
Product: [oVirt] vdsm Reporter: Tomáš Golembiovský <tgolembi>
Component: CoreAssignee: Tomáš Golembiovský <tgolembi>
Status: CLOSED CURRENTRELEASE QA Contact: Polina <pagranat>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.50CC: ahadas, bugs, dfodor
Target Milestone: ovirt-4.5.1Flags: pm-rhel: ovirt-4.5?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: vdsm-4.50.1.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-23 05:54:58 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 Tomáš Golembiovský 2022-05-09 16:04:40 UTC 
When restoring a hibernated VM VDSM discards domain XML provided by engine and restores the original domain XML saved during hibernation. While this is normally correct it presents a problem for dedicated VMs. Stored CPU pinning cannot be used because the CPUs may be already dedicated to different VM or may not be available on the host at all. VDSM needs to remove the stored CPU pinning from domain XML and replace it with pinning from XML passed by engine or provide another method to get new pinning from engine.
Comment 1 Polina 2022-06-19 10:39:59 UTC 
verified on ovirt-engine-4.5.1.2-0.11.el8ev.noarch according to the attached https://polarion.engineering.redhat.com/polarion/redirect/project/RHEVM3/workitem?id=RHEVM-28104
Comment 2 Sandro Bonazzola 2022-06-23 05:54:58 UTC 
This bugzilla is included in oVirt 4.5.1 release, published on June 22nd 2022.
Since the problem described in this bug report should be resolved in oVirt 4.5.1 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.