Hi, On 02/08/13 11:24, baban devkate wrote: > > I have installed Fedora 18 on ATA disk and booted it as NVMe disk
Do you mean, you installed F18 to an emulated IDE device, using qemu + OVMF, then shut down the guest, changed the disk type to NVMe, and rebooted? Where do you have NVMe from? It doesn't seem to be in upstream qemu. Did you take the driver from <http://lists.nongnu.org/archive/html/qemu-devel/2012-12/msg02268.html>? > by > executing boot loader at "fs0:\EFI\fedora\grubx64.efi"(where "fs0" is > ESP partiton on NVMe storage). I couldn't boot into OS, but dropped on > "dracut:/#" emergency shell prompt. > > These are errors were displayed on console..... > > dracut-initqueue[182]:warning could not boot > dracut-initqueue[182]:warning /dev/fedora/root does not exist. > dracut-initqueue[182]:warning /dev/fedora/swap does not exist. > dracut-initqueue[182]:warning /dev/mapper/fedora-root does not exist. > dracut:/# Dracut is the initial ramdisk (ram fs). https://fedoraproject.org/wiki/Dracut http://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#dracut.kernel https://dracut.wiki.kernel.org/index.php/Main_Page If you get this far, that means that grub2 has booted the kernel and the initial ramdisk, using UEFI services and your NVMe driver. At this point however dracut cannot switch from the initramfs to the real root fs. The most probable reason is that when this dracut image (initramfs) was built with livecd-tools, the kernel driver for NVMe devices was not included. You can verify this by mounting the F18 LiveCD (or the ISO image), and executing gzip -d < isolinux/initrd0.img \ | pax \ | grep kernel/drivers/block in its root directory. If it doesn't list "drivers/block/nvme.ko", then you've likely found the problem. A similar bug for virtio-blk was <https://bugzilla.redhat.com/show_bug.cgi?id=672936>, and the one for virtio-scsi was <https://bugzilla.redhat.com/show_bug.cgi?id=864012>. You could consider filing a similar Fedora bug for the nvme driver too. The fixes for the above bugs are: - http://git.fedorahosted.org/cgit/livecd/commit/?id=228f10f51c8e415d6ddf59e8f94c99f5867caa86 - http://git.fedorahosted.org/cgit/livecd/commit/?id=212bb38e5c03b98fb8b11ba9dbc70e5cdee616aa You could try (1) modifying livecd-tools similarly to the above git commits, so that it builds an ISO with an initramfs that includes nvme.ko, (2) actually building a new LiveCD <https://fedoraproject.org/wiki/How_to_create_and_use_a_Live_CD> -- I think this should happen on an existing F18 installation (physical machine or VM), (3) installing F18 in a VM (qemu+OVMF), from this LiveCD, to an emulated NVMe device. Laszlo ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
