Red Hat Bugzilla – Bug 974420
Kernel 3.9.5 locks up when Qemu/KVM is started
Last modified: 2013-09-19 08:56:19 EDT
Description of problem:
After yesterday's upgrades for Fedora 19 beta which included kernel 3.9.5-301 and qemu 1.4.2-3, I get lockups soon after I have started a VM. When it first happened, I have reset the computer and tried it again, this time without Firefox, Thunderbird and skype running.
My computer has an 8-core AMD FX-8120 CPU with 16GB memory and the VM guest is CentOS 5.9, 8 CPUs are assigned to it together with 2GB memory. The lockup happends when it tries to switch to "graphics mode" in the guest and starting up X and GDM.
The VM and the computer is completely usable with the previous kernel 3.9.4-301.
The lockup has the attached traces in the syslog for the two lockups.
Version-Release number of selected component (if applicable):
# rpm -q kernel
Two out of two attempts.
Steps to Reproduce:
Computed locks up.
No lock up.
Created attachment 761126 [details]
Kernel BUGs for the first lockup
Created attachment 761127 [details]
general protection faults for the second lockup
I also had a similar issue, but kernel panic was with a Windows 7 KVM guest. In my testing I just started the guest with "virsh start Windows7" and within the boot process the kernel will panic. Since this is my machine for work I just returned to 3.9.4-200.
# rpm -q kernel
MB GIGABYTE GA-990XA-UD3 R
VGA SAPPHIRE|100315L HD6850 R
I don't have the logs from my event. I would be willing to assist if someone provides the details how to retrieve the panic log.
(In reply to jcpowermac from comment #3)
> I also had a similar issue, but kernel panic was with a Windows 7 KVM guest.
> In my testing I just started the guest with "virsh start Windows7" and
> within the boot process the kernel will panic. Since this is my machine for
> work I just returned to 3.9.4-200.
This might be a separate issue and possibly a dup of bug 975065. It would be good to confirm/deny with a backtrace though.
> I don't have the logs from my event. I would be willing to assist if
> someone provides the details how to retrieve the panic log.
Generally the backtrace will make it to the primary console of the host, particularly if that's a simple serial console. Otherwise you can look into setting up kdump to get the entire core, and then grabbing the backtrace from that.
Please test this scratch build when it completes:
Created attachment 763275 [details]
Kernel BUGs with kernel-3.9.6-301.4.fc19.x86_64
Upgrading to kernel-3.9.6-301.4.fc19.x86_64 from koji didn't help.
Same lockup at the same time when KVM is getting to start up GDM in the CentOS 5.9 guest.
Hm. Looking at your latest attachment, that seems to be a radeon issue. Here's another scratch build for you to try if you'd like, but I'm not convinced it's the same issue we're chasing in the other bugs.
*********** MASS BUG UPDATE **************
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.
Fedora 19 has now been rebased to 3.11.1-200.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.
If you experience different issues, please open a new bug report for those.
I should have closed this bug, it was fixed with the kernel upgrade to 3.10.x.