Start PXE Over IPv4 in a Hyper-V VM
A Hyper-V Generation 2 machine can be compared to a running UEFI workstation. The UEFI workstation would not be able to communicate with legacy PXE, but only with UEFI. This is the same for Hyper-V Generation 2 machines. This guide explains how to start PXE over IPv4 on Generation 2 Hyper-V VMs.
If your network is configured to deploy boot images using legacy methods, you will need to configure the hardware of the virtual machine.
This blog post describes how to accomplish this.
CREATE VIRTUAL SWITCH
First you need to create a virtual switch. This is required for the Virtual Machine to be able to communicate with the network. If you already have created a virtual machine for your network, you can skip this step. Start by right-clicking the Hyper-V host in Hyper-V Manager and selecting Virtual Switch Manager.
Create a new Virtual Switch. Select External. External is similar to “Bridged” if you are using other virtualization platforms.
Give the new Virtual Switch a name. I named mine “Bridged”.
By default, there is only a “Standard Network Adapter” installed on the Virtual Machine, but for PXE functionality you are required to add a Legacy Network Adapter.
Go to the Legacy Network Adapter that you just added and specify that it should use the Virtual Switch that you just created.
6. Last but not least, you should change the BIOS boot priority to make sure that the Virtual Machine always tries to boot first using the “Legacy Network Adapter”. Just select the “Legacy Network Adapter” and move it to the top using the buttons.
START VIRTUAL MACHINE
Start your Virtual Machine and now PXE boot should work 🙂
- Hyper-V issue when starting virtual machine from dowloaded ISO file
- 2 Solutions for solving issue with Hyper-V virtual machine and Secure Boot on non-supported operating systems
- Don’t forget this step if you want SCCM clients to boot using PXE
- How to create and configure a Hyper-V VM using Powershell
- Hyper-V failure error
About the author
Daniel Classon works as a Senior Consultant at Mansoft, focusing on Microsoft Configuration Manager, Windows 10 and Powershell