Duplicate VMDK UUIDs are created when virtual machines are deployed from a template
search cancel

Duplicate VMDK UUIDs are created when virtual machines are deployed from a template

book

Article ID: 343814

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

This article describes a specific issue. If you experience all of the above symptoms, consult the sections below. If you experience some but not all of these symptoms, your issue is not related to this article. Search for your symptoms in the Knowledge Base or open a Support Request.


Symptoms:
When virtual machines are deployed from a template, you experience these symptoms:
  • Virtual machines have duplicate virtual disk (VMDK) ddb (disk data base) UUIDs
  • Backup software fails
  • In the vSphere client, you see entries similar to:
     
    • msg.disk.duplicateUUID:Virtual disks
    • "/vmfs/volumes/DATASTORE/VM_FOLDER/VM_NAME.vmdk" and "/vmfs/volumes/DATASTORE/VM_FOLDER/VM_NAME2.vmdk" have the same UUID. Virtual disks with the same UUID should not be assigned to a virtual machine because duplications can lead to problems when the guest boots. Make sure the virtual disks have unique UUIDs.
       
  • The virtual machine fails to power on and gets stuck at 95% in progress


Environment

VMware vCenter Server 4.1.x
VMware vCenter Server 5.1.x
VMware vCenter Server 6.0.x
VMware vSphere ESXi 6.5
VMware vSphere ESXi 5.1
VMware vSphere ESXi 6.0
VMware vCenter Server 5.0.x
VMware vCenter Server 5.5.x
VMware vCenter Server 4.0.x
VMware vSphere ESXi 6.7
VMware vSphere ESXi 5.5
VMware ESXi 4.0.x Embedded
VMware ESXi 4.1.x Embedded
VMware ESXi 4.1.x Installable
VMware ESXi 4.0.x Installable

Cause

This issue may occur when multiple virtual machines are deployed within a short period of time from the same template to different hosts. The backup application fails because some third party backup applications require the virtual machines to have unique UUIDs.

Resolution

This is a known issue affecting vSphere 4.x, 5.x and 6.x. Currently, there is no resolution.

To work around this issue, deploy virtual machines to the same host and then migrate them later. This ensures that each disk has a unique identifier.
 
To identify the virtual machines with the same UUID, run this command at the CLI via SSH to verify the UUID:
 
vmkfstools -J getuuid <vmname>.vmdk


If you have already identified the virtual machines with the same UUID, run this command to change the ddb UUID:
 
vmkfstools -J setuuid <vmname>.vmdk


Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box テンプレートから仮想マシンをデプロイすると重複する VMDK UUID が作成される
Adding a virtual disk to a virtual machine that already has a virtual disk with the same UUID fails

Powered by Wolken Software