![]() Workaround: Export the virtual machine as an OVF template, and then create an OVA template from the OVF template files. If want OVA,then you use OVFTool and you’ll get the same behavior as 6.5 (which had the export run locally) as mentioned in the vCenter 6.5 release notes: For small VMs, this may not be a problem but there are many customers who have extremely large VMs (several hundred GBs) and this could have a huge impact on VC. ![]() The issue with supporting OVA as I understand it was that it would require additional space on vCenter Server to actually store the contents where as today, it is directly streamed to the customer for download. In 6.5, CIP was removed and rather than relying on a client side tool to perform the export, this was now done natively within vCenter Server using the Content Library service which runs server side. This happened due to the removal of the Client Integration Plugin (CIP) which included a copy of OVFTool which ran locally on your desktop and was used to perform the export. ![]() As per the vSphere 6.5 documentation cannot export OVA templates. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |