Bug 588878 - Rebooting a kernel with kvmclock enabled, into a kernel with kvmclock disabled, causes random crashes
Rebooting a kernel with kvmclock enabled, into a kernel with kvmclock disable...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kvm (Show other bugs)
5.5
All Linux
low Severity medium
: rc
: ---
Assigned To: Glauber Costa
Virtualization Bugs
:
Depends On: 588884
Blocks: Rhel5KvmTier1 588877
  Show dependency treegraph
 
Reported: 2010-05-04 14:40 EDT by Glauber Costa
Modified: 2013-01-09 17:32 EST (History)
18 users (show)

See Also:
Fixed In Version: kvm-83-185.el5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 588874
Environment:
Last Closed: 2011-01-13 18:35:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Glauber Costa 2010-05-04 14:40:27 EDT
+++ This bug was initially created as a clone of Bug #588874 +++

Description of problem:

Right now, if we boot into a kernel with kvmclock eanbled, and then reboot into a kernel with kvmclock disabled (rebooting with no-kvmclock kernel option is enough), we'll see the second kernel crash with random memory corruption.

This indicates that kvmclock is still writing to the old memory location,
which will now contain something else entirely.

Version-Release number of selected component (if applicable):
all, including upstream

How reproducible:

Always

Steps to Reproduce:
1. boot a kernel with kvmclock enabled
2. reboot
3. pause grub in the OS selection screen, edit parameters, and remove kvmclock
  
Actual results:

Crash

Expected results:

Work.
Comment 1 Zachary Amsden 2010-06-22 17:00:50 EDT
Hasn't this already been fixed?  I remember reviewing the patches.
Comment 2 Glauber Costa 2010-06-23 09:25:01 EDT
My bad, forgot to send the patches for 5.5 Just did it for 6.
I am sending it within the hour.
Comment 7 Mike Cao 2010-11-03 03:47:52 EDT
# uname -r 
2.6.18-229.el5
# rpm -q kvm
kvm-83-207.el5

Verified with Fedora 13 and rhel5.5 64 bit guest by using the steps in comment #0,
This issue has already been fixed.
Comment 10 errata-xmlrpc 2011-01-13 18:35:24 EST
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-2011-0028.html

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