VMware vSphere

 View Only

Importing .ova into vSphere does not bring over everything

  • 1.  Importing .ova into vSphere does not bring over everything

    Posted Nov 16, 2019 12:11 AM

    Hello.

    I've built a VM in VMware Workstation. I have successfully converted the .vmx to an .ova file (size ~ 5GB). I can manually import this .ova into VMware Workstation or my remote vSphere

    environment via GUI with success. After importing I'm able to power on the VM and use it.

    Whenever I try to use the ovftool to deploy the .ova remotely via CLI onto vSphere, the action completes successfully. I see the VM imported into inventory, but the transfer happens impossibly fast and looking at the contents of the vm on the datastore it shows the .vmdk only being around 700K (when it should be ~5GB).

    I get the same behavior with PowerCLI and the Import-VApp cmdlet. I can import the .ova into inventory but the entire contents of the ~5GB do not transfer over - just a few bits.

    I've looked over the ovftool documentation and I don't see anything I'm missing.

    What am I doing wrong? Have any of you run into this problem before?