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 592296 - KVM should support the newer set of MSRs for kvmclock
Summary: KVM should support the newer set of MSRs for kvmclock
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.0
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Glauber Costa
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 533943 569603 624983
TreeView+ depends on / blocked
 
Reported: 2010-05-14 13:47 UTC by Glauber Costa
Modified: 2013-01-09 22:34 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 624983 (view as bug list)
Environment:
Last Closed: 2010-11-11 15:50:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Glauber Costa 2010-05-14 13:47:19 UTC
Description of problem:

KVM has deprecated the current msr set used by kvmclock, and came up with a new set. While the old set is still working, and will, during the lifetime of RHEL6,
in a 7 year period, it is likely that new guests will appear that uses only the newer set. We should, therefore, support both.

Comment 1 RHEL Program Management 2010-05-14 14:30:46 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 5 Aristeu Rozanski 2010-05-18 21:13:52 UTC
Patch(es) available on kernel-2.6.32-27.el6

Comment 10 Shirley Zhou 2010-08-18 10:10:13 UTC
Test this bug with kernel-2.6.32-63.el6 as following

1.start guest fc15, kernel is 2.6.36-0.0.rc0.git1.fc15.i686.PAE
2.check dmesg info 
dmesg|grep kvm
kvm-clock: Using msrs 12 and 11
kvm-clock: cpu 0, msr 0:c4a081, boot clock
kvm-clock: cpu 0, msr 0:3149081, primary cpu clock
kvm-clock: cpu 1, msr 0:3349081, secondary cpu clock
Switching to clocksource kvm-clock

From dmesg, no newer msr available. 
After talk with Glauber through IRC, Glauber think qemu lack patch to make it work, open qemu Bug 624983 to track this issue. 
Change status to verified as patch added.

Comment 11 releng-rhel@redhat.com 2010-11-11 15:50:57 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


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