Kais Belgaied wrote: >> On 10/19/09 07:12, Sebastien Roy wrote: >>> Kais, >>> >>> Are you satisfied with Susan's answers to your questions? >>> > > almost there. > > >>> On 10/12/09 11:17, Susan Kamm-Worrell wrote: >> >> The open source virt-convert import does not yet support the TAR (ova) >> format. >> >> It does support an input of a directory that contains the OVF package >> files or an input of the ovf file directly. If specifying the ovf file >> directly the ovf file will describe the other files required by >> the OVF package. > > OK, > Could you give an example or list in the text of the draft man page what > the content of > such dir looks like? > Can you clarify if there are files ignored in the package content dir > while importing (I'm thinking about the cert files for integrity > checks).
Here's an example of an OVF directory containing an opensolaris guest: # ls osol-0906 osol-0906.ovf osol-0906.vmdk User would convert by doing: virt-convert -o virt-instance osol-0906 osol-0906-xvm.xml or virt-convert -o virt-instance osol-0906/osol-0906.ovf osol-0906-xvm.xml User would then create guest (just as in previous virt-convert) with: virsh define osol-0906-xvm.xml <path_to_xml_file> The current opensource virt-convert ignores the manifest, certificate and resource files. Future enhancements are planned for virt-convert to handle these files as well as a TAR input, but this version allows us to take an exported image from VirtualBox and convert to an xvm format since VirtualBox doesn't create a manifest, certificate or resource file. Susan > > Kais,. > >
