+++ 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
Steps to Reproduce:
1. boot a kernel with kvmclock enabled
3. pause grub in the OS selection screen, edit parameters, and remove kvmclock
Hasn't this already been fixed? I remember reviewing the patches.
My bad, forgot to send the patches for 5.5 Just did it for 6.
I am sending it within the hour.
# uname -r
# rpm -q kvm
Verified with Fedora 13 and rhel5.5 64 bit guest by using the steps in comment #0,
This issue has already been fixed.
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.