On 26 Jun 2018, at 16:54, Aziz <azizgstest@gmail.com> wrote:
--000000000000c1a2b4056f8cac08 Content-Type: multipart/alternative; boundary="000000000000c1a2b2056f8cac07"
--000000000000c1a2b2056f8cac07 Content-Type: text/plain; charset="UTF-8"
Yes sure :
Based on this message *"Empty element ResourceType under Item element, line 1. see DMTF Schema Documentation http://schemas.dmtf.org/wbem/cim-html/2/ <http://schemas.dmtf.org/wbem/cim-html/2/>"."*
It seems that something is missing when generating the OVA file from oVirt
OVA is a very “flexible” format. In general it’s not compatible between different hypervisors. There is typically some specific compatibility or tools helping with conversions, but a “foreign” OVA is almost never natively supported in other products Here the oVirt’s OVA is only consumable by oVirt. You could do the conversions manually - convert disk by qemu-img as suggested before, and constructing the VM configuration from scratch. Thanks, michal