Unable to PXE with Hyper-V VM
Hello,
I'm trying to make a new image, and for some reason I cannot PXE to my SDA. Whenever I add the legacy network adapter, and try to network boot it pauses on DHCP and generates a PXE-E53: No boot filename received. I can ping the appliance from the VM. Kind of at a loss.
-
I've just tried to PXE boot a gen 2 VM and it fails quickly suggesting it's not happy with the Secure Boot signature coming from SDA/RSA 9.1. Is Hyper-V supported as a host platform??? - mcnaugha 1 year ago
Answers (4)
Hi, you can try this:
The idea is checking if the target PC is receiving the right information from the DHCP (boot file, DNS, an IP in a valid range etc)
As a side note, make sure the VM is a gen 2. I've had problem with gen 1 VMs.
Hello Cheecho,
Can you please confirm if the suggested answer has worked for you?
Please remember that you can always create a support case so that one of our engineers can assist you with that issue. Two ways you can use to create a support case: via the web or via phone.
Best regards,
Mauricio.
The VM is unable to locate a DHCP with PXE boot instructions.
Make sure that VM is getting to the DHCP\Network capable of PXE booting.
Also Hyper-V VMs are not good for PXE Booting, I would rather use VMWare, ESXi, or Acropolis Nutanix.
(You could also try with VMWare workstation or Oracle's Virtual Box)
Hey Cheecho
With Hyper-V, I have had luck creating a new virtual switch and changing the setting on the VM to the new virtual adapter. Also, make sure to change the Firmware Boot order to the network adaptor at the top of the list. Sometimes I have to switch it back, but between the two I can always get it to PXE boot. Hopefully this might help.