This project is read-only.


AutomatedLabs 3.1 and 3.3 betas both have EFI errors on hyper-v


Hi there.
Every time I install the 3.1 beta or 3.3 beta, and try to do the single server 2012r2 script, or any of the other examples, I get:
"Boot Failed. EFI SCSI DevicePXE Network boot using ipv4
PXE-E18: Server response timeout.
Boot Failed. EFI Network.
Boot Failed. EFI SCSI Device.
No Operating system was Loaded. Press a key to retry the boot sequence..."

Looks like the script/cmdlets are using generation 2 now, which is great, but why the errors?

file attachments

Closed Jan 4, 2016 at 9:12 PM by raandree


dagryph wrote Aug 10, 2015 at 5:56 PM

Hmm, still seeing these errors on Windows 10 Enterprise with 3.3 beta.

wrote Aug 10, 2015 at 10:35 PM

dagryph wrote Aug 10, 2015 at 10:35 PM

Even with the 3.5 (current source available as of 8/10/2015) still shows the attached, never finishes since it cannot find the boot files.

raandree wrote Aug 10, 2015 at 10:51 PM

Sorry, but I know a lot of people using AutomatedLab with various operating systems and without this issue.

What is the operating system of your host machine? Have you been able to deply a lab or does every sample script fail?

dagryph wrote Aug 10, 2015 at 11:41 PM

This is a clean install, x64 Windows 10 Enterprise RTM install, with Hyper-V enabled. Out of the box, this does not function. Looks like the EFI partitions are not set up correctly in the vhdx file.

dagryph wrote Aug 10, 2015 at 11:43 PM

What OS are you using for -generation 2 to work?

dagryph wrote Aug 10, 2015 at 11:47 PM

Every sample script fails. The last version that works (albeit with -generation 1 VMs) was 2.2. I would love to upgrade my labs to use the latest, but I can't until this generation/EFI bug is fixed. I'm more than willing to help fix. :) AutomatedLab is one of my favorite projects.

raandree wrote Aug 11, 2015 at 7:52 AM

We are only going for Gen2 VMs if the following condition is true:
if ($hostOsVersion -ge 6.3 -and $machine.OperatingSystem.Version -ge 6.2)
    $parameters.Add('Generation', 2)
    $parameters.Add('Generation', 1)
Have you deleted the base images? Having Gen1 base images that are used by a Gen2 VMs created this kind of problem.

dagryph wrote Aug 11, 2015 at 11:05 PM

No, the base images are intact. Just no EFI files in the right places inside the VHDX for the VM to boot.

sintaxasn wrote Sep 4, 2015 at 3:28 PM

I'm seeing the exact same issue, running under Windows 10 Enterprise. During the "Creating Base Images" section, I see the following...
10:27:11|00:00:18|00:00:00.000| - Creating base image for operating system 'Windows 8.1 Pro'Format-Volume : Invalid Parameter
Activity ID: {a681dbb5-ee14-4f84-9dd2-29d4b3608e97}
At C:\Users\xxxxxx\Documents\WindowsPowerShell\Modules\AutomatedLabWorker\AutomatedLabWorkerDisks.psm1:79 char:47
+ ... Partition | Format-Volume -FileSystem NTFS -NewFileSystemLabel 'Windo ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (StorageWMI:ROOT/Microsoft/...age/MSFT_Volume) [Format-Volume], CimExce
    + FullyQualifiedErrorId : StorageWMI 5,Format-Volume
Could this be a Windows 10 specific issue?

wrote Sep 8, 2015 at 11:07 PM

raandree wrote Nov 17, 2015 at 10:56 PM

A bit more than a hand full of people have reported this. Unfortunately we cannot reproduce the issue on any available machine so it is very hard to track it down.

If you have some more data on the problem we can try to fix it.

raandree wrote Jan 4, 2016 at 9:12 PM

EFI problems should be fixed now.

wrote Jan 4, 2016 at 9:12 PM