This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1879200 - libvirt should invalidate QEMU capabilities cache when kvm module parameters change
Summary: libvirt should invalidate QEMU capabilities cache when kvm module parameters ...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Jiri Denemark
QA Contact: Luyao Huang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-15 16:20 UTC by Jiri Denemark
Modified: 2023-09-22 12:19 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-22 12:19:34 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-7031 0 None Migrated None 2023-09-22 12:19:30 UTC

Description Jiri Denemark 2020-09-15 16:20:11 UTC 
Description of problem:

Removing kvm_intel model and inserting it back with different parameters can
influence QEMU capabilities, such as CPU features available on the host. For
example, changing nested or pt_mode parameters may change availability of vmx
or intel-pt features respectively. The nested parameter is already checked by
libvirt in virQEMUCapsKVMSupportsNesting and capabilities cache is properly
invalidated when the value of nested parameter changes. Changing pt_mode does
not invalidate the cache, though.

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

libvirt-6.6.0-5

How reproducible:

always

Steps to Reproduce:
1. prepare an Icelake-Server host
2. virsh domcapabilities
3. modprobe -r kvm_intel
4. modprobe kvm_intel pt_mode=1
5. virsh domcapabilities

Actual results:

In step 2. the <mode name='host-model' supported='yes'> element will contain
Icelake-Server CPU model and intel-pt with policy='disable'.

In step 5. the output will be exactly the same as in step 2.

Expected results:

The intel-pt feature with policy='disable' should disappear from the <mode
name='host-model' supported='yes'> element. This means intel-pt can be
enabled, because libvirt consideres it a part of Icelake-Server CPU model.
Comment 2 John Ferlan 2021-09-08 13:31:40 UTC 
Bulk update: Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release.
Comment 4 RHEL Program Management 2023-09-22 12:18:27 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 5 RHEL Program Management 2023-09-22 12:19:34 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.