Red Hat Bugzilla – Bug 528310
when kvm is load, Kernel panic on rebooting after implement suspend and resume
Last modified: 2010-03-30 03:51:27 EDT
Created attachment 364363 [details] picture Description of problem: I can reproduce this bug on my laptop (Lenovo X200). The last message before the Call Trace is : "kvm: exiting hardware virtualization ",attached is the screenshot of the panic. If remove the kvm module,then reboot works well. When trying to reproduce this problem on OPTIPLEX 760, hit a kernel's issue before "kvm: exiting hardware virtualization".(bug 528308) Version-Release number of selected component (if applicable): kvm-83-105.el5_4.9 kernel-2.6.18-164.2.1.el5 How reproducible: 100% Steps to Reproduce: 1. Suspend ( System -> Suspend ) 2. Resume by pressing the power button 3. Reboot Actual results: Expected results: Additional info:
Suspending KVM hosts is not supported currently. If suspend/resume support is needed (on a machine that is not a KVM host), the user needs to uninstall kmod-kvm.
Should be fixed by the fix for bug #510814. Moving to POST to reflect the fix status.
The fix for bug #510814 (that should solve this bug) is in kernel-2.6.18-170.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5 Testing is welcome.
(In reply to comment #6) > The fix for bug #510814 (that should solve this bug) is in > kernel-2.6.18-170.el5 > You can download this test kernel from http://people.redhat.com/dzickus/el5 > > Testing is welcome. Yes . Can not reproduce in kernel-2.6.18-170.el5 ( from https://brewweb.devel.redhat.com/buildinfo?buildID=116005 )
retest in kernel -185, host is auto-resume due to 550014, but the kernel oops on rebooting is gone.
(In reply to comment #9) > retest in kernel -185, host is auto-resume due to 550014, but the kernel oops > on rebooting is gone. 550014 is gone in -189.el5. retested and this bug also PASSed. # uname -r 2.6.18-189.el5 #rpm -q kvm kvm-83-157.el5 setting to verified.
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-0271.html