Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

.vmx file of an encrypted VM is decrypted after a scheduled VM compatibility upgrade (77257)

Last Updated: 4/2/2020Categories: TroubleshootingTotal Views: 6648Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

After a scheduled VM compatibility upgrade of an encrypted VM, the .vmx file will have the non-empty line for 'dataFileKey’ field as shown here:

$ cat <VM-Name>.vmx | grep 'dataFileKey' | wc -l
1

$ cat <VM-Name>.vmx | grep 'virtualHW.scheduledUpgrade.state'
virtualHW.scheduledUpgrade.state = "done"

Note: Only the encrypted VM Home (.vmx file) is affected. Any encrypted disks associated with that VM remain unaffected (encrypted). This issue does not impact unscheduled VM Compatibility upgrades of encrypted VMs.

Any subsequent reconfiguration tasks on this VM may result in errors. For example, adding a CD/DVD drive to this VM will result in
"Virtual machine has encryption enabled, but the virtual machine home doesn't have an encryption profile or doesn't have a configured security device (like TPM)".

Cause

A bug in scheduled VM compatibility upgrade of encrypted VM results in .vmx file being written in unencrypted state.

Resolution

This issue is resolved in vSphere 6.5 U3 / vSphere 6.7 U2 / vSphere 7.0. available at VMware download .

Workaround

To workaround this issue:

There are two ways to manually remediate the affected VM. But, it is advised to upgrade to recommended patch release.

Solution 1: [Re-apply storage policy]

Ensure the VM is powered-off.

Note: Make a note of the current configuration of each disk associated with the VM (i.e. whether encrypted or not).

Unregister the VM from vCenter.

Re-register the VM in vCenter back to the same host as before.

Re-apply the  encryption policy (e.g. “VM Encryption Policy”) to the VM Home and to each of the disk which are intended to be encrypted.

Note:  The .vmx file now must be re-encrypted. Specifically, 'dataFileKey' should not be present and instead we must have 'encrypted.keySafe'. The .vmx file uses a new/different key that the one that was used before.

Solution 2: [Move all disks]

Ensure the VM is powered-off.

Create a new encrypted VM with no disks.

Note:similar to the original VM.

Remove all the disks from the old VM, and attach them to the new VM. The storage policy of each disk must remain the same as before.

Note:  The .vmx file now must be re-encrypted. Specifically, 'dataFileKey' should not be present and instead we must have 'encrypted.keySafe'. The .vmx file uses a new/different key that the one that was used before.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
无法从 NDES 服务器生成 SCEP 证书 (80935)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 7.0.0

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

Take Our Survey

Support Assistant