Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
This bug has been copied from bug #609032.
Solved in upstream and proposed to be backported to 6.4, in order to reduce support load.
Patch successful applied and tested to kernel-2.6.32-220.4.1:
commit c94c3ba901f87115cf574044e7faabfb1d0251fb
Author: Avi Kivity <avi>
Date: Wed Sep 1 10:23:35 2010 +0300
KVM: Don't save/restore MSR_IA32_PERF_STATUS
It is read/only; restoring it only results in annoying messages.
Signed-off-by: Avi Kivity <avi>
--- a/x86/x86.c 2011-04-07 13:49:17.000000000 +0200
+++ b/x86/x86.c 2011-04-07 13:49:33.000000000 +0200
@@ -715,7 +715,7 @@
#ifdef CONFIG_X86_64
MSR_CSTAR, MSR_KERNEL_GS_BASE, MSR_SYSCALL_MASK, MSR_LSTAR,
#endif
- MSR_IA32_TSC, MSR_IA32_PERF_STATUS, MSR_IA32_CR_PAT, MSR_VM_HSAVE_PA
+ MSR_IA32_TSC, MSR_IA32_CR_PAT, MSR_VM_HSAVE_PA
};
static unsigned num_msrs_to_save;
Comment 1Przemyslaw Sztoch
2012-06-08 22:19:44 UTC
?!
Comment 2RHEL Program Management
2012-07-10 07:49:41 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 3RHEL Program Management
2012-07-11 02:06:35 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Hi avi,
Can you give some suggestion how to verify this bug.
no stable step to get message:
"9480: cpu0 unimplemented perfctr wrmsr: 0x186 data 0x130079"
Thanks
Suqin
update the component to kernel according to the patch in comment0
Comment 7RHEL Program Management
2012-07-13 02:39:57 UTC
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release. Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
Test with qemu-kvm-0.12.1.2-2.340.el6.x86_64:
we won't see following message any more:
"9480: cpu0 unimplemented perfctr wrmsr: 0x186 data 0x130079"
however we still get:
kvm: 6149: cpu0 unhandled wrmsr 0x40000000 data 0
kvm: 6149: cpu0 unhandled rdmsr 0x40000000
Hope this is enough to verify the bug.
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2013-0496.html