Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Virtual Machine Booting with an EFI error VMware vSphere ESXi 5.x

Summary: This article provides information on issues with a virtual machine booting with an EFI error VMware vSphere ESXi 5.x.

This article may have been automatically translated. If you have any feedback regarding its quality, please let us know using the form at the bottom of this page.

Article Content


Symptoms

Issue : 

While attempting to boot a virtual machine (VM), you see the following error in the console :

EFI virtual disk (0.0) ... unsuccessful.


The VM does not proceed to boot.

SLN283097_en_US__1I_VMware_EFIBOOT_JP_V1a

Resolution : 
 

 

Note: This KB can be applied on Vmware ESXi host only. It is not compatible with Vmware Workstation and a Mac OS installation.

 



The issue is related to the VMX structure which is corrupted. You have to regenerate a new file following these steps:
Create a new VM using the same numbers and options (EFI mode, CPU, memory, etc) and use the existing VMDK(s).

To proceed, you need to power off the original Virtual Machine and create a new Virtual machine :

SLN283097_en_US__3wm1 (1)


On the configuration step, select "Custom" Option :

SLN283097_en_US__4wm1 (2)


Fill each next option with the same option than the original VM. On the step "Select a Disk" , and them use the option "Use an Existing Virtual Disk"

SLN283097_en_US__5wm1 (3)


And select the .vmdk file located on the datastore where is located the original VM.

SLN283097_en_US__6wm1 (4)


Finish the installation.

If you need to add additional VMDKs, then you can do so after the VM has been created, before you power it on


 

Cause

No cause information.

Resolution

Ask the community on the "Enterprise Operating Systems" forums

Article Properties


Affected Product

Servers, PowerEdge

Last Published Date

11 Mar 2021

Version

3

Article Type

Solution