Hi,
On Jun 28, 2018, at 8:25 AM, Michal Skrivanek
<michal.skrivanek(a)redhat.com> wrote:
> On 26 Jun 2018, at 16:54, Aziz <azizgstest(a)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.
but OVA is a clear open format where more companies in the past agreed to work on.
So, the compliancy on the format is pretty clear and the target, at the end, is to move
to/from one hypervisor to an other by using this “standard” format (where each hypervisor
has its own - vmdk for VMware / vdi for VBox and so on).
Different thing is the possible issue while trying to boot the VM on the target
hypervisor, issue usually due to the missing storage/network drivers while booting
(initrd/initramfs and/or win-kernel).
I’m used to get everything easily created on VirtualBox (with Vagrant) and then get the
same VM available on the “server” hypervisor by OVA export/import.
At the same time, as a developer, I want to play with a VM on my own laptop (by using
VBox, VMware), a VM that is a clone of what is running on oVirt/KVM production; and here
why the OVA compliancy should be respected.
Simon
Thanks,
michal
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/X2BQPMU3SLJ...