I have seen the same issue. The instructions need to be updated. The original vmdk path may remain in the .vmsd and .vmsn files. -Andy
On Wed, Feb 26, 2014 at 10:08 AM, Waldron, Michael H <[email protected] > wrote: > I got around this error by deleting the snapshot on the VM first. > Curious that I never had to do that before. > > Mike Waldron > Systems Specialist > ITS - Research Computing Center > University of North Carolina at Chapel Hill > > On 02/26/2014 08:31 AM, Waldron, Michael H wrote: > > I have been using the procedure for resizing hard disks for VM images on > > ESXi hosts documented at > > > https://cwiki.apache.org/confluence/display/VCL/How+to+Increase+the+Size+of+a+Virtual+Machine+Hard+Drive+Under+VMware+ESXi > > with no problems in the past. > > > > Suddenly, I'm now getting this error in vSphere client when I try to > > remove the original hard disk of the VM, and add the copy that was made > > from it and resized: > > > > "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." > > > > This is after making an imaging reservation for the image, shutting down > > the vm, making a copy of the current disk and resizing it using: > > vmkfstools -i original.vmdk copy.vmdk -d thin > > vmkfstools -X 35G copy.vmdk > > > > I can't think of anything that has changed in the setup (VCL 2.3.1 or > > ESXi) since I last did this successfully. I've tried with several > > different images on differ ESXi hosts and get the same result. I've > > tried on both ESXi 5.1 and 5.5 hosts. > > > > Has anyone else seen this? > > > >
