Hyper-V: Virtual machine doesn't start over PXE IPv4

Kwadwo Anom 0 Reputation points
2024-04-09T13:47:24.8866667+00:00

I have set up a virtual server for deploying virtual machines using Windows Deployment Services. When I want to start a new virtual machine (Generation 2) via PXE IPv4, I encounter the attached screens.
Schermafbeelding 2024-04-09 141433

Schermafbeelding 2024-04-09 141554

Does anyone have an idea how I can fix this? Deploying a generation 1 virtual machine is successful. The G2 virtual machine has TPM enabled and the network adapter is designated first in the boot order.

Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,735 questions
Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
9,899 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Ian Xue 37,706 Reputation points Microsoft Vendor
    2024-04-10T08:17:31.16+00:00

    Hi Kwadwo,

    Thanks for your post. Based on my research, "Start PXE or IPv4" is a message that's generated when the VM's boot firmware can't find a bootable operating system on hard disk or CD/ROM. It's resorting to trying a network boot. That is why whatever you're trying to boot doesn't contain a bootable operating system. The VM's firmware is iterating across known hardware devices and hasn't come up with anything, so it's trying to boot from the network. In order to get to a solution, we're going to need more information from you about what you're trying to do.

    The message has three common causes:

    • You didn't install anything to the VM's hard drive. Fusion doesn't provide an operating system for virtual machines, It's up to you to download and install it like you would for a bare-bones physical machine.
    • You're trying to boot ISO installation media on Fusion running on M1/M2 Mac that is designed for Intel x64/x86_64 chips, which means there is wrong ISO architecture ISO to run on arm64 architectures. The solution to this is to make sure that your ISO installer is for arm64/aarch64 (ARM) architectures. not Intel. This is a common error if you have downloaded a Windows 11 ISO directly from Microsoft. The fine print there is that ISO is for Intel PCs only (you can thank Microsoft for not having a Windows 11 ARM ISO download). You can investigate the free CrystalFetch app (available in the Mac App store) to download an ARM version of Windows 11 that will work.
      • You're trying to install Windows 11 ARM, and missed the "Press any key to boot from CD/DVD" prompt. The solution to that is to move keyboard focus to the VM (either by clicking into the VM or typing Command-G) and then pressing any key. 

    Kindly check the above potential root cause and see if it takes effct.

    Best Regards,

    Ian Xue


    If the Answer is helpful, please click "Accept Answer" and upvote it.

    0 comments No comments

  2. Kwadwo Anom 0 Reputation points
    2024-04-10T11:06:52.8866667+00:00

    Indeed, I haven't installed any operating system on the virtual hard disk. I am trying to install Windows 11 through Microsoft Deployment Tool/Windows Deployment Services and I am doing this on a Windows 11 laptop.

    0 comments No comments

  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.