Description of problem: I attempted an installation of F11 Alpha in a KVM VM on F10. This resulted in a non-bootable instance. Booting a live CD and examining the installation, it looks like grub is the culprit: # grub-install /dev/vda No suitable drive was found in the generated device map. Version-Release number of selected component (if applicable): grub-0.97-37.fc11 How reproducible: Always Steps to Reproduce: 1. Boot F11 Alpha live CD 2. Install to disk 3. Reboot Actual results: Unbootable system Expected results: Bootable system Additional info:
(In reply to comment #0) > I attempted an installation of F11 Alpha in a KVM VM on F10. This resulted in > a non-bootable instance. Could you give some more details on how you did this install? This should work fine. > Booting a live CD and examining the installation, it looks like grub is > the culprit: > > # grub-install /dev/vda > No suitable drive was found in the generated device map. What does /boot/grub/device.map contain?
*** This bug has been marked as a duplicate of bug 479760 ***
I don't think this is a dupe, this is a different bug. On a very recent Fedora 13/Rawhide hybrid box I can reproduce the bug that Matt saw: # grub-install --root-directory=/sysroot /dev/vda1 Probing devices to guess BIOS drives. This may take a long time. No suitable drive was found in the generated device map. /boot/grub/device.map contains: (fd0) /dev/fd0 An easy reproducer for this with guestfish >= 1.3: $ rm -f test1.img $ guestfish -N fs -m /dev/vda1 grub-install / /dev/vda1 (Add the '-v' option on the guestfish command line to get a lot more detail).
Created attachment 419330 [details] script that creates /boot/grub/device.map file I found that this works if you manually create a device.map file, eg: mkdir /boot mkdir /boot/grub upload -<<__end__ /boot/grub/device.map (hd0) /dev/vda __end__ grub-install / /dev/vda This appears to be related to bug 479760, marked as fixed but this might have regressed. I have posted a patch which changes the documentation to note the extra steps that users may need to take if they encounter this error message: https://www.redhat.com/archives/libguestfs/2010-June/msg00036.html
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping