Unbootable virtual machine? Here are three useful guestfish commands to help. (You can also consider using virt-rescue).
1. Edit /boot/grub/grub.conf
$ guestfish -i Rawhide Welcome to guestfish, the libguestfs filesystem interactive shell for editing virtual machine filesystems. Type: 'help' for help with commands 'quit' to quit the shell ><fs> ls /boot/ System.map-184.108.40.206-9.fc13.x86_64 System.map-220.127.116.11-21.fc13.x86_64 System.map-2.6.33-0.40.rc7.git0.fc13.x86_64 config-18.104.22.168-9.fc13.x86_64 config-22.214.171.124-21.fc13.x86_64 config-2.6.33-0.40.rc7.git0.fc13.x86_64 [...]
Use the “edit”, “emacs” or “vi” commands to edit grub.conf:
><fs> vi /boot/grub/grub.conf
From here you can change the boot kernel, change it to boot in single user mode, enable the grub menu, remove the “rhgb quiet” option so you can see boot messages, and much more.
2. Look at the /init script
When the kernel panics because it cannot mount root, it’s often because the initrd or initramfs is broken in some way. Two commands help here:
><fs> initrd-list /boot/initramfs-2.6.33-0.40.rc7.git0.fc13.x86_64.img | less ><fs> initrd-cat /boot/initramfs-2.6.33-0.40.rc7.git0.fc13.x86_64.img init | less
The first command lists all the files in the initrd, which lets you see if the right drivers got included for the (virtual) hardware. The second command lists out the init script — which is the shell script that runs first before the OS proper starts to boot.