Welcome to the Community,
from where (which application) did you import the .vmdk file(s)?
First, I'd like to find out whether the .vmdk has a supported format.
If you are familiar with the ESXi host's command line, please run ls -lisa in the VM's folder, and post the results.
Btw. what type of virtual disk is it? SCSI, SATA, or IDE? Note that resizing IDE disks from the vSphere Client is not supported.
Many Thanks for getting back to me so quickly.
.vmdk file started life as an .img file - converted to .vmdk using StarWind V2V Image Converter and vmkfstools used to make sure its converted to an ESXi supported .vmdk.
381682116 128 drwxr-xr-x 1 root root 72.0K Apr 14 19:25 .
4 1024 drwxr-xr-t 1 root root 76.0K Apr 14 18:58 ..
62914564 976896 -rw------- 1 root root 953.7M Apr 14 19:23 router-flat.vmdk
67108868 0 -rw------- 1 root root 466 Apr 14 19:23 router.vmdk
50331652 0 -rw-r--r-- 1 root root 0 Apr 14 18:56 test-bsd.vmsd
37748740 0 -rwxr-xr-x 1 root root 2.0K Apr 14 19:25 test-bsd.vmx
It is a SCSI virtual Disk. Yes, I do know IDE disk resizing is not supported... Let me know if you need any further info...
Can you please attach the "router.vmdk" as well as the "test-bsd.vmx" to a reply post?
One of those files should contain hints on what's causing this issue.
The virtual hardware is set to a very old version in the vmdk-file.
ddb.virtualHWVersion = "4"
It may help if you delete that line / or update it to the really used version.
I changed the ddb.virtualHWVersion to 13 as that seems to be in line with the other VMs.
Unfortunately, the issue persists...
I'm unable to reproduce the issue with a newly created virtual disk, and your descriptor file. Resizing worked flawlessly for me.
StarWind V2V Image Converter and vmkfstools used to make sure its converted to an ESXi supported .vmdk.
Can you provide some more details please:
- what was the source, i.e. which virtualization product, which file format?
- which target format did you select for the StarWind V2V conversion?
- which vmkfstools command did you use to convert the virtual disk file?
- how do the flat file's first few bytes look like?
hexdump -n 16 -C router-flat.vmdk
* In Starwind V2V Converter - I picked Local file (location of .img file) and Location of destination image Remote VMware ESXi Server
* Converted using vmkfstools -i <.vmdk> <new.vmdk> (tried both -d thin and thick options)
* 00000000 fc 31 c0 8e c0 8e d8 8e d0 bc 00 7c 89 e6 bf 00 |.1.........|....|
The img you downloaded already is a perfect thick flat.vmdk.
Converting it is like the attempt to paint a green wall green ...
Maybe the partitions are the reasons for the failure ?
The vmdk has 4 partitions :
450 mb unknown
450 mb unknown
15 mb UFS
15 mb UFS
Which partition do you want to resize ?
Thanks - Was not even aware the .vmdk has partitions on it.
I have tried to extend the disk using vmfstools to 2G but, its still showing up 1G on the GUI... and not saving the change when I increase the disk to 2G.
At this point I might need to seek an alternative VM.. but, thanks all for your help thus far.