some time I clone VM will Reconfigured VM disk cause boot fail

This post was originally published on this site

I have running vcenter 6.7

 

and when I cone VM

normal task log like this

 

 

Clone virtual machine

Status:

Completed

Initiator:

VSPHERE.LOCALAdministrator

Target:

VM1

Result:

[object Object]

Server:

vcsa.local

Related events:

2020/09/04

H10:49:40

Clone of VM1 completed

2020/09/04

H10:49:40

Virtual machine VM1 disks consolidated successfully on 192.168.125.121 in cluster Cluster in Datacenter.

2020/09/04

H10:48:51

Assign a new instance UUID (50232538-009c-93a6-9829-7c97def40590) to test123

2020/09/04

H10:48:51

Assigned new BIOS UUID (42237531-ed1f-a55a-7dca-bf88cf66fe12) to test123 on 192.168.125.111 in Datacenter

2020/09/04

H10:48:51

Cloning VM1 on host 192.168.125.121 in Datacenter to test123 on host 192.168.125.111

2020/09/04

H10:48:38

Task: Clone virtual machine

 

 

but some time

log have additional information is  Reconfigured  ……

020/09/02 H5:08:15

Clone of VM1 completed

2020/09/02 H5:08:15

Virtual machine VM1 disks consolidated successfully on 192.168.125.121 in cluster Cluster in Datacenter.

2020/09/02 H5:08:12

Reconfigured 123 on 192.168.125.123 in Datacenter. Modified: config.hardware.device(2000).backing.fileName: “ds:///vmfs/volumes/5c544e67-ca1f903a-c26b-246e96d82670/123/123_3.vmdk” -> “ds:///vmfs/volumes/5c54c8cf-d115ec56-14a9-246e96d85ddc/VM1/VM1.vmdk”; config.hardware.device(2000).backing.datastore: ‘vim.Datastore:fca6d527-0bc5-4d1d-bf87-08a27619ff81:datastore-49’ -> ‘vim.Datastore:fca6d527-0bc5-4d1d-bf87-08a27619ff81:datastore-50’; config.hardware.device(2000).backing.uuid: “6000C293-ed6c-4bbe-220b-f7e8b5164754” -> “6000C29d-20cc-a673-d0c0-ecf6e170fb6f”; config.hardware.device(2000).backing.contentId: “8ee760b8e334a81831951cb38439e344” -> “b86c49471c3e95e2d36780e32564c034”; config.hardware.device(2001).backing.fileName: “ds:///vmfs/volumes/5c544e67-ca1f903a-c26b-246e96d82670/123/123_5.vmdk” -> “ds:///vmfs/volumes/5c54c8cf-d115ec56-14a9-246e96d85ddc/VM1/VM1_1.vmdk”; config.hardware.device(2001).backing.datastore: ‘vim.Datastore:fca6d527-0bc5-4d1d-bf87-08a27619ff81:datastore-49’ -> ‘vim.Datastore:fca6d527-0bc5-4d1d-bf87-08a27619ff81:datastore-50’; config.hardware.device(2001).backing.uuid: “6000C298-e462-2d32-3acd-2d7249c7aa74” -> “6000C291-92ad-d0a6-ad5d-44d2d1666230”; config.hardware.device(2001).backing.contentId: “3f6d2fcfc84a25cd504b13cd7a48ccf0” -> “fe542a0847061c52b2f937385ec6283c”; Added: Deleted:

2020/09/02 H5:05:03

Assign a new instance UUID (5023856b-1b5d-7a63-71ea-ce4dc006883e) to 123

2020/09/02 H5:05:03

Assigned new BIOS UUID (42232bb5-9e63-1512-2bca-4e3e2e6d73d5) to 123 on 192.168.125.123 in Datacenter

2020/09/02 H5:05:03

Cloning VM1 on host 192.168.125.121 in Datacenter to 123 on host 192.168.125.123

 

 

 

if clone task have additional Reconfigured action

VM “123” ‘s virtual disk is use VM1’s virtual disk

when VM “123” try boot will get error “the disk is lock by VM1”

 

so why some time clone vm task , the VM configure will be Reconfigured ??

 

my vcenter version is  6.7.41000 Build 14836122

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.