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

Modified NVRAM Settings Might Prevent Virtual Machine from Powering-On (1503)

  • 5 Ratings


Why is my deployed virtual machine not able to boot its operating system?


This problem can occur if the NVRAM file is not copied to a new location when you migrate, clone or deploy a virtual machine.

The NVRAM file contains information such as BIOS settings. It is not copied to the target host when a virtual machine is migrated, migrated with VMotion, cloned or deployed from a template.

Changing the boot sequence of the original virtual machine, for instance, modifies the NVRAM settings. Since the NVRAM file is not copied as part of the migration or cloning process, the destination virtual machine might receive a different boot sequence and consequently cannot find the disk with the boot partition.

If you have settings in NVRAM that are not default values, you need to manually copy the original NVRAM file to the target host.

  1. Copy the NVRAM file to a temporary location before you perform the provisioning action on the virtual machine.
  2. Perform the migration, cloning or deploying from a template.
  3. Copy the saved NVRAM file to the new location after the migration, cloning or deployment completes.

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.


  • 5 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.
  • 5 Ratings