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.

Bug 518285

Summary: [LTC 6.0 FEAT] kvm hpet support [202011]
Product: Red Hat Enterprise Linux 6 Reporter: IBM Bug Proxy <bugproxy>
Component: qemu-kvmAssignee: Glauber Costa <gcosta>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 6.0CC: amit.shah, jjarvis, kmonroe, lihuang, llim, snagar, syeghiay, tburke, virt-maint
Target Milestone: rcKeywords: FutureFeature
Target Release: 6.1   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: qemu-kvm-0.12.1.2-2.30.el6 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 576973 (view as bug list) Environment:
Last Closed: 2011-05-26 19:29:08 UTC Type: ---
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:    
Bug Blocks: 356741, 524565, 554559, 576973, 580953, 655920    

Description IBM Bug Proxy 2009-08-19 18:11:50 UTC
=Comment: #0=================================================
Emily J. Ratliff <ratliff.com> - 
1. Feature Overview:
Feature Id:	[202011]
a. Name of Feature:	kvm hpet support
b. Feature Description
Add hpet emulation to qemu and kvm

2. Feature Details:
Sponsor:	LTC
Architectures:
x86
x86_64

Arch Specificity: Both
Affects Kernel Modules: Yes
Delivery Mechanism: Backport
Category:	Xen
Request Type:	Package - New
d. Upstream Acceptance:	Accepted
Sponsor Priority	2
f. Severity: Medium
IBM Confidential:	no
Code Contribution:	IBM code
g. Component Version Target:	kvm-88, qemu

3. Business Case
Provide higher resolution timer to KVM guests.  HPET emulation provides more accurate and faster
timers for guest resulting in higher performance and better timer latency for certain workloads in
guests.

4. Primary contact at Red Hat: 
John Jarvis
jjarvis

5. Primary contacts at Partner:
Project Management Contact:
Stephanie Glass, sglass.com, 512-838-9284

Technical contact(s):
Ryan Harper, raharper.com

IBM Manager:
Warren Grunbok II, grunbok.com

Comment 2 Dor Laor 2009-09-24 11:50:39 UTC
It will be automatically in qemu. We'll test it for correctness.
If you have additional info validating it's stability today it will be helpful.

Comment 3 Eduardo Habkost 2010-01-20 11:52:17 UTC
On RHEL-6, the KVM userspace package is named "qemu-kvm". Moving bug to the right component.

Comment 6 Dor Laor 2010-02-10 15:21:37 UTC
The feature is included but not tested enough. Unless we'll get reports that the hpet is stable on all supported guests and does not drift, we'll need to use -no-hpet flag by default.