one of my cusomer was not able to power on a virtual machine, which was corrupted during vMotion to other host. The vMotion hang at 72% for 2 hour.\u00a0The biggest problem was, that this virtual machine is critical for my customer… yes we have backup 1 day old, but… The vm was invalid, so i was decided to remove it from inventory and add to inventory, but all 3 virtual disks showed 0 MB.<\/p>\n
Cannot open the disk '\/vmfs\/volumes\/XXX\/virtualmachine\/virtualmachine-000001.vmdk' or one of the snapshot disks it depends on. Reason: The parent virtual disk has been modified since the child was created.<\/pre>\nnice try to power on…<\/p>\n
I have problem with CID mismatch,\u00a0which is triggered by vm migrations like\u00a0Storage vMotion or Migration, VMware software error, or user action. The CID (content ID) of the parent disk of vm does not match the corresponding parent content ID in the child (snapshot). Yes, my customer have 2 snapshots :)) and the vm runs on the latest snapshot.<\/p>\n