`vsphere-iso`: Deploying exported OVF results in VM with empty disks

[ghost]

This issue was originally opened by @nilic as hashicorp/packer#9629. It was migrated here as a result of the Packer plugin split. The original body of the issue is below.

---

Initially a part of hashicorp/packer#8995, now opening a separate issue as requested.

The OVF exported by the vsphere-iso builder currently seems unusable.

After hashicorp/packer#9020 was released as a part of Packer 1.5.6 I tried the following:

• deploying the exported OVF to two vCenter servers using the vsphere post-processor

• converting the OVF to OVA manually using ovftool and uploading it to vCloud Director

All of these attempts have the same result - I get a VM which seemingly looks fine (in terms of virtual hardware, disk size etc) but has virtual disks which are zero in size:

and doesn't boot.

Message I get from ovftool when converting to OVA:

Wrong file size specified in OVF descriptor for 'centos7-XXX-disk-0.vmdk' (specified: 12884901888, actual 1344942592).
Wrong file size specified in OVF descriptor for 'centos7-XXX-disk-1.vmdk' (specified: 12884901888, actual 74752).

Virtual disk 0 is 10 GB and disk 1 is 2 GB in size if that's of any help.

Packer 1.5.6 ovftool 4.3.0 (build-13981069) vSphere 6.5

[tenthirtyam]

This was resolved in https://github.com/hashicorp/packer/issues/9629, but was migrated over as an open issue.