When attempting to remove a hard disk from the virtual machine, an error message stating “Invalid configuration” is encountered.
The error indicates that one of the parent disks is included in a snapshot of the virtual machine.
"Invalid configuration for device '0'. Cannot remove virtual disk from the virtual machine because it or one of its parent disks is part of a snapshot of the virtual machine"
In environments where the target VM is a vCenter Server Appliance (VCSA), consolidation attempts may cause the management interface to freeze or become unresponsive (ping drops) before failing with an "Unable to access file since it is locked" error. This typically indicates that orphaned snapshots are being held by a third-party backup process
VMware vSphere ESXi 6.x
VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x
The affected VM will reference the snapshot vmdk.
It's a recognized issue that a snapshot VMDK cannot be deleted without consolidation if one or more of its parent disks are included in the virtual machine's snapshot.
This condition frequently occurs when a backup proxy VM (e.g., Veeam) utilizing "HotAdd" transport mode fails to unmount the disks after a backup job. If a storage outage or backup failure occurs, the proxy retains a Read-Only lock on the base disks. This creates a metadata conflict: the proxy cannot release the disk because it is part of an active snapshot chain, and the target VM cannot consolidate because the proxy holds a lock.
First, we need to consolidate the snapshots of the virtual machine.
Consolidation integrates the changes between snapshots and the previous delta disks into the base parent disk, merging them with the base virtual machine disk.
Once the consolidation is complete, we will be able to successfully remove the disk from the virtual machine.
You may came across similar below error when you try to remove the disk from backup proxy server for disk consolidation issue.
"Invalid configuration for device '0'. Cannot remove virtual disk from the virtual machine because it or one of its parent disks is part of a snapshot of the virtual machine"
As workaround you can follow the below steps:
For vCenter Server Appliances, it is a Broadcom best practice to utilize Native File-Based Backup (VAMI) instead of image-based snapshot backups to avoid "stuns" and stale "HotAdd" locks.