I've tried installing the Red Hat Enterprise Linux 6 beta 2 under KVM on Fedora 13... completely updated system.
For some reason the RHEL6 installer crashes at various places across multiple VM boots / attempts... with no specific, repeatable operation-to-bug relation. I use Fedora 12, 13, and Windows 7 in KVM without any problems and am baffled why RHEL6 is so error prone.
At first I thought it was RHEL6 but I've seen reports from those who have witnessed this problem switch to VirtualBox and/or physical hardware and the problems disappeared.
How to repeat:
Download RHEL6 Beta 2 media (x86_64 workstation is what I was using but I've heard it pertains to the i686 release as well) and boot it up in an attempt to create a VM with it. I have created hundreds of VMs with the same setup and RHEL6 is the only thing I've had a problem with.
I'm not even sure where to start with providing data points on this "bug"... but it is pretty easy to trigger just by trying to create a RHEL6beta2 VM.
This also affects me. Using a F13 workstation, running RHEL 6 beta 2 (either x86_64 or i386) is unusably flaky under KVM. :(
Running it under VirtualBox works, as does running other guest OS's under KVM, so this appears to be a bug in KVM + RHEL 6 beta 2 not working correctly together.
I suspect it may be related to BZ# 609071 or BZ# 607650.
607650 talks of a host kernel problem that's resolved by upstream commit 3be2264be3c00865116f997dc53ebcc90fe7fc4b
That commit should soon find its way to stable kernels and to Fedora (or be backported).
Wow. More and more bugs I try to browse to give me the "You are not authorized to access bug #xxxxxxx"... and that's what happens to bug #607650 that you mention. :(
(In reply to comment #3)
> Wow. More and more bugs I try to browse to give me the "You are not authorized
> to access bug #xxxxxxx"... and that's what happens to bug #607650 that you
> mention. :(
A few bugs get reported during the regular testing of upcoming Red Hat releases and are not visible to non-Red Hat people. IIRC these bugs are normally opened to all once some release milestones are met.
In any case, we've identified the bug and the commit that's needed to fix it.
I'll also update the subject line to better describe the bug.
Avi Kivity, the Engineer who has been fixing this problem, has created a kernel rpm for testing with.
On my F13 workstation it's working fine and RHEL 6 beta 2 inside kvm is happy.
Are you able to give this a shot as well, and let us know how it goes?
That commit is:
I assume we want this similar fix too?
Hi Chuck, not sure. Ask Avi or Andrea maybe?
(In reply to comment #5)
> Hi Scott,
> Avi Kivity, the Engineer who has been fixing this problem, has created a kernel
> rpm for testing with.
> On my F13 workstation it's working fine and RHEL 6 beta 2 inside kvm is happy.
> Are you able to give this a shot as well, and let us know how it goes?
Works for me. I was able to successfully install RHEL6Beta x86_64 Workstation and ran it for a while without any problems. I could only get 800x600 in virt-manager selecting RHEL6 as the distro profile when creating but I don't know if that is a kernel thing or not. With other OSes, I'm able to get 1024x768.
So, the problem appears to be fixed!
Those commits are important, but they don't fix the problem reported here. I'll post patches for the Fedora kernel.
Scott, thanks for testing.
*** Bug 616011 has been marked as a duplicate of this bug. ***
Avi has identified upstream commit 06f334e2b509b4c9f6c4cec7e0e56444a2730922 from kvm.git as fixing this issue:
Please backport to the F13 kernel.
Created attachment 433437 [details]
Fedora 13 patch (2.6.33 kernel)
Patch went in 220.127.116.11-25.fc13
Will this fix make it to 2.6.35?
18.104.22.168-25.fc13 isn't in testing, is it going to be put into the F13 repos or is it just going to be available from the rawhide repo?
(In reply to comment #14)
> Will this fix make it to 2.6.35?
Yes. I'll submit it tomorrow, with -stable updates to follow.
(In reply to comment #15)
> 22.214.171.124-25.fc13 isn't in testing, is it going to be put into the F13 repos or
> is it just going to be available from the rawhide repo?
You can get it from koji for now -- there are still too many bugs to keep it from going into F13 updates-testing just yet.
Chuck, is it possible to push a 2.6.33 update with just the patch added on top, to avoid the long 2.6.34 cycle? This bug is hitting many people.
Patch added to 126.96.36.199-147.2.2.fc13
kernel-188.8.131.52-147.2.4.fc13 has been submitted as an update for Fedora 13.
kernel-184.108.40.206-147.2.4.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update kernel'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/kernel-220.127.116.11-147.2.4.fc13
*** Bug 618227 has been marked as a duplicate of this bug. ***
I believe the problem I am/was having stems from the same cause. My RHEL6beta x86_64 KVM guest was quite unstable on a Fedora12/13 host but ran fine on a CentOS-5.5 host. I installed the test kernel-18.104.22.168-147.2.4.fc13 on the Fedora13 host. This did not fix the problem.
Then I applied a workaround  (offered for RHEL6beta) to the 6beta guest and this seems to have resolved the instability issue. I am now testing the patched kernel-2.6.32-44.2.el6 on this guest (with the workaround removed).
 Boot/install the guest with transparent huge pages off using the kernel command line parameter: 'transparent_hugepage=never'
kernel-22.214.171.124-147.2.4.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.