Description of problem: running upstream qemu on rhel 5.4 hangs on boot Version-Release number of selected component (if applicable): 5.4 How reproducible: always Steps to Reproduce: 1.check out qemu kvm b7e0dba1a864767ad5836f944f3d6dd89ebcdc7a 2. boot linux. Actual results: timer is not being deliverd and kernel hangs on boot Expected results: should boot Additional info: using -no-kvm-irqchip works around this issue
Created attachment 356216 [details] patch 1 fixes the main issue
Created attachment 356217 [details] patch 2 fixes bug introduced by patch 1
Created attachment 356218 [details] patch 3 fixes build with config from my box so I could work on 1&2
Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: ABI stability: the ABI between userspace (e.g. qemu-kvm) and the KVM kernel modules is likely to change in future updates.
fixing component: it's kvm, not kernel
Eduardo, that's a pretty obscure note. Maybe note upstream qemu-kvm specifically? - qemu revisions built from latest qemu-kvm tree are known to fail on boot - As a work around, specify -no-kvm-irqchip on the command line - The issue will be fixed in a future errata
Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -ABI stability: the ABI between userspace (e.g. qemu-kvm) and the KVM kernel modules is likely to change in future updates.+ABI stability: the ABI between userspace (e.g. qemu-kvm) and the KVM kernel modules is likely to change in future updates. Running latest upstream qemu-kvm isn't supported because of the ABI differences (see bug 515549).
Got this from the user that reported this originally: > Date: Wed, 5 Aug 2009 10:00:36 -0700 > From: Ramachandra Pai > > Big Positive ACK! yes it fixes the problem.
*** Bug 516228 has been marked as a duplicate of this bug. ***
Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -ABI stability: the ABI between userspace (e.g. qemu-kvm) and the KVM kernel modules is likely to change in future updates. Running latest upstream qemu-kvm isn't supported because of the ABI differences (see bug 515549).+the application binary interface (ABI) between the KVM userspace (e.g. qemu-kvm) and the KVM kernel modules may change in future updates. Using the latest upstream qemu-kvm package is unsupported due to ABI differences. (BZ#515549)
(In reply to comment #0) Michael, How did you configure the qemu-kvm? Could you please add your steps in this bug? I just use "configure && make && make install" to combine the qemu-kvm, then start guest. But the guest failed in kernel panic. Attached the Screenshot. I tried on kvm-83-113.el5.
Created attachment 380752 [details] Screenshot-kernel panic
I could not reproduce this bug on kvm-83-152.el5 (commit 34f6b13147766789fc2ef289f5b420f85e51d049)
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