My guess is that we have no legacy bus controllers and no way to install the enlightened modules that would access the controller we do have so we wind up dead in the water. boot/config-3.17.86_64 and looking in that shows config files lying around nor does scripts/extract-ikconfig vmlinuz0 work.īooting the Workstation ISO on a Gen 1 VM to bash and poking around shows initrd0.img contains next to nothing in terms other than microcode and I couldn't find out what the kernel was configured with because there are no. Sadly it looks as if the serial console has gone away with Generation 2 VMs removing a useful debugging tool :-(įurther, there seems to be no way of displaying the bootloader menu before the kernel starts (I tried holding down shift, alt, escape and tab but none of these had any effect). The Fedora 21 Workstation ISO also boots but does not respond to the keyboard and bails out with an error message of comment #13 (sending ctrl-alt-del didn't work for me either). If Secure Boot is disabled then the Fedora 21 Server ISO boots to a GUI. When using a Generation 2 Hyper-V VM neither the Fedora 21 Server nor Workstation ISOs will boot if Secure Boot is enabled - the UEFI "BIOS" gives the result described in the Actual results of comment #1. I can confirm Carwyn's comment with the final release of Fedora 21 install media. In the time it's taken to write this I've successfully installed Fedora 21 Server onto a Gen2 HyperV VM on a Windows 8.1.1 host (i.e. It seems reasonable that a server would be more expected to be installed on HyperV than a workstation. Interacting with the virtual machine's keyboard device failed."Ĭould it be that the virtual keyboard driver mentioned in comment #7 is in the server initrd but not in the workstation initrd? "Could not send keys to the virtual machine. Keyboard input at the dracut:/# prompt after the timeout does not work.Īt any point attempting to send Action -> Ctrl+Alt+Delete generates a dialog message: has a long pause at the Fedora boot logo then times out showing hv-gen2-error.png (attached). Interestingly the Fedora-Server-DVD-x86_64-21.iso from:īoots into anaconda on a hyper v gen 2 VM with mouse and keyboard working but: The Ubuntu 14.04 ISO boots directly in a Generation 2 VM.Īttaching /sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f. However the moment you turn on Secure Boot you will no longer be able to boot the VM. In the extreme scenario, if you take the Fedora cloud image in a Generation 1 VM, update it, install various utilities, convert the disk from MBR to GPT using gdisk, create a FAT32 partition on the end with and EFI id, format the partition, mount it on /boot/efi, install grub2-efi and shim, run something like grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg etc., hack up /boot/efi/EFI/fedora/grub.cfg so linux -> linuxefi etc, attach the disk to a Generation 2 VM and boot it then you will have a Fedora booting in a Hyper-V 2012 Generation 2 VM. You will seeīooting `Test this media & start Fedora Live' Click on Firmware at the left and untick Enable Secure Boot at the right, Click OK, right mouse button on the VM and click Start. If you press the right mouse button over the VM and go to Settings. Double click the newly made VMs name so that the Virtual Machine Connection window appears.īoot Failed. Press the right mouse button over the newly created VM and select Start.ġ0. Tick Install an operating system from a bootable image file and select Fedora-Live-Desktop-x86_64-20-1. At the top right select New -> Virtual Machine.Ĥ. Version-Release number of selected component (if applicable):ġ. If you are trying to use a Microsoft Hyper-V 2012 R2 Generation 2 guest you will be unable to boot Fedora while secure mode is present. Switch to the Downloads directory as whatever we download from the browser saves in that, by default./sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |