Hyper V generation 2 machines don't boot

7

0

I am running windows server 2012 R2, and no matter what I do, I cannot get an Generation 2 machines up and running. They always fail to boot wit the message "boot failed efi scsi device"

I have found that I am supposed to "hold down a key when starting the VM" but

  1. This does not seem to do anything
  2. Its an issue even if I am not trying to boot from an ISO (I tried to convert a working generation 1 instance of Windows 10 preview and windows 8.1 to generation two machines, but then those failed to boot as well)

I have already tried turning secure boot on and off.

What else should I be looking for?

soandos

Posted 2014-12-17T13:17:41.763

Reputation: 22 744

@ramhound when it asks you what type of machine you want you pick a generation. Gen 2 machines have a much higher level of integration with the host – soandos – 2014-12-17T15:03:04.867

Have you tried creating a new Win8/10 Gen2 Vm from scratch yet? Also, did you use anything to convert form Gen1 to Gen2, or are you just trying to boot to an existing VHD using a newly made Gen2 VM? – Ƭᴇcʜιᴇ007 – 2014-12-17T15:41:36.203

@Ƭᴇcʜιᴇ007 Creating from scratch was the first thing I tried. As far as the migration, I used the powershell module from here: https://code.msdn.microsoft.com/windowsdesktop/Convert-VMGeneration-81ddafa2 (author is a hyper v dev)

– soandos – 2014-12-17T15:43:04.990

What do you have your the disk type set to for the VHD you're booting from? – I say Reinstate Monica – 2014-12-17T16:00:18.617

@Twisty, what do you mean? All drives in gen 2 are SCSI drives, and the underlying data is a .vhdx file – soandos – 2014-12-17T16:01:34.903

I don't have a 2012 R2 server handy so I wasn't sure if it was possible to accidently connect the VHD to an IDE controller, which as you obviously know won't boot on a Gen 2 VM. Just checking! – I say Reinstate Monica – 2014-12-17T16:04:05.233

Anything in the Hyper-V application event log show up when trying to boot the VMs? – I say Reinstate Monica – 2014-12-17T16:05:39.373

1@Twisty, nothing that seems out of the ordinary. Just information about the NIC and shutting down (under server roles, nothing under regular admin events) – soandos – 2014-12-17T16:09:53.287

Try the solution from this article that avoids the need to press a key. This constructs a special boot ISO, where in the \efi\microsoft\boot directory you rename cdboot.efi to cdboot_prompt.efi, and cdboot_noprompt.efi to cdboot.efi, then use the oscdimg command to recreate the media to boot with.

– harrymc – 2014-12-21T09:26:55.750

Answers

1

I found my solution doing this simple steps:

  • Create a Gen2 VM.
  • Create a vhdx and inserting (in creation process) the ISO file.
  • Try to boot the machine holding down the space bar (the machine not boot)
  • Turn off the machine
  • Edit the machine settings
  • Uncheck "Secure Boot"
  • Put the DVD in position 0 from the SCSI order.
  • Put VHDX in the position 1 from the SCSI order
  • The most important: Remove the network adapter.
  • Start the machine HOLDING DOWN THE SPACEBAR.
  • Install the OS.
  • After the OS installation, turn off the machine and recreate the network adapter (if you need that).

Ronaldo Ribeiro

Posted 2014-12-17T13:17:41.763

Reputation: 11

What is the importance of the space bar key and how can I recreate its effect in PowerShell? – Tomáš Hübelbauer – 2020-02-14T21:09:46.170

0

I used an iso image for Windows 2016 from February 2018, and it finally booted correctly without any issues. All previous Windows 2016 server iso disks refused to boot no matter the Hyper-V server (2012R2 or 2016) version was or what setting I change for the boot options.

Greg Kilgore

Posted 2014-12-17T13:17:41.763

Reputation: 1