[German]In Hyper-V, you may not be able to install guest operating systems in Generation 2 VMs. The installation process ends with a 'PXE Network boot using IPv4 …' message.
The error image
I come across the corresponding error description in this German administrator.de post a few days ago:
Setup VM W2016 does not start in Hyper-V 2016
is just sitting over my new server and trying to install it a VM at the host. I wanted to install a W2016 VM (as Generation 2 over an ISO) as a guest os in Hyper-V … briefly saw the prompt to press any key to setup via the "optical drive" … and then I'm constantly in a black screen with "PXE Network boot using IPv4 ( ESC to cancel). Performing DHCP Negotiation …." please.
It looks like the prompt to press a key is not being passed to the virtual machine. Then the VM will not boot from the mounted ISO file and attempt a PXE network boot, which of course fails.
If you search the internet for this error message, you will get several hits at once. The Technet forum thread here discusses the issue – and this blog post also deals with the topic. The above screenshot is from this blog post.
Suggested solutions for the problem
In this blog post you will find a hint to set the Secure Boot option to "Microsoft UEFI Certificate Authority" in the security settings or to disable the Secure Boot.
The above screenshot is also from the contribution of scomandothergeekystuff.com, but refers to Ubuntu there. On German WindowsPro you can find this article, which also deals with this topic. There you can find the hint to convert the whole thing to Gen 1 VMs – which is not very helpful. Also in this article someone deals with the configuration of the VM, but aims at a legacy network adapter for the network.
On administrator.de, one person has found a completely different solution – he only makes sure that the keystrokes of the host are forwarded to the VM and the guest. He writes about this:
Some suggestions found in the network (uncheck secure start, move ISO file) … have brought nothing. Note: In the HOST settings under User configure the keyboard for use with the "physical" computer …
Maybe it will help one or the other affected person out of a mess.
Cookies helps to fund this blog: Cookie settings