/build/static/layout/Breadcrumb_cap_w.png

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?
1 Comment   [ + ] Show comment

Comments

  • It sounds like the KBE is not able to talk to the VMWare Fusion virtual NIC.

    When you get the to the wpeinit phase, could you tell us what the error message is?
    might be 1231?

    -Make sure your VM is using an E1000 Adapter, do not use E1000E or VMXNET3

    type IPCONFIG
    -If you don't see any IP address, the KBE lacks the drivers needed. (we will need to confirm the Device exact Model, service tag will help).

    -If you see a 169 APIPA address, your DHCP is not providing a valid IP to the KBE.

    -If you see valid IP address, then you should not be seeing the 1231 error message. Try to type STARTNET.CMD and hit enter.


    Now, I have never seen a K2 SDA being used with VMWare fusion, I have seen Hyper-V, VMware, Virtual Box, VirtIO.

Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ