vmdk ESXi compatible without vmkfstools expanding my image to 300GB? The vmkfstools command gives me two files, an metadata.vmdk and the actual data.vmdk.Īs mentioned above my disk is thin provisioned for 300GB and when I apply vmkfstools it expands the disk and gives me a size of 300GB.ĭeploying the image through the vSphere Client works without any problem however, for the purpose of this project I want to use the ovftool and doing so with such a large image is not feasible. vmkfstools -i myImage.vmdk outputName.vmdk -d thin Therefore, in order to make it ESXi compatible I have to use the vmkfstools with the following command. This command gives me a vmdk image which is only VMWare Workstation compatible. I used the image converter tool qemu with the following command qemu-img convert -f qcow2 myImage.qcow2 -O vmdk myNewImage.vmdk
I have myImage.qcow2 with a disk which is thin provisioned for 300GB. I am currently working on VMWare virtualization I am trying to make a converted image from qcow2 to vmdk work with ESXi Server 6.0.
0 kommentar(er)
