The problem is the underlying format used to store virtual machines on VMware Hosted products differs from the format used to store virtual machines on ESX/ESXi hosts.
See this: https://kb.vmware.com/s/article/1028943
Solution:
[root@ESXi01:/vmfs/volumes/5f1c7304-77d00f04-ad0f-1c697a6ba3e5/cloudera-quickstart-vm-5.13.0-0-vmware] mkdir new
[root@ESXi01:/vmfs/volumes/5f1c7304-77d00f04-ad0f-1c697a6ba3e5/cloudera-quickstart-vm-5.13.0-0-vmware] vmkfstools -i cloudera-quickstart-vm-5.13.0-0-vmware.vmdk new/cloud
era-quickstart-vm-5.13.0-0-vmware.vmdk
Destination disk format: VMFS zeroedthick
Cloning disk 'cloudera-quickstart-vm-5.13.0-0-vmware.vmdk'...
Clone: 100% done.
Detach the currently attached VMDK from the virtual machine:
In the vSphere Client or vSphere Web Client, right-click the virtual machine and click Edit Settings.
Select the hard disk.
Click Remove.
Select the Remove from virtual machine option.
Click OK.
move *.vmdk to a subdir old
move the vmdk file from new to the vm dir
Reattach the newly formatted VMDK from Step 2:
In the vSphere Client or vSphere Web Client, right-click the virtual machine and click Edit Settings.
Click Add.
Select the hard disk.
Click Next.
Select the Use an existing virtual disk option.
Click Next.
Click Browse and locate the new VMDK created in Step 2.
Click Next.
Click Next.
Click Finish to close the Add Hardware window.
Click OK to close the Virtual Machine properties window.
Power on the virtual machine.
once ok can delete the subdir old and dir new (should be empty now)
No comments:
Post a Comment