Search the VMware Knowledge Base (KB)
View by Article ID

OVF/OVAs of EFI-based Linux virtual machines fail to boot after deploying to new virtual machines with the error: EFI SCSI Hard Drive... unsuccessful (2061784)

  • 2 Ratings
Language Editions

Symptoms

  • Open Virtualization Format (OVF) or Open Virtualization Appliances (OVA) of EFI (Unified Extensible Firmware Interface) Shell based Linux virtual machines fail to boot after being deployed to new virtual machines.
  • Before loading the EFI Shell as a fallback option, the virtual machine console shows a boot failure error message similar to:

    Attempting to start up from: 
    EFI SCSI Hard Drive... unsuccessful.

Cause

When creating OVF or OVA files in current versions of vCenter Server, the NVRAM file is not exported with the OVF. This issue occurs because the EFI-based Linux virtual machines requires the NVRAM file to boot successfully.

Note: This will not impact any virtual machines which are Cloned, relocated via Storage vMotion, and is specific only to OVF/OVA exported EFI based Linux Virtual Machines. BIOS based virtual machines are not affected.

Resolution

This issue is resolved in vCenter Server 6.5.x, available at VMware Downloads
 
To work around this issue in earlier versions, copy the original NVRAM file from the source virtual machine into the new virtual machines folder.
 
To copy the original NVRAM file from the source virtual machine into the new virtual machines folder:

Note: This is only successful if the virtual disk layout has not changed between the original and newly created virtual machines.
  1. Take a copy of the original source virtual machine's NVRAM file (vmname.nvram) from the virtual machine folder.
  2. Deploy the OVF to the new virtual machine. For more information, see Deploy an OVF Template section in the vSphere Single Host Management Guide.
  3. Power on and attempt to boot the new virtual machine. This will fail. It will generated a new NVRAM file in the virtual machine datastore folder.
  4. Power off the new virtual machine.
  5. Copy the NVRAM file from Step 1 into the destination folder, and rename it accordingly to overwrite the existing NVRAM file created in Step 3.
  6. Power on and boot the new virtual machine.

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

See Also

Update History

11/9/2016 - vSphere 6.5 release has resolved this issue.

Language Editions

ja,2148147;zh_cn,2148227

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 2 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 2 Ratings
Actions
KB: