Expanding vmdk file created by V2V converter
Posted: Sat Oct 23, 2010 1:00 am
I'm testing various processes for converting our vhd files to vmdk files to be used with ESXi v4.1. (The vhd files are Virtual Iron exports.)
The V2V Image Converter converts these files successfully. However, in some cases, we also want to expand the size of the disks. Unfortunately, ESXi does not currently appear to natively support expanding IDE disks (what Virtual Iron had us use). So I've been testing the use of VMware Workstation's "vmware-vdiskmanager" utility to do this. Though expansion works with vhd images converted to vmdk by either itself or WinImage trialware, it produces an error when working with the vmdk's produced by the V2V converter:
Failed to expand the disk 'c:\temp\sw\beta.vmdk': An error occurred while writing a file; the disk is full. Data has not been saved. Free some space and try again (0xd00000008).
I have about 120GB free on the drive. I'm running the vmware-vdiskmanager on Win7 64bit from inside an elevated Administrator command prompt. For extra measure, I've also cacl'd the folder to make sure my user account isn't hampered by weird Windows file perms.
Any ideas?
Thanks.
The V2V Image Converter converts these files successfully. However, in some cases, we also want to expand the size of the disks. Unfortunately, ESXi does not currently appear to natively support expanding IDE disks (what Virtual Iron had us use). So I've been testing the use of VMware Workstation's "vmware-vdiskmanager" utility to do this. Though expansion works with vhd images converted to vmdk by either itself or WinImage trialware, it produces an error when working with the vmdk's produced by the V2V converter:
Failed to expand the disk 'c:\temp\sw\beta.vmdk': An error occurred while writing a file; the disk is full. Data has not been saved. Free some space and try again (0xd00000008).
I have about 120GB free on the drive. I'm running the vmware-vdiskmanager on Win7 64bit from inside an elevated Administrator command prompt. For extra measure, I've also cacl'd the folder to make sure my user account isn't hampered by weird Windows file perms.
Any ideas?
Thanks.