I had an instance of FC 14 running in a kvm vm on a centos 5.6 box. After updating the kernel today, that vm refused to boot. I'm bumped into a grub menu. Grub doesn't seem to be able to find the boot image or the root partition. There are two othere vm instances (FC 13, and Winxp) that are fine.
Has anyone else seen this? I don't know my way around grub well enough to get it going. As an expedient I simply created a new instance, but I'd like to know what went wrong.
Thanks in advance.
On Tue, Apr 12, 2011 at 8:02 PM, Barry txscope@fastmail.fm wrote:
I had an instance of FC 14 running in a kvm vm on a centos 5.6 box. After updating the kernel today, that vm refused to boot. I'm bumped into a grub menu. Grub doesn't seem to be able to find the boot image or the root partition. There are two othere vm instances (FC 13, and Winxp) that are fine.
You might have run into a 5.6 bug. Are the F13 and WinXP images of type qcow2 and the F14 image of type raw?
On Wed, 13 Apr 2011 01:01 -0400, "Tom H" tomh0665@gmail.com wrote:
On Tue, Apr 12, 2011 at 8:02 PM, Barry txscope@fastmail.fm wrote:
I had an instance of FC 14 running in a kvm vm on a centos 5.6 box. After updating the kernel today, that vm refused to boot. I'm bumped into a grub menu. Grub doesn't seem to be able to find the boot image or the root partition. There are two othere vm instances (FC 13, and Winxp) that are fine.
You might have run into a 5.6 bug. Are the F13 and WinXP images of type qcow2 and the F14 image of type raw? --
That's good question. I used the default settings in Virtmanager and created all the easy way, so I suppose that they are all raw.
Looking at the xml files in /etc/libvirt/qemu, both the problem FC14 and the working FC13 vms have no type listed in the driver spec.
The Winxp and a new FC14 instance (created last night and working fine) have a type listed as 'raw'.
I don't know where else to look for the type.
I just updated the host to Centos 5.6 on the weekend, and I restarted the machine then, and therefore, restarted the vms as well, and all three of the vms fired up. It was only when I updated the FC14 vm that I ran into the problem.
On Wed, Apr 13, 2011 at 8:55 AM, Barry txscope@fastmail.fm wrote:
On Wed, 13 Apr 2011 01:01 -0400, "Tom H" tomh0665@gmail.com wrote:
On Tue, Apr 12, 2011 at 8:02 PM, Barry txscope@fastmail.fm wrote:
I had an instance of FC 14 running in a kvm vm on a centos 5.6 box. After updating the kernel today, that vm refused to boot. I'm bumped into a grub menu. Grub doesn't seem to be able to find the boot image or the root partition. There are two othere vm instances (FC 13, and Winxp) that are fine.
You might have run into a 5.6 bug. Are the F13 and WinXP images of type qcow2 and the F14 image of type raw?
That's good question. I used the default settings in Virtmanager and created all the easy way, so I suppose that they are all raw.
Looking at the xml files in /etc/libvirt/qemu, both the problem FC14 and the working FC13 vms have no type listed in the driver spec.
The Winxp and a new FC14 instance (created last night and working fine) have a type listed as 'raw'.
I don't know where else to look for the type.
I just updated the host to Centos 5.6 on the weekend, and I restarted the machine then, and therefore, restarted the vms as well, and all three of the vms fired up. It was only when I updated the FC14 vm that I ran into the problem.
I thought that with the latest version, if there's no type specified, raw's assumed for some reason. So if the type's qcow2, it fails.
But that doesn't explain why your F13 VM's OK.
From the CentOS archive:
http://lists.centos.org/pipermail/centos/2011-April/109595.html
On Sat, 16 Apr 2011 07:26 -0400, "Tom H" tomh0665@gmail.com wrote:
On Wed, Apr 13, 2011 at 8:55 AM, Barry txscope@fastmail.fm wrote:
On Wed, 13 Apr 2011 01:01 -0400, "Tom H" tomh0665@gmail.com wrote:
On Tue, Apr 12, 2011 at 8:02 PM, Barry txscope@fastmail.fm wrote:
I had an instance of FC 14 running in a kvm vm on a centos 5.6 box. After updating the kernel today, that vm refused to boot. I'm bumped into a grub menu. Grub doesn't seem to be able to find the boot image or the root partition. There are two othere vm instances (FC 13, and Winxp) that are fine.
You might have run into a 5.6 bug. Are the F13 and WinXP images of type qcow2 and the F14 image of type raw?
That's good question. I used the default settings in Virtmanager and created all the easy way, so I suppose that they are all raw.
Looking at the xml files in /etc/libvirt/qemu, both the problem FC14 and the working FC13 vms have no type listed in the driver spec.
The Winxp and a new FC14 instance (created last night and working fine) have a type listed as 'raw'.
I don't know where else to look for the type.
I just updated the host to Centos 5.6 on the weekend, and I restarted the machine then, and therefore, restarted the vms as well, and all three of the vms fired up. It was only when I updated the FC14 vm that I ran into the problem.
I thought that with the latest version, if there's no type specified, raw's assumed for some reason. So if the type's qcow2, it fails.
I saw some discussion of that, but the problem FC14 does start to boot. It jumps right to grub where it gets stuck. I think the vm image must be messed up.
I thought I might be able to boot into an earlier kernel by entering the commands in grub. I can find the vmlinuz files, and the initrd image, but I don't know how to point grub to the root system. It's using LVM and I'm not sure how to construct the pointer. It looks like it should be "root=vg_MACHINENAME-lv_root" but one really dumb thing is that I cannot recall the name. I've tried a few variations and it never finds root
I tried to see the grub.conf, but 'cat /boot/grub/grub.conf' showed me an empty file.
As a last resort, I can delete image and start again. Anything important is saved.
But that doesn't explain why your F13 VM's OK.
From the CentOS archive:
http://lists.centos.org/pipermail/centos/2011-April/109595.html
On 04/17/2011 01:21 PM, Barry wrote:
I thought I might be able to boot into an earlier kernel by entering the commands in grub.
Once you've entered the grub menu, you should be able to use the arrow keys to select the kernel you want (By default, Fedora keeps the most recent three.) and tell it to boot.
On Sun, 17 Apr 2011 13:29 -0700, "Joe Zeff" joe@zeff.us wrote:
On 04/17/2011 01:21 PM, Barry wrote:
I thought I might be able to boot into an earlier kernel by entering the commands in grub.
Once you've entered the grub menu, you should be able to use the arrow keys to select the kernel you want (By default, Fedora keeps the most recent three.) and tell it to boot. --
I don't get the grub menu -- it just jumps to the grub prompt. I tried to examine the file grub.conf in grub -- which is where the grub menu comes from -- but it shows up as empty.
I can find the kernel images and I've tried the boot the current one and the previous one, but I need to specify where / can be found -- assuming all else is ok. It's an LVM partition -- the default -- and because I wasn't careful, I never copies the LVM pointer.
I may well be stuck.
-
Barry -
Joe Zeff -
Tom H