Bug 1856522

Summary:	Expose new CPU models/versions from QEMU automatically
Product:	Red Hat Enterprise Linux 9	Reporter:	Eduardo Habkost <ehabkost>
Component:	libvirt	Assignee:	Tim Wiederhake <twiederh>
libvirt sub component:	General	QA Contact:	Luyao Huang <lhuang>
Status:	CLOSED DEFERRED	Docs Contact:
Severity:	high
Priority:	high	CC:	ailan, berrange, chayang, dyuan, fjin, jdenemar, jsuchane, kchamart, lmen, mtessun, nanliu, qizhu, twiederh, virt-maint, xiaohli, xuwei, xuzhang, yafu, yalzhang, yuhuang
Version:	9.0	Keywords:	FutureFeature, Reopened, Triaged
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-12 09:50:34 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1697663, 1856515
Bug Blocks:	1974560, 2034454, 2109643

Description Eduardo Habkost 2020-07-13 19:55:30 UTC

This is a feature request:

When we add a new CPU model or a new version of a CPU model to QEMU, we need to manually add a corresponding copy of that CPU model definition to libvirt's cpu_map.xml.  This increases the effort and time required to ship important bug fixes to customers (e.g. when a bug fix requires the introduction of a new CPU model version).

libvirt should be able to expose new CPU models from QEMU through its existing CPU model API automatically, without the need to ship a cpu_map.xml update.

Comment 2 John Ferlan 2021-09-09 15:47:16 UTC

Bulk update: Move RHEL-AV bugs to RHEL8.

Added RHV as dependent product and left in RHEL8. If a Resolution/Testing is required for RHEL9, then a clone will need to be created.

Comment 4 RHEL Program Management 2022-01-13 07:27:58 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 8 Tim Wiederhake 2022-07-18 09:06:05 UTC

See https://listman.redhat.com/archives/libvir-list/2022-June/232626.html for a proposal to address this

Comment 9 John Ferlan 2022-07-20 11:09:03 UTC

NB: Removed RHV as dependent product since this is a RHEL9 issue

Comment 11 Daniel Berrangé 2022-08-10 11:21:58 UTC

(In reply to Tim Wiederhake from comment #8)
> See https://listman.redhat.com/archives/libvir-list/2022-June/232626.html
> for a proposal to address this

Note, this proposal is incomplete

  https://listman.redhat.com/archives/libvir-list/2022-July/232891.html

Comment 14 Jaroslav Suchanek 2023-07-12 09:50:34 UTC

Lets close this one correspondingly to qemu-kvm counterpart (bug 1697663). We will create new set of feature requests, once we get better understanding of what is actually the desired goal and how to implement it through the stack. Thanks.

Comment 15 Red Hat Bugzilla 2023-11-10 04:25:03 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days