Bug 1013641
Summary: | RHEL-5.9 loops in early boot stages, taking all CPU | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jiri Popelka <jpopelka> | ||||||||||
Component: | qemu | Assignee: | Fedora Virtualization Maintainers <virt-maint> | ||||||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | high | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 20 | CC: | amit.shah, berrange, cfergeau, crobinso, dwmw2, gnatapov, itamar, jpopelka, pbonzini, rjones, scottt.tw, virt-maint | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | x86_64 | ||||||||||||
OS: | Linux | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2013-11-29 11:24:54 UTC | Type: | Bug | ||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||
Documentation: | --- | CRM: | |||||||||||
Verified Versions: | Category: | --- | |||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
Embargoed: | |||||||||||||
Attachments: |
|
Does rmmod kvm_intel && modprobe kvm_intel emulate_invalid_guest=0 make any difference? If so, please dup this to 1012119 That does not seem to make any difference. Can you provide the guest XML (sudo virsh dumpxml $vmname) and /var/log/libvirt/qemu/$vmname.log Created attachment 806350 [details]
/var/log/libvirt/qemu/$vmname.log
Created attachment 806351 [details]
virsh dumpxml $vmname
Jiri, if you 'sudo virsh edit $vmname' and change <domain type> to qemu, does the guest boot? (albeit very slowly) Yes, with <domain type='qemu'> it boots (very slowly). Jiri, can you provide /proc/cpuinfo? Also, please try kernel 3.12 from rawhide, on the host machine. Gleb, Paolo, ideas for further debugging? Created attachment 818372 [details] /proc/cpuinfo (In reply to Cole Robinson from comment #8) > Jiri, can you provide /proc/cpuinfo? attached > Also, please try kernel 3.12 from rawhide, on the host machine. 3.12.0-0.rc7.git2.1.fc21.x86_64 makes no change There's a kernel bug tracking similar issues: https://bugzilla.redhat.com/show_bug.cgi?id=967652 The 3.13 kernels in rawhide have the referenced patch. Jan, can you give the latest rawhide kernel a spin as well? If that kernel fixes the boot issues, we can dup this to the kernel bug. 3.13.0-0.rc0.git5.1.fc21.x86_64 doesn't seem to fix it. Okay, to summarize: - RHEL5.9 guest - Started fine on F19, seems to loop endlessly on f20 - 3.13 kernel from rawhide doesn't help - Running without KVM _does_ make things work - Host cpuinfo and guest commandline are in previous comments Paolo, Gleb, any ideas what else to debug here? Jiri, even with a newer kernel it will take a few minutes to boot. Yes, with <domain type='qemu'> the boot takes many minutes. With <domain type='kvm'> it stucks on https://bugzilla.redhat.com/attachment.cgi?id=805216 even with rawhide's 3.12 and 3.13. FWIW that graphical corruption should be fixed by latest spice-gtk queued for F20, but it shouldn't affect this issue. With <domain type='kvm'> it will be stuck for several minutes and then proceed at normal speed. (In reply to Cole Robinson from comment #15) > FWIW that graphical corruption should be fixed by latest spice-gtk queued > for F20, but it shouldn't affect this issue. I don't see that red patterns anymore. (In reply to Paolo Bonzini from comment #16) > With <domain type='kvm'> it will be stuck for several minutes and then > proceed at normal speed. I left it running for 15 minutes, but no progress. (In reply to Jiri Popelka from comment #17) > I left it running for 15 minutes, but no progress. With kernel-3.13.0-0.rc1.git3.1.fc21.x86_64 And a moment after I posted the previous comment it started to boot :-D at what seems to be normal speed. And after updating guest from RHEL-5.9 to RHEL-5.10 (kernel-2.6.18-371) everything's OK even with host's 3.11.9-300.fc20 Thanks Jirka. *** This bug has been marked as a duplicate of bug 967652 *** |
Created attachment 805216 [details] screenshot Description of problem: This is F20 x86_64 constantly updated since Alpha-RC1. It's the first time I tried to run my old RHEL-5.9 image (was working in F19) on F20 so I can't tell whether it's been caused with some update or it's like this since the initial install. Version-Release number of selected component (if applicable): qemu-system-x86-1.6.0-8.fc20.x86_64 libvirt-1.1.2-4.fc20.x86_64 How reproducible: Always Steps to Reproduce: 1. Try to install (or run already installed image) RHEL-5.9 x86_64 Actual results: The guest machine loops in early boot stages, taking 100% CPU. See screenshot.