This post explains about the step by step procedure to expand the virtual machine VMDK size using vmkfstools.Prior ESX 3.5, There is no option to extend the virtual hard disk size from vSphere client. Yunie modeli foto vk download. Virtual harddsik expansion can be done only via CLI with the help of vmkfstools. Command and also you need to power down the virtual machine before proceeding with the below steps prior ESX 3.5.

Hi, I am migrating a virtual machine from VMware Server 1.X to ESXi 4.0. I have copied the server across using fastscp and the instructions here: However while trying to convert the machine using vmkfstools, I am not having any success. Here is the directory: /vmfs/volumes/4c35cad3-7e6 b098e-b172 -001372123 403/temp # ls Test-Client-flat.vmdk Test-Client.vmdk Here is the command that I am running followed by the error that I get: /vmfs/volumes/4c35cad3-7e6 b098e-b172 -001372123 403/temp # vmkfstools -i Test-Client.vmdk Test-Client-New.vmdk DiskLib_Check() failed for source disk The system cannot find the file specified (25). I've tried a couple of resources online but none have been helpful in explaining the syntax for vmkfstools.

I have also viewed the man page and used the /? If anyone could tell me what comman I need to run to convert this disk I would really appreciate it.

I'm facing a strange issue with my virtual machine. I have an rhel 6.1 guest os running on VMware workstation (9.0.2 build-1031769) hosted on Windows 7 Enterprise 64 bit. The size of the vmdk file is around 65 GB whereas the total size of the guest os is only 11GB. What am I missing here? [root@praveenVM praveen]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda3 95G 11G 79G 12% / tempfs 499M 340K 499M 1% /dev/shm /dev/sda1 124M 61M 58M 52% /boot There was some temporary files in /var (Unnecessary logs), which I have deleted now and hence the used space is around 11GB.

But why is that the vmdk file is around 65GB? Having deleted all the unnecessary files in the Guest OS, the size of the vmdk should automatically decrease right? It appears that VMware isn't able to do much to compact ext4-formatted drives. The solution is that you need to fill the drive with zeroes and then delete a file that you used to do that. So: sudo su cat /dev/zero > wipefile; rm -f wipefile shutdown -h now Basically, you become root, you create a file filled with zeroes and then you delete it and shutdown the machine. I ran the above code a moment ago, and watched a few things as I did: • I suspected the vmdk file would grow to the size of the disk, but it didn't. It grew slightly, but not much.

This was good because my host does not have space for the full vmdk file. • I suspected drive on the guest would fill up.

I watched it with: while: do du -h sleep 2 done The guest disk started at about 15% full, then climbed to 100%, at which point the cat command failed and the wipefile was rm'ed, bringing it back to 15% full. I've seen a few posts that also say you should do this for /boot. Probably a good idea, but I don't think it's always necessary. Once that's complete, go into the machine's settings > Hard Disk > Utilities > Compact., and you should be all good.