Bug 909574

just updated my f18 vm - no issues

We'll need to actually see the kernel panic.  There's nothing we can do with this bug at the moment.

ok .. so how do i collect data for a kernel panic?

If you have a serial console, you can log the output to that.  Or you can transcribe the text from the screen by hand.  Otherwise, a digital picture of the panic on the screen is better than nothing.

If the panic is scrolling off the screen, you can use the pause_on_oops=30 kernel parameter to make it pause first.  Just add that to the kernel parameters in the grub configuration file for that kernel.

Created attachment 697751 [details]
screenshot of laptop with kernel panic

let me know if you need another picture. i can recreate it at will

oh and let me know if i need to add pause_on_oops=30 kernel parameter and if i do need to do that, how to do it with grub2. i am a little behind with technology ;)

in today's version too. kernel-3.7.7-201.fc18.x86_64

All the picture is showing is that the kernel cannot find the rootfs.  Can you attach the grub.cfg file?

Also, do /boot/initramfs-3.7.6-201.fc18.x86_64.img and /boot/initramfs-3.7.7-201.fc18.x86_64.img exist?

i had an enlightening moment and uninstalled 3.7.6. i only have 3.7.7 on my desktop now.
[marafa@desktop ~]$ rpm -qa | grep kernel-3.7
kernel-3.7.4-204.fc18.x86_64
kernel-3.7.5-201.fc18.x86_64
kernel-3.7.2-204.fc18.x86_64
kernel-3.7.7-201.fc18.x86_64
[marafa@desktop ~]$ yum erase ^C
[marafa@desktop ~]$ cd /boot/initramfs-3.*
bash: cd: /boot/initramfs-3.6.10-2.fc17.x86_64.img: Not a directory
[marafa@desktop ~]$ ll /boot/initramfs-3.*
-rw------- 1 root root 20M Dec 16 03:14 /boot/initramfs-3.6.10-2.fc17.x86_64.img
-rw------- 1 root root 20M Jan  5 12:15 /boot/initramfs-3.6.11-1.fc17.x86_64.img
-rw------- 1 root root 20M Jan 20 23:04 /boot/initramfs-3.7.2-204.fc18.x86_64.img
-rw------- 1 root root 20M Jan 27 03:20 /boot/initramfs-3.7.4-204.fc18.x86_64.img
-rw------- 1 root root 20M Feb  5 07:37 /boot/initramfs-3.7.5-201.fc18.x86_64.img
[marafa@desktop ~]$ ll /boot/initramfs-3.7*
-rw------- 1 root root 20M Jan 20 23:04 /boot/initramfs-3.7.2-204.fc18.x86_64.img
-rw------- 1 root root 20M Jan 27 03:20 /boot/initramfs-3.7.4-204.fc18.x86_64.img
-rw------- 1 root root 20M Feb  5 07:37 /boot/initramfs-3.7.5-201.fc18.x86_64.img
[marafa@desktop ~]$ df -h
Filesystem                      Size  Used Avail Use% Mounted on
devtmpfs                        3.9G     0  3.9G   0% /dev
tmpfs                           3.9G  2.2M  3.9G   1% /dev/shm
tmpfs                           3.9G   20M  3.9G   1% /run
tmpfs                           3.9G     0  3.9G   0% /sys/fs/cgroup
/dev/mapper/vg_desktop-lv_root  453G  351G   79G  82% /
tmpfs                           3.9G   21M  3.9G   1% /tmp
/dev/sda1                       485M  159M  301M  35% /boot
[marafa@desktop ~]$ rpm -qil kernel-3.7.7-201.fc18.x86_64|grep initramfs
/boot/initramfs-3.7.7-201.fc18.x86_64.img

[marafa@desktop ~]$ sudo ls -ltr /etc/grub*
[sudo] password for marafa: 
lrwxrwxrwx. 1 root root   22 May 30  2011 /etc/grub.conf -> ../boot/grub/grub.conf
lrwxrwxrwx  1 root root   22 Jan 17 21:37 /etc/grub2.cfg -> ../boot/grub2/grub.cfg

Created attachment 699186 [details]
grub2.cfg

grub2.cfg

OK.  So you have neither the initramfs file for 3.7.7, nor does the grub2.cfg file list an initrd entry for it.  I'm going to go ahead and guess that 3.7.6 was a similar case.  That explains why it can't find the rootfs.

This looks like a grubby bug of some sort.  As a workaround, you can regenerate the initramfs by doing:

sudo dracut /boot/initramfs-3.7.7-201.fc18.x86_64.img 3.7.7-201.fc18.x86_64

and then adding the corresponding initrd line to grub2.cfg.

As an aside, I'm not sure why you have more than 3 kernels installed.  Perhaps you changed the default number that yum keeps, which is normally three.

[marafa@desktop tmp]$ sudo rpm -ivh kernel-3.7.8-202.fc18.x86_64.rpm --force
[sudo] password for marafa: 
Preparing...                          ################################# [100%]
Updating / installing...
   1:kernel-3.7.8-202.fc18            ################################# [100%]
grubby fatal error: unable to find a suitable template
F: installkernel failed in module ovirtnode
mkinitrd failed
warning: %posttrans(kernel-3.7.8-202.fc18.x86_64) scriptlet failed, exit status 1

yes, i changed it a while back to 10 so i can always have a working kernel ;)

(In reply to comment #12)
> [marafa@desktop tmp]$ sudo rpm -ivh kernel-3.7.8-202.fc18.x86_64.rpm --force
> [sudo] password for marafa: 
> Preparing...                          #################################
> [100%]
> Updating / installing...
>    1:kernel-3.7.8-202.fc18            #################################
> [100%]
> grubby fatal error: unable to find a suitable template
> F: installkernel failed in module ovirtnode
> mkinitrd failed
> warning: %posttrans(kernel-3.7.8-202.fc18.x86_64) scriptlet failed, exit
> status 1

Have you been seeing this the entire time?  Because if you had, that would have been some really good information to include in the initial bug report instead of making us ask for info piecemeal and try to figure out what's wrong.

> yes, i changed it a while back to 10 so i can always have a working kernel ;)

yum won't remove the running kernel, so just boot into whatever a "good" kernel is you won't run the risk of being left without something booting (unless you don't use yum).

seeing this? no. its a cron job at 3am :D

10 is to make sure i always have a "good" kernel. 

and also i uninstalled ovirt about a month back.

hi

[marafa@notebook 91ovirtnode]$ pwd
/lib/dracut/modules.d/91ovirtnode
[marafa@notebook 91ovirtnode]$ ls
[marafa@notebook 91ovirtnode]$ 
[marafa@notebook 91ovirtnode]$ sudo dracut /boot/initramfs-3.7.7-201.fc18.x86_64.img 3.7.7-201.fc18.x86_64
[sudo] password for marafa: 
F: installkernel failed in module ovirtnode
[marafa@notebook 91ovirtnode]$ cd ..
[marafa@notebook modules.d]$ sudo rm -rf 91ovirtnode/
[marafa@notebook modules.d]$ sudo dracut /boot/initramfs-3.7.7-201.fc18.x86_64.img 3.7.7-201.fc18.x86_64
[marafa@notebook modules.d]$ 

[root@notebook ~]# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.7.8-202.fc18.x86_64
Found linux image: /boot/vmlinuz-3.7.7-201.fc18.x86_64
Found initrd image: /boot/initramfs-3.7.7-201.fc18.x86_64.img
Found linux image: /boot/vmlinuz-3.7.5-201.fc18.x86_64
Found initrd image: /boot/initramfs-3.7.5-201.fc18.x86_64.img
Found memtest image: /boot/elf-memtest86+-4.20
done

looks like this is problem with ovirtnode uninstallation. as it was not complete.

@josh thanks for taking the trouble to walk me through it

This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.

Closing this, as ovirt-node is not intended to get installed on a regular host.

Please reopen if necessary.