Workaround: PXE Boot your VMware Fusion VM

[Last Reviewed: 2019-02-20]

If you attempt to PXE boot a virtual machine using VMware Fusion, you might see this error:

Error Code: 0cx0000001

Some quick research showed that I’d have better luck using the ‘vmxnet3’ network adapter rather than the default ‘e1000e’ adapter. I had no problem adding the vmxnet3 to our WinPE image, but… it was Friday. Read-only Friday. How could I image this machine before the weekend?

Here’s a workaround you can try. It assumes that your WinPE image already has Intel Net drivers. We’ll add a second NIC. The default NIC, using e1000e, will be used during WinPE; the secondary NIC, using vmxnet3 will be used for PXE. Once your VM has been created and VMware Tools has been installed, you can remove the second NIC.

  1. Create your Virtual Machine as usual, then open your VM settings
  2. Add another network adapter (be sure they are both set to “Bridged Networking”)
  3. Close VMware Fusion, and navigate to where the VM is stored on disk (the default is ~\Virtual Machines). Right-click on your Virtual Machine and select “Show Package Contents”.
  4. Find the .vmx file in that folder. Right-click and open it with your text editor of choice.
  5. Look for the line ‘ethernet1.virtualDev = “e1000e”‘ — change e1000e to vmxnet3
  6. Save your changes, close your text editor, then re-open VMware Fusion
  7. If your OSD process requires a TPM, now you can turn on Encryption and then add the TPM (don’t do this before you edit the .vmx file, otherwise it will be encrypted!)
  8. Under Startup Disk, select “Network Adapter 2” as your default
  9. Power on your VM and OSD away!

Once OSD completes, install VMware Tools and then you can remove your 2nd network adapter.

Enjoy your new virtual machine! Come Monday you can add that vmxnet3 driver to WinPE. ☺️

Jacob

2 thoughts on “Workaround: PXE Boot your VMware Fusion VM”

  1. Hrmm.. No luck here. Created a new Win 10 x64 machine, no OS. Added the second network adapter, set both to bridged (autodetect), changed the second one to “vmxnet3” and restarted Fusion. The message I get is “EFI Network 1… unsuccessful”. Fusion 11.0.2, Macos 10.14.4. Thoughts?

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.