Bug 557095

Summary:	kvm pvclock on i386 suffers from double registering
Product:	Red Hat Enterprise Linux 5	Reporter:	Glauber Costa <gcosta>
Component:	kernel	Assignee:	Glauber Costa <gcosta>
Status:	CLOSED ERRATA	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	medium	Docs Contact:
Priority:	urgent
Version:	5.5	CC:	cpelland, ehabkost, lihuang, mjenner, tburke
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-03-30 06:53:29 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:	528898, 561454

Description Glauber Costa 2010-01-20 12:21:09 UTC

By looking at the dmesg on a i386 kvm guest with pvclock enabled, I noticed that we're registering the boot clock after primary and secondary clock are already registered, as part of the cpu identification code.

This causes kvm to write data to a random memory area during guest's life.

Comment 1 Glauber Costa 2010-01-20 18:36:01 UTC

I just posted it, definitely for 5.6.

But maybe we should consider it for 5.5 post beta too. Fix is not hard and not invasive.

Comment 2 RHEL Program Management 2010-01-21 07:30:39 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 12 errata-xmlrpc 2010-03-30 06:53:29 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0178.html