Sean, Like you mentioned, there is something in OVF that is of bound.
Perhaps logs will reveal more info? They way I usually address this, I take a good know working OVF, and inject my VMDK or just rename VMDK to match what you have. OVAs are create with tar command, so you can easily tar it up again (don't remember if gzip compression was used, I think it did). Regards ilya Also, does it fail on > -----Original Message----- > From: Sean Hamilton [mailto:s...@seanhamilton.co.uk] > Sent: Tuesday, November 05, 2013 7:45 AM > To: users@cloudstack.apache.org > Subject: VMware vCloud to CloudStack migration > > Hi Guys, > > I have a user that is trying to export an instance from vCloud so that they > can > import into CloudStack. They've exported the .ova file which contains: > - .ovf file > - .vmdk file > > When they upload the template they get a deployment fail, I think that this is > due to the metadata in the .ovf file. I've seen specific entries before on > VirtualBox to CloudStack migrations but can't figure this one out. > > Are there any recommendations or best practises on this at all? > > Thanks, > Sean
