Systems Deployment Question
VMWare Fusion EFI issue with KBE
03/22/2018 1063 views
I have an issue with vmware fusion pxe booting efi to k2000. The bootloader kicks off successfully but following the winpeinit script after loading network and waiting for network to settle I am unable to lease an address. I cannot ping any addresses if I manually apply an IP via netsh either. This same kbe works on other physical devices to successfully capture/deploy images from either legacy or uefi booting and I am also able to boot this vm with legacy bios and successfully load the k2000 capture/deploy utility, I just can't connect to the network from any KBEs booted from uefi firmware inside vmware fusion.
Suspecting the issue was with vmware fusion, As a test I built a wds server, loaded winpe boot images and imported the same driver packs I have in the k2000 environment. I was able to successfuly PXE boot from UEFI firmware and complete a win10 installation. I can boot that win10 environment and successfully connect to the network from inside that OS.
In my device list, I see my vm boot history from the legacy side and can verify the platform/device info is accurate but there seems to be no trace of the UEFI boot attempts. I was suspecting a possible platform identification issue when booting from UEFI but as stated WDS handles it correctly so I am still unsure if the issue lies with k2000 or vmware fusion. my next step is to try to efi boot a vsphere guest from another environment but its sort of a hassle to setup so I am dreading it. Anything I am overlooking?
Be the first to answer this question