Network boot from VMware VMXNET3.”7.0.x
The primary VMDK is unable to provide any valid boot information. This typically happens when the disk is corrupted or the operating system files on it are no longer accessible, causing the VM to skip the local disk and attempt a network boot.
Reimage the virtual machine with a fresh operating system. This ensures the VM starts with a healthy OS and resolves the boot device detection issue.
Note: You can also attach the disks as existing, and if there are any RDMs, add them to the newly reimaged VM.