The parser code is here https://github.com/virt-manager/virt-manager/blob/561f5cd3e68fa3f1fb6745463a5c1a486171d8c9/virtconv/ovf.py
----- Mail original ----- De: "aderumier" <aderum...@odiso.com> À: "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Jeudi 19 Janvier 2017 07:53:35 Objet: Re: [pve-devel] Question: open virtual appliance >>Does somebody known where are the specifications of config format ? does it >>have revisions ? seem than virt-manager have a virt-convert tool which is able to read ovf https://github.com/virt-manager/virt-manager/blob/master/virt-convert they are a lot of ovf sample configs in the repository. ----- Mail original ----- De: "aderumier" <aderum...@odiso.com> À: "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Jeudi 19 Janvier 2017 07:46:39 Objet: Re: [pve-devel] Question: open virtual appliance Hi, as a first step, I have send patch to import external disk image. now for ova import, I think we need a method to extract files from ova (it's a simple tar file), then an xml parser to parse OVF descriptor Does somebody known where are the specifications of config format ? does it have revisions ? ----- Mail original ----- De: "Andreas Steinel" <a.stei...@gmail.com> À: "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Mercredi 18 Janvier 2017 18:54:39 Objet: Re: [pve-devel] Question: open virtual appliance Only some experience: I was not able easily interchange simple OVA generated from VMware with OVA generated from VirtualBox without manual intervention. If you build something that works, that should be fine. I also tried to import OVA exported from VMware into Xen and it also did not work, not even with their support. Always some strange error. Whereas I never had problems importing into Proxmox VE. On Wed, Jan 18, 2017 at 12:25 PM, Emmanuel Kasper <e.kas...@proxmox.com> wrote: > On 01/16/2017 10:14 PM, Gustaf Ankarloo wrote: > > Are there any plans of making a import function for OVA/OVF ? > > I know it's doable with a lot of manual tinkering > > I have this somewhere in my todo list although it is not high priority > at the momment. > > I would like to try to following approach: > * extract the OVA archive (itsel a tar) to get the OVF xml manifest and > the disk image > * from the OVF xml file generate a minimal vm.conf > * create a vma archive with the disk image and associated vm.conf using > the vma command > * now you have a valid vzdump ready to be extracted to the storage of > your choice with the tools you know already > > stuff to be left out for first approach: > > * ova with multiple disk images (don't know if the vma command line > utils support that) > > * extraneous paramaters of OVF file. The OVF spec is 40 pages long and > allows vendor specific options via private xml namespaces. So we're not > going to cover all of it. > > Any comments on this approach ? > > _______________________________________________ > pve-devel mailing list > pve-devel@pve.proxmox.com > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel > _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel