From Sebastien.Roy@Sun.COM Fri Oct 9 12:59:34 2009 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02.SFBay.Sun.COM [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n99JxYQg002784 for ; Fri, 9 Oct 2009 12:59:34 -0700 (PDT) Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n99JxYor051929 for ; Fri, 9 Oct 2009 12:59:34 -0700 (PDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n99JxY0H019280 for ; Fri, 9 Oct 2009 19:59:34 GMT MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KR900600J39A900@mail-amer.sun.com> for psarc-ext@sac.sfbay.sun.com; Fri, 09 Oct 2009 13:59:34 -0600 (MDT) Received: from [129.148.174.103] ([unknown] [129.148.174.103]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KR900E7TJJ7XV80@mail-amer.sun.com> for psarc-ext@sac.sfbay.sun.com; Fri, 09 Oct 2009 13:59:31 -0600 (MDT) Date: Fri, 09 Oct 2009 15:57:09 -0400 From: Sebastien Roy Subject: OVF Support in virt-convert [PSARC/2009/548 FastTrack timeout 10/16/2009] Sender: Sebastien.Roy@Sun.COM To: psarc-ext Cc: Susan Kamm-Worrell Message-id: <1255118229.10215.144.camel@strat> Organization: Sun Microsystems Status: RO Content-Length: 1384 I'm submitting this fast-track for Susan Kamm-Worrell, it times out on 10/16/2009. The release binding is Patch. The proposed man page changes are contained in the case's materials directory. 1. Introduction This case introduces another input format to the xvm command-line utility, virt-convert(1). A patch binding is requested. 2. Discussion The Open Virtualization Format (OVF) is the latest industry wide format used to move guest VMs between different v12n platforms. In following the upstream virt-install project, virt-convert has been enhanced to auto-detect the OVF format as an input type or to have it explicitly set on use as follows: usage: virt-convert -i ovf inputdir|input.vmx|input.ovf [outputdir|output.xml] The manpage has also been updated to reflect the support of the OVF format. (see the man page in the materials directory). 3. Input/output formats virt-convert now supports both .vmx and OVF format input files. 4. Interface table An additional input format is listed in the interface table describing the still changing OVF specification. virt-convert command line Uncommitted virt-convert output Not-an-interface virt-instance output format Uncommitted VMX input format Volatile OVF input format Volatile 5. References PSARC/2008/579 virt-convert From Mark.Carlson@Sun.COM Fri Oct 9 14:45:48 2009 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02.SFBay.Sun.COM [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n99LjmFD004710 for ; Fri, 9 Oct 2009 14:45:48 -0700 (PDT) Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n99LjlXB047899 for ; Fri, 9 Oct 2009 14:45:47 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n99LjlkG002939 for ; Fri, 9 Oct 2009 21:45:47 GMT MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_h/J4ZGbtCpQIx6cmQSRYBQ)" Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KR900A00NIGEN00@mail-amer.sun.com> for psarc-ext@sac.sfbay.sun.com; Fri, 09 Oct 2009 15:45:47 -0600 (MDT) Received: from Macintosh-335.local ([unknown] [209.116.49.251]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KR9006R1OFRMG70@mail-amer.sun.com> for psarc-ext@sac.sfbay.sun.com; Fri, 09 Oct 2009 15:45:28 -0600 (MDT) Date: Fri, 09 Oct 2009 15:45:23 -0600 From: "Mark A. Carlson" Subject: Re: OVF Support in virt-convert [PSARC/2009/548 FastTrack timeout 10/16/2009] In-reply-to: <1255118229.10215.144.camel@strat> Sender: Mark.Carlson@Sun.COM To: Sebastien Roy Cc: psarc-ext , Susan Kamm-Worrell Message-id: <4ACFAEF3.3050805@sun.com> References: <1255118229.10215.144.camel@strat> User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) Status: RO Content-Length: 5026 This is a multi-part message in MIME format. --Boundary_(ID_h/J4ZGbtCpQIx6cmQSRYBQ) Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT +1 -- mark Sebastien Roy wrote: > I'm submitting this fast-track for Susan Kamm-Worrell, it times out on > 10/16/2009. The release binding is Patch. The proposed man page > changes are contained in the case's materials directory. > > 1. Introduction > > This case introduces another input format to the xvm command-line utility, > virt-convert(1). > > A patch binding is requested. > > 2. Discussion > > The Open Virtualization Format (OVF) is the latest industry wide > format used to move guest VMs between different v12n platforms. > > In following the upstream virt-install project, virt-convert > has been enhanced to auto-detect the OVF format as an input type > or to have it explicitly set on use as follows: > > usage: virt-convert -i ovf inputdir|input.vmx|input.ovf [outputdir|output.xml] > > The manpage has also been updated to reflect the support of the OVF format. > (see the man page in the materials directory). > > 3. Input/output formats > > virt-convert now supports both .vmx and OVF format input files. > > 4. Interface table > > An additional input format is listed in the interface table describing > the still changing OVF specification. > > virt-convert command line Uncommitted > virt-convert output Not-an-interface > virt-instance output format Uncommitted > VMX input format Volatile > OVF input format Volatile > > 5. References > > PSARC/2008/579 virt-convert > > > _______________________________________________ > opensolaris-arc mailing list > opensolaris-arc@opensolaris.org > -- * Mark A. Carlson * Sr. Architect *Systems Group* Phone x69559 / 303-223-6139 Email Mark.Carlson@Sun.COM --Boundary_(ID_h/J4ZGbtCpQIx6cmQSRYBQ) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: 7BIT +1

-- mark

Sebastien Roy wrote: 
I'm submitting this fast-track for Susan Kamm-Worrell, it times out on
10/16/2009.  The release binding is Patch.  The proposed man page
changes are contained in the case's materials directory.

1.  Introduction

This case introduces another input format to the xvm command-line utility,
virt-convert(1).

A patch binding is requested.

2.  Discussion

The Open Virtualization Format (OVF) is the latest industry wide 
format used to move guest VMs between different v12n platforms.

In following the upstream virt-install project, virt-convert  
has been enhanced to auto-detect the OVF format as an input type 
or to have it explicitly set on use as follows:

usage: virt-convert -i ovf inputdir|input.vmx|input.ovf [outputdir|output.xml]

The manpage has also been updated to reflect the support of the OVF format.
(see the man page in the materials directory).

3.  Input/output formats

virt-convert now supports both .vmx and OVF format input files.

4.  Interface table

An additional input format is listed in the interface table describing
the still changing OVF specification.

   virt-convert command line          Uncommitted
   virt-convert output                Not-an-interface
   virt-instance output format        Uncommitted
   VMX input format                   Volatile
   OVF input format                   Volatile

5.  References

PSARC/2008/579 virt-convert


_______________________________________________
opensolaris-arc mailing list
opensolaris-arc@opensolaris.org

--
Mark A. Carlson
Sr. Architect

Systems Group
Phone x69559 / 303-223-6139
Email Mark.Carlson@Sun.COM

--Boundary_(ID_h/J4ZGbtCpQIx6cmQSRYBQ)-- From Kais.Belgaied@Sun.COM Sun Oct 11 12:00:55 2009 Received: from jurassic-x4600.sfbay.sun.com (cretaceous.SFBay.Sun.COM [129.146.17.63]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n9BJ0t36023839 for ; Sun, 11 Oct 2009 12:00:55 -0700 (PDT) Received: from [129.146.11.144] (sr1-jurassic-01.SFBay.Sun.COM [129.146.11.144]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n9BJ0rgv509472 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 11 Oct 2009 12:00:55 -0700 (PDT) Message-ID: <4AD22B65.9080804@Sun.COM> Date: Sun, 11 Oct 2009 12:00:53 -0700 From: Kais Belgaied User-Agent: Thunderbird 2.0.0.21 (X11/20090311) MIME-Version: 1.0 To: Sebastien Roy CC: psarc-ext , Susan Kamm-Worrell Subject: Re: OVF Support in virt-convert [PSARC/2009/548 FastTrack timeout 10/16/2009] References: <1255118229.10215.144.camel@strat> In-Reply-To: <1255118229.10215.144.camel@strat> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Status: RO Content-Length: 2044 - Scope of this case: Typically, you don't get a naked .ovf file. You get an OVF package, which is a tar ball of the content (actual vmdk's of a disk image + possible .iso if needed for startup, optional signing cert ...) along with the .ovf that describes the metatdata for configuring the VM. The package is what VWare's OVF tool exports and imports. It seems to me that stopping at importing and producing only the .ovf falls short of delivering a complete answer and leaves the user on his/her own to go assemble the needed parts. - Interoperability: OVF defines 3 levels of conformance, depending on the attributes and optional extensions implemented. What is the conformance level of OVF files produced/exported by virt-convert? On the import side, what level is understood by this implementation? - Evolution Any tying to a particular version of the format? Kais. On 10/09/09 12:57, Sebastien Roy wrote: > The Open Virtualization Format (OVF) is the latest industry wide > format used to move guest VMs between different v12n platforms. > > In following the upstream virt-install project, virt-convert > has been enhanced to auto-detect the OVF format as an input type > or to have it explicitly set on use as follows: > > usage: virt-convert -i ovf inputdir|input.vmx|input.ovf [outputdir|output.xml] > > The manpage has also been updated to reflect the support of the OVF format. > (see the man page in the materials directory). > > 3. Input/output formats > > virt-convert now supports both .vmx and OVF format input files. > > 4. Interface table > > An additional input format is listed in the interface table describing > the still changing OVF specification. > > virt-convert command line Uncommitted > virt-convert output Not-an-interface > virt-instance output format Uncommitted > VMX input format Volatile > OVF input format Volatile > > 5. References > > PSARC/2008/579 virt-convert > > > > From Susan.Kamm-Worrell@Sun.COM Mon Oct 12 11:17:27 2009 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02.SFBay.Sun.COM [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n9CIHRud025216 for ; Mon, 12 Oct 2009 11:17:27 -0700 (PDT) Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n9CIHRT4032747 for ; Mon, 12 Oct 2009 11:17:27 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n9CIHQZk019214 for ; Mon, 12 Oct 2009 18:17:26 GMT MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KRE00J00X9Z1J00@mail-amer.sun.com> for psarc-ext@sac.sfbay.sun.com; Mon, 12 Oct 2009 12:17:26 -0600 (MDT) Received: from [141.138.4.104] ([unknown] [76.76.64.29]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KRE00C50YT23N80@mail-amer.sun.com>; Mon, 12 Oct 2009 12:17:26 -0600 (MDT) Date: Mon, 12 Oct 2009 12:17:26 -0600 From: Susan Kamm-Worrell Subject: Re: OVF Support in virt-convert [PSARC/2009/548 FastTrack timeout 10/16/2009] In-reply-to: <4AD22B65.9080804@Sun.COM> Sender: Susan.Kamm-Worrell@Sun.COM To: Kais Belgaied Cc: Sebastien Roy , psarc-ext Message-id: <4AD372B6.1060009@sun.com> References: <1255118229.10215.144.camel@strat> <4AD22B65.9080804@Sun.COM> User-Agent: Thunderbird 2.0.0.21 (X11/20090323) Status: RO Content-Length: 2916 Kais Belgaied wrote: > - Scope of this case: > Typically, you don't get a naked .ovf file. You get an OVF package, > which is a tar ball of the content (actual vmdk's of a disk image + > possible .iso if needed for startup, optional signing cert ...) > along with the .ovf that describes the metatdata for configuring > the VM. The package is what VWare's OVF tool exports and imports. It > seems to me that stopping at importing and producing only the .ovf > falls short of delivering a complete answer and leaves the user on > his/her own to go assemble the needed parts. 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. > > - Interoperability: > OVF defines 3 levels of conformance, depending on the attributes and > optional extensions implemented. > What is the conformance level of OVF files produced/exported by > virt-convert? > On the import side, what level is understood by this implementation? virt-convert does not yet support export of an OVF package. virt-convert understands the basic ovf core metadata sections in use by the industry at this time. It currently complies with import of Conformance Level 1 ovf packages. > > - Evolution > Any tying to a particular version of the format? No. If the parser can parse the ovf xml file without failure then the import will be attempted. If an unknown required section is encountered during the parsing of the ovf xml file, then virt-convert will fail. Thanks, Susan > > Kais. > > On 10/09/09 12:57, Sebastien Roy wrote: >> The Open Virtualization Format (OVF) is the latest industry wide >> format used to move guest VMs between different v12n platforms. >> >> In following the upstream virt-install project, virt-convert has been >> enhanced to auto-detect the OVF format as an input type or to have it >> explicitly set on use as follows: >> >> usage: virt-convert -i ovf inputdir|input.vmx|input.ovf >> [outputdir|output.xml] >> >> The manpage has also been updated to reflect the support of the OVF >> format. >> (see the man page in the materials directory). >> >> 3. Input/output formats >> >> virt-convert now supports both .vmx and OVF format input files. >> >> 4. Interface table >> >> An additional input format is listed in the interface table describing >> the still changing OVF specification. >> >> virt-convert command line Uncommitted >> virt-convert output Not-an-interface >> virt-instance output format Uncommitted >> VMX input format Volatile >> OVF input format Volatile >> >> 5. References >> >> PSARC/2008/579 virt-convert >> >> >> >> > From Sebastien.Roy@Sun.COM Mon Oct 19 07:15:05 2009 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01.SFBay.Sun.COM [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n9JEF5Z0002824 for ; Mon, 19 Oct 2009 07:15:05 -0700 (PDT) Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n9JEF5hI009167 for ; Mon, 19 Oct 2009 07:15:05 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n9JEF48B007319 for ; Mon, 19 Oct 2009 14:15:04 GMT MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KRR00500L2AZS00@mail-amer.sun.com> for psarc-ext@sac.sfbay.sun.com; Mon, 19 Oct 2009 08:15:04 -0600 (MDT) Received: from [129.148.174.103] ([unknown] [129.148.174.103]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KRR00HFGM8XPTE0@mail-amer.sun.com>; Mon, 19 Oct 2009 08:14:58 -0600 (MDT) Date: Mon, 19 Oct 2009 10:12:31 -0400 From: Sebastien Roy Subject: Re: OVF Support in virt-convert [PSARC/2009/548 FastTrack timeout 10/16/2009] In-reply-to: <4AD372B6.1060009@sun.com> Sender: Sebastien.Roy@Sun.COM To: Susan Kamm-Worrell Cc: Kais Belgaied , psarc-ext Message-id: <1255961551.10280.6.camel@strat> Organization: Sun Microsystems References: <1255118229.10215.144.camel@strat> <4AD22B65.9080804@Sun.COM> <4AD372B6.1060009@sun.com> Status: RO Content-Length: 73 Kais, Are you satisfied with Susan's answers to your questions? -Seb From Kais.Belgaied@Sun.COM Tue Oct 20 10:38:47 2009 Received: from jurassic-x4600.sfbay.sun.com (cretaceous.SFBay.Sun.COM [129.146.17.63]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n9KHclHQ021860 for ; Tue, 20 Oct 2009 10:38:47 -0700 (PDT) Received: from [129.146.11.144] (sr1-jurassic-01.SFBay.Sun.COM [129.146.11.144]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n9KHclcP500724 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Oct 2009 10:38:47 -0700 (PDT) Message-ID: <4ADDF5A7.7000408@Sun.COM> Date: Tue, 20 Oct 2009 10:38:47 -0700 From: Kais Belgaied User-Agent: Thunderbird 2.0.0.21 (X11/20090311) MIME-Version: 1.0 To: Susan Kamm-Worrell CC: Sebastien Roy , psarc-ext Subject: Re: OVF Support in virt-convert [PSARC/2009/548 FastTrack timeout 10/16/2009] References: <1255118229.10215.144.camel@strat> <4AD22B65.9080804@Sun.COM> <4AD372B6.1060009@sun.com> In-Reply-To: <4AD372B6.1060009@sun.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Status: RO Content-Length: 782 > 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). Kais,. From Susan.Kamm-Worrell@Sun.COM Tue Oct 20 12:29:38 2009 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02.SFBay.Sun.COM [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n9KJTcLJ024917 for ; Tue, 20 Oct 2009 12:29:38 -0700 (PDT) Received: from brmea-mail-1.sun.com (brmea-mail-1.Sun.COM [192.18.98.31]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id n9KJTbsW019808 for ; Tue, 20 Oct 2009 12:29:37 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n9KJTbgJ013088 for ; Tue, 20 Oct 2009 19:29:37 GMT MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KRT00400UT3CU00@mail-amer.sun.com> for psarc-ext@sac.sfbay.sun.com; Tue, 20 Oct 2009 13:29:37 -0600 (MDT) Received: from [141.138.4.103] ([unknown] [76.76.64.29]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KRT00KXJVH8Z710@mail-amer.sun.com>; Tue, 20 Oct 2009 13:29:32 -0600 (MDT) Date: Tue, 20 Oct 2009 13:29:32 -0600 From: Susan Kamm-Worrell Subject: Re: OVF Support in virt-convert [PSARC/2009/548 FastTrack timeout 10/16/2009] In-reply-to: <4ADDF5A7.7000408@Sun.COM> Sender: Susan.Kamm-Worrell@Sun.COM To: Kais Belgaied Cc: Sebastien Roy , psarc-ext Message-id: <4ADE0F9C.6040905@sun.com> References: <1255118229.10215.144.camel@strat> <4AD22B65.9080804@Sun.COM> <4AD372B6.1060009@sun.com> <4ADDF5A7.7000408@Sun.COM> User-Agent: Thunderbird 2.0.0.21 (X11/20090323) Status: RO Content-Length: 1620 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 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,. > > From Sebastien.Roy@Sun.COM Wed Oct 21 14:07:13 2009 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01.SFBay.Sun.COM [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n9LL7DKe011618 for ; Wed, 21 Oct 2009 14:07:13 -0700 (PDT) Received: from brmea-mail-1.sun.com (brmea-mail-1.Sun.COM [192.18.98.31]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id n9LL7CMF018371 for ; Wed, 21 Oct 2009 14:07:12 -0700 (PDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n9LL7CqA024894 for ; Wed, 21 Oct 2009 21:07:12 GMT MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KRV00G00U6VIL00@mail-amer.sun.com> for psarc-ext@sac.sfbay.sun.com; Wed, 21 Oct 2009 15:07:12 -0600 (MDT) Received: from [129.148.174.103] ([unknown] [129.148.174.103]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KRV00K5UUNPJQA0@mail-amer.sun.com> for psarc-ext@sac.sfbay.sun.com; Wed, 21 Oct 2009 15:07:02 -0600 (MDT) Date: Wed, 21 Oct 2009 17:04:34 -0400 From: Sebastien Roy Subject: Re: OVF Support in virt-convert [PSARC/2009/548 FastTrack timeout 10/16/2009] In-reply-to: <1255118229.10215.144.camel@strat> Sender: Sebastien.Roy@Sun.COM To: psarc-ext Cc: Susan Kamm-Worrell Message-id: <1256159074.13241.336.camel@strat> Organization: Sun Microsystems References: <1255118229.10215.144.camel@strat> Status: RO Content-Length: 318 On Fri, 2009-10-09 at 15:57 -0400, Sebastien Roy wrote: > I'm submitting this fast-track for Susan Kamm-Worrell, it times out on > 10/16/2009. The release binding is Patch. The proposed man page > changes are contained in the case's materials directory. This case was approved during today's PSARC meeting. -Seb