Red Hat Bugzilla – Bug 448097
RHEL 5.2 doesn't start in kvm virtual machine
Last modified: 2009-04-24 01:11:39 EDT
Description of problem:
When booting RHEL 5.1 (just hoped to upgrade) in kvm virtual machine (it used to
work like a month ago when I started the machine last time; then it was still
Fedora Rawhide), the boot doesn't get over "Enabling local filesystem quotas".
Then it freezes and doesn't do anything else (waited half an hour to be sure).
Unfortunately, because the computer didn't start up, I don't know much how to
get more information about the issue.
Version-Release number of selected component (if applicable):
100% in two tries
Steps to Reproduce:
1.(as root) virsh create /etc/libvirt/qemu/tikanga.xml ; virt-viewer -c
freezes on "Enabling local filesystem quotas"
it should work, and Firefox shouldn't break (which is I wanted to test at the
Posting the configuration file (tikanga.xml) would really help for us to spot a
bit better what kind of things are happening there.
Also, as a startup, please post host information (cpuinfo to start with)
meanwhile, I'll see if I can reproduce the problem
Note that 5.2 under KVM is known to be broken as well. That is a combination of
two bugs; one a bug in the powernow driver in 5.2 (which should be fixed in
5.3), the second being the fact that KVM doesn't export DMI information. Both
should really be fixed (the latter upstream).
Created attachment 306518 [details]
Created attachment 306519 [details]
Created attachment 306520 [details]
output of dmidecode
Created attachment 306530 [details]
OK, to make sure that the information is complete, here is sysreport attached.
(In reply to comment #2)
> Note that 5.2 under KVM is known to be broken as well. That is a combination of
> two bugs; one a bug in the powernow driver in 5.2 (which should be fixed in
> 5.3), the second being the fact that KVM doesn't export DMI information. Both
> should really be fixed (the latter upstream).
Are there any workarounds for these issues?
Not that I know of; the code with the problem int 5.2 is in the bootpath, and I
don't know of a way to disable that bootpath. And adding the DMI information to
KVM is something that should be done, but is not entirely trivial. You should
stick with a 5.1 kernel for now, if you can get it working.
Which means reinstall over slow ADSL line. Oh well.
Matej, 5.1 does not work with F9 KVM? 5.2 with 5.1 kernel seems to work fine on
I have apparently upgraded to 5.2 kernel or 5.1 doesn't work with F9. I don't
know, and I cannot test it because I cannot get to the virtual machine to find
Created attachment 309327 [details]
Introductory grub screen to show which kernel versions I have
I found that the only way how to collect some information about this issue is
to run whole thing in virt-manager (which I don't usually use) and make a lot
of screenshots. So this is the first image my funnies about whole story. This
is to show which kernels I have installed in the virtual machine and that I
have selected the older one.
Created attachment 309328 [details]
editing kernel command line
I have removed "quiet rhgb" from the kernel command line
Created attachment 309329 [details]
voilá! this is the conclusion -- kernel panick when local drivers are mounted
Yes, and in regards to comment #10, 5.1 KVM guests work just fine for me here on
both AMD and Intel. Although I have to admit, I'm just using 53.el5, not one of
the releases after that. Matej, can you install the .53 (not 53.1.6), and see
if that boots?
(In reply to comment #15)
> Yes, and in regards to comment #10, 5.1 KVM guests work just fine for me here
> on both AMD and Intel. Although I have to admit, I'm just using 53.el5, not
> one of the releases after that. Matej, can you install the .53 (not 53.1.6),
> and see if that boots?
Well, I have to reinstall the guest from scratch, which will take some time --
this is not my highest priority at the moment.
OK, I have reinstalled and bare RHEL 5.1GA works perfectly. Running yum upgrade
and will report the results.
Created attachment 309649 [details]
screenshot of non-reproduction
With upgrading to the latest version of everything (including kernel
2.6.18-92.1.1.el5) everything works without a problem. I would hesitate to just
close this bug, if there is not a good explanation why it suddenly works.
Matej, still running on the Intel host?
Host system is still the same (Fedora 9, kernel-220.127.116.11-55.fc9.i686,
I has been working for some time already.