Bug 2218193

Summary:	VMI with x86_Icelake fail when mpx feature is missing
Product:	Container Native Virtualization (CNV)	Reporter:	Barak <bmordeha>
Component:	Virtualization	Assignee:	Barak <bmordeha>
Status:	CLOSED ERRATA	QA Contact:	Kedar Bidarkar <kbidarka>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.11.4	CC:	acardace
Target Milestone:	---
Target Release:	4.11.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	v4.11.5-67	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-12 13:06:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Barak 2023-06-28 12:06:22 UTC

Description of problem:
There is a QEMU && libvirt conflict regarding which features are needed to run a vmi with named CPU model.
To solve this we need to support a CPU model only if we have the requirements by both libvirt and qemu.



Version-Release number of selected component (if applicable):


How reproducible:
Try to create VMI with `x86_Icelake` when mpx is missing on the nodes.

Steps to Reproduce:
1.
2.
3.

Actual results:
VMI creation will fail with libvirt error

Expected results:
The node shouldn't have label for `x86_Icelake` in that case and virt-launcher pod shouldn't be scheduled.

Additional info:
For more information : https://wiki.qemu.org/Features/CPUModels in "Getting information about CPU models" section

Comment 1 Kedar Bidarkar 2023-07-24 10:04:32 UTC

Verification requires very specific hardware, we don't have such servers in QE.

It is covered by unit tests, so moving it to Verified state.

Comment 7 errata-xmlrpc 2023-09-12 13:06:18 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Virtualization 4.11.6 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:5103