Bug 2083302 - CPU pinning not replaced when resuming hibernated VM with CPU policy 'Dedicated'
Summary: CPU pinning not replaced when resuming hibernated VM with CPU policy 'Dedicated'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: 4.50
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.5.1
: ---
Assignee: Tomáš Golembiovský
QA Contact: Polina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-09 16:04 UTC by Tomáš Golembiovský
Modified: 2022-06-23 05:54 UTC (History)
3 users (show)

Fixed In Version: vdsm-4.50.1.2
Clone Of:
Environment:
Last Closed: 2022-06-23 05:54:58 UTC
oVirt Team: Virt
Embargoed:
pm-rhel: ovirt-4.5?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt vdsm pull 215 0 None Merged virt: use proper CPU pinning when resuming hibernated VM 2022-06-07 13:33:00 UTC
Red Hat Issue Tracker RHV-45994 0 None None None 2022-05-09 16:21:57 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.