VMWare OVF deployment support

2,242 views
Skip to first unread message

Rodrigo Oshiro

unread,
May 8, 2015, 7:28:05 AM5/8/15
to kiwi-...@googlegroups.com
Hi all,

I am having issues to deploy an OVF/VMDK image to our VMWare vSphere infrastucture at our EMC data centers. The following section in config.xml highlights what we need: a vmx image type in ovf format used by vmware.


<type image="vmx" filesystem="ext3" boot="vmxboot/suse-SLES12" primary="true" format="ovf" bootloader="grub2" firmware="efi" kernelcmdline="splash">
    <systemdisk name="systemVG">
        <volume name="swap" size="6144"/>
    </systemdisk>
       <machine memory="4096" guestOS="sles12-64" HWversion="7" arch="x86_64" ovftype="vmware">
        <vmdisk controller="lsilogic" id="0"/>
        <vmdvd  controller="ide" id="0"/>
        <vmnic driver="vmxnet3" interface="0" mode="bridged"/>
    </machine>
    <size unit="G">50</size>
</type>

The image builds fine, I can also convert an equivalent build of vmx format to OVF/VMDK using ovftools and deploy it to vSphere, so the image contents are valid.
So the issues I am having I believe lies in two areas, the OVF file itself (XML contents) and the VMDK image created.

1) When I deploy the OVF to vCenter I got the following errors:
Line 20: Missing child element 'Info'
Line 21: Unsupported element 'osType'
Line 22: Unsupported element 'Info'
Line 42: Unsupported element 'Weight'
Line 95: Unsupported element 'Automatic-Allocation'
Line 95: Unsupported element 'Connection'

VMWare vCenter Server Version 6.0.0, Build 2559267
kiwi version: 7.02.42-953.1
Build host OS: SLES12
Build target OS: SLES12

2) I manually fixed the errors in the OVF file, but then I got the following error in vCenter after the image was deployed:
Failed to deploy: Error uploading file DevKitSLIM.x86_64-12.0.0.1.101.vmdk to server. Not a supported disk format (sparse VMDK version too old)

So to compare the OVF created by ovftools, there are differences in the order of the xml elements that require to be in a certain order.

Also the VMDK image created by ovftools are compressed, while the one KIWI outputs is not. This is the last section of the log:
May-07 14:05:21 <1> : EXEC [parted /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.101/OVF/vmx-appliance/DevKitSLIM.x86_64-12.0.0.1.101.raw print 2>&1]
May-07 14:05:22 <1> : Starting raw => ovf conversion
May-07 14:05:22 <1> : Creating vmdk image...
May-07 14:05:22 <1> : EXEC [/usr/bin/qemu-img convert -f raw /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.101/OVF/vmx-appliance/DevKitSLIM.x86_64-12.0.0.1.101.raw -O vmdk -o adapter_type=lsilogic /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.101/OVF/vmx-appliance/DevKitSLIM.x86_64-12.0.0.1.101.vmdk 2>&1]
May-07 14:07:27 <1> : EXEC [mkdir -p /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.101/OVF/vmx-appliance/DevKitSLIM.x86_64-12.0.0.1.101.ovf]
May-07 14:07:27 <1> : EXEC [ln -s ../DevKitSLIM.x86_64-12.0.0.1.101.vmdk /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.101/OVF/vmx-appliance/DevKitSLIM.x86_64-12.0.0.1.101.ovf/DevKitSLIM.x86_64-12.0.0.1.101.vmdk]
May-07 14:07:27 <1> : Creating vmdk image machine configuration
May-07 14:07:27 <1> : Creating image VMware configuration file...
May-07 14:07:27 <1> : Creating vmx image machine configuration
May-07 14:07:27 <1> : Creating image OVF configuration file
May-07 14:07:27 <1> : EXEC [/usr/bin/uname -m]
May-07 14:07:27 <1> : EXEC [/usr/bin/uname -m]
May-07 14:07:27 <1> : Write OVF configuration file
May-07 14:07:27 <1> : --> /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.101/OVF/vmx-appliance/DevKitSLIM.x86_64-12.0.0.1.101.ovf/DevKitSLIM.x86_64-12.0.0.1.101.ovf
May-07 14:07:56 <1> :
Unknown guest OS setting 'sles12-64' using generic Linux setup
May-07 14:07:56 <2> : --> No nominal CPU count set, using 1
May-07 14:07:56 <2> : --> No disk disktype set, using "scsi"
May-07 14:07:56 <1> : EXEC [sync]
May-07 14:07:57 <1> : EXEC [sync]
May-07 14:07:57 <1> : EXEC [rm -rf /tmp/kiwiboot.q4o8jv 2>&1]
May-07 14:07:57 <1> : EXEC [rm -rf /tmp/kiwiloop.slBw27 2>&1]
May-07 14:07:57 <1> : EXEC [rm -rf /tmp/kiwiboot.8Euq7O 2>&1]
May-07 14:07:57 <1> : EXEC [sync]
May-07 14:07:57 <1> : EXEC [sync]
May-07 14:07:57 <1> : EXEC [/usr/bin/uname -m]
May-07 14:07:57 <1> : EXEC [mv -f /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.101/OVF/vmx-appliance/* /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.101/OVF 2>&1]
May-07 14:07:57 <1> : Find build results at: /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.101/OVF
May-07 14:07:57 <1> : Closing session with ecode: 0
May-07 14:07:58 <1> : KIWI exited successfully
May-07 14:07:58 <1> : EXEC [mv /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.101/OVF/build/image-root.2005.screenrc.log /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.101/OVF/build/image-root.log 2>&1]
May-07 14:07:58 <1> : Complete logfile at: /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.101/OVF/build/image-root.log
May-07 14:07:58 <1> : Release package manager lock
May-07 14:07:58 <1> : EXEC [rm -f /var/lock/kiwi-init.lock]
May-07 14:07:58 <1> : Release package manager lock
May-07 14:07:58 <1> : EXEC [rm -f /var/lock/kiwi-init.lock]
May-07 14:07:58 <1> : EXEC [rm -rf /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.101/OVF/vmx-appliance/boot-VMX.RNVqZh 2>&1]
May-07 14:07:58 <1> : EXEC [rm -f /var/cache/kiwi/zypper/zypper.conf.2005 /var/cache/kiwi/zypper/zypp.conf.2005]

So any ideas of what should be our next steps?

Thanks,

Marcus Schäfer

unread,
May 8, 2015, 8:32:25 AM5/8/15
to kiwi-...@googlegroups.com
Hi,

> I am having issues to deploy an OVF/VMDK image to our VMWare vSphere
> infrastucture at our EMC data centers.

Thanks for reporting this. I recently received similar reports

> So the issues I am having I believe lies in two areas, the OVF file
> itself (XML contents) and the VMDK image created.

Your observations are correct. With regards to kiwi's ovf config generator
I must admit we are not up to date for what vSphere requires. As you can
see qemu's vmdk generator isn't too

I'm also not convinced that it is a good idea to keep the code generating
the ovf metadata for VMware products in kiwi. In order to provide a good
quality we would have to assign a dedicated resource for kiwi vCenter
builds which we don't have

Because of that I have the 'ova' format in kiwi. Instead of saying
format="ovf" you could also set

format="ova"

If your host system has the ovftool installed kiwi will use it to create
a compatible version of the .ovf machine data file and a .vmdk disk image
file. kiwi will replace its own results by the result of ovftool.

In order to operate ovftool needs a basic version of a .ovf machine data
file as input. The one kiwi produces here was suitable at least with the
version of ovftool I have tested in the past. It might be the case that
this is not the case for newer versions but that's something we can fix
together

The beauty of using ovftool is that it knows about the disk modes vSphere
supports. Thus you can specify in your kiwi <vmdisk> section the required
disk mode. For vSphere I would use:

<vmdisk ... diskmode="streamOptimized"/>

The vmdk produced by ovftool will then work for you

All this is a little nasty but given the limited resources I had to plan
with I couldn't come up with a better solution at the moment.

Let me know if using ova as alternative format is an option for you
and if ovftool does not accept the input config file kiwi creates
let's fix this one

All what counts are happy customers :)

Any feedback is very much appreciated

Regards,
Marcus
--
Public Key available via: https://keybase.io
keybase search marcus_schaefer
-------------------------------------------------------
Marcus Schäfer (Res. & Dev.) SUSE Linux GmbH
Tel: 0911-740 53 0 Maxfeldstrasse 5
FAX: 0911-740 53 479 D-90409 Nürnberg
HRB: 21284 (AG Nürnberg) Germany
GF: Felix Imendörffer, Jane Smithard
GF: Jennifer Guild, Dilip Upmanyu, Graham Norton
http://www.suse.de
-------------------------------------------------------

Rodrigo Oshiro

unread,
May 8, 2015, 8:58:30 AM5/8/15
to kiwi-...@googlegroups.com, m...@suse.com
Thank you for the reply. I will try the ova alternative and see how far I can get, then post the findings.

Rodrigo Oshiro

unread,
May 8, 2015, 10:18:49 AM5/8/15
to kiwi-...@googlegroups.com, m...@suse.com
I have the following ovftool version installed:

# ovftool --version
VMware ovftool 3.5.0 (build-1274719)

config.xml:
<type image="vmx" filesystem="ext3" boot="vmxboot/suse-SLES12" primary="true" format="ova" bootloader="grub2" firmware="efi" kernelcmdline="splash">

    <systemdisk name="systemVG">
        <volume name="swap" size="6144"/>
    </systemdisk>
    <machine memory="4096" guestOS="sles12-64" HWversion="7" arch="x86_64">
            <vmdisk controller="lsilogic" id="0" diskmode="streamOptimized"/>

            <vmdvd  controller="ide" id="0"/>
            <vmnic driver="vmxnet3" interface="0" mode="bridged"/>
    </machine>
    <size unit="G">50</size>
</type>

# kiwi --build /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.102/src -d /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.102/image/OVA
May-08 09:36:49 <1> : --> Starting image format conversion...
May-08 09:36:49 <1> : EXEC [parted /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.102/image/OVA/vmx-appliance/DevKitSLIM.x86_64-12.0.0.1.102.raw print 2>&1]
May-08 09:36:49 <1> : Starting raw => ova conversion
May-08 09:36:49 <1> : EXEC [mkdir -p /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.102/image/OVA/vmx-appliance/DevKitSLIM.x86_64-12.0.0.1.102.ovf]
May-08 09:36:49 <1> : EXEC [ln -s ../DevKitSLIM.x86_64-12.0.0.1.102.raw /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.102/image/OVA/vmx-appliance/DevKitSLIM.x86_64-12.0.0.1.102.ovf/DevKitSLIM.x86_64-12.0.0.1.102.raw]
May-08 09:36:49 <1> : Creating vmx image machine configuration
May-08 09:36:49 <1> : Creating image OVF configuration file
May-08 09:36:49 <1> : EXEC [/usr/bin/uname -m]
May-08 09:36:49 <2> : --> No OVF type specified using fallback "vmware".
May-08 09:36:49 <1> : EXEC [/usr/bin/uname -m]
May-08 09:36:49 <3> : Could not find expected image '/opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.102/image/OVA/vmx-appliance/DevKitSLIM.x86_64-12.0.0.1.102.ovf/DevKitSLIM.x86_64-12.0.0.1.102.vmdk'
May-08 09:36:49 <1> : EXEC [sync]
May-08 09:36:49 <1> : EXEC [sync]
May-08 09:36:49 <1> : EXEC [rm -rf /tmp/kiwiboot.bnzgxD 2>&1]
May-08 09:36:49 <1> : EXEC [rm -rf /tmp/kiwiloop.toQeIY 2>&1]
May-08 09:36:49 <1> : EXEC [rm -rf /tmp/kiwiboot.6rwBW0 2>&1]
May-08 09:36:49 <1> : EXEC [sync]
May-08 09:36:49 <1> : EXEC [sync]
May-08 09:36:49 <1> : EXEC [/usr/bin/uname -m]
May-08 09:36:49 <1> : EXEC [mv -f /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.102/image/OVA/vmx-appliance/* /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.102/image/OVA 2>&1]
May-08 09:36:49 <1> : Find build results at: /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.102/image/OVA
May-08 09:36:49 <1> : Closing session with ecode: 0
May-08 09:36:50 <1> : KIWI exited successfully
May-08 09:36:50 <1> : EXEC [mv /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.102/image/OVA/build/image-root.4441.screenrc.log /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.102/image/OVA/build/image-root.log 2>&1]
May-08 09:36:50 <1> : Complete logfile at: /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.102/image/OVA/build/image-root.log
May-08 09:36:50 <1> : Release package manager lock
May-08 09:36:50 <1> : EXEC [rm -f /var/lock/kiwi-init.lock]
May-08 09:36:50 <1> : Release package manager lock
May-08 09:36:50 <1> : EXEC [rm -f /var/lock/kiwi-init.lock]
May-08 09:36:50 <1> : EXEC [rm -rf /opt/ADG/createAppliance/jobs/DevKitSLIM-12.0.0.1.102/image/OVA/vmx-appliance/boot-VMX.nLFf2k 2>&1]
May-08 09:36:50 <1> : EXEC [rm -f /var/cache/kiwi/zypper/zypper.conf.4441 /var/cache/kiwi/zypper/zypp.conf.4441]

But not many useful files for deploying were created:

# tree OVA
OVA
|-- DevKitSLIM.x86_64-12.0.0.1.102.ovf
|   `-- DevKitSLIM.x86_64-12.0.0.1.102.raw -> ../DevKitSLIM.x86_64-12.0.0.1.102.raw
|-- DevKitSLIM.x86_64-12.0.0.1.102.packages
|-- DevKitSLIM.x86_64-12.0.0.1.102.pids
|-- DevKitSLIM.x86_64-12.0.0.1.102.raw
|-- DevKitSLIM.x86_64-12.0.0.1.102.verified
|-- initrd-vmxboot-suse-SLES12.x86_64-2.7.1.gz
|-- initrd-vmxboot-suse-SLES12.x86_64-2.7.1.kernel -> initrd-vmxboot-suse-SLES12.x86_64-2.7.1.kernel.3.12.28-4-default
|-- initrd-vmxboot-suse-SLES12.x86_64-2.7.1.kernel.3.12.28-4-default
|-- initrd-vmxboot-suse-SLES12.x86_64-2.7.1.kernel.3.12.28-4-default.md5
|-- initrd-vmxboot-suse-SLES12.x86_64-2.7.1.md5
|-- initrd-vmxboot-suse-SLES12.x86_64-2.7.1.splash.gz -> initrd-vmxboot-suse-SLES12.x86_64-2.7.1.gz
`-- kiwi.buildinfo

Anyway, even if outputs a single OVA file instead, then I would then need to split this file into OVF/VMDK pair, so I could mount the VMDK disk locally, as I would a raw image file.

Marcus Schäfer

unread,
May 11, 2015, 6:40:13 AM5/11/15
to Rodrigo Oshiro, kiwi-...@googlegroups.com
Hi,

> I have the following ovftool version installed:
> # ovftool --version
> VMware ovftool 3.5.0 (build-1274719)

mine is VMware ovftool 3.5.1 (build-1743917), guess this is close
enough for testing.

I found several issues with the current code and fixed them.
I don't have a VSphere env around to test it but maybe you
can give it another try:

> But not many useful files for deploying were created:

With ova format the important data is the .ova like:

/tmp/mytest/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ova

this is what ovftool has created and it usually contains data like

tar -tf /tmp/mytest/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ova

LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ovf
LimeJeOS-openSUSE-13.2.x86_64-1.13.2.mf
LimeJeOS-openSUSE-13.2.x86_64-1.13.2-disk1.vmdk

In order to let you directly process the .ovf and the .vmdk kiwi extracts
this information from the tarball and overwrites its own result with
it. kiwi reports this like:

May-11 12:30:55 <1> : Replacing qemu's vmdk file with version from generated OVA
May-11 12:30:56 <1> : Replacing kiwi's ovf file with version from generated OVA

I will submit new kiwi packages today evening

v7.02.46

Let me know if that brings you any further

Regards,
Marcus
--
Public Key available via: https://keybase.io
keybase search marcus_schaefer
-------------------------------------------------------
Marcus Schäfer (Res. & Dev.) SUSE Linux GmbH
Tel: 0911-740 53 0 Maxfeldstrasse 5
FAX: 0911-740 53 479 D-90409 Nürnberg
HRB: 21284 (AG Nürnberg) Germany
GF: Felix Imendörffer, Jane Smithard
GF: Dilip Upmanyu, Graham Norton
http://www.suse.de
-------------------------------------------------------

Rodrigo Oshiro

unread,
May 11, 2015, 7:02:31 AM5/11/15
to kiwi-...@googlegroups.com, m...@suse.com
Thanks! I just looked that was another post entry about it, I will take a look at this version.

Prakash Kumar

unread,
Jun 18, 2015, 3:06:05 AM6/18/15
to kiwi-...@googlegroups.com, m...@suse.com
hi,

I am getting the same error even after changing the format="ova". I am trying to deploy the image in VCenter Server 5.0.

Looks like the kiwi generated .ovf file doesn't have the xml elements in correct order..

Line 20: Missing child element 'Info'
Line 21: Unsupported element 'osType'
Line 22: Unsupported element 'Info'
Line 42: Unsupported element 'Weight'
Line 95: Unsupported element 'Automatic-Allocation'
Line 95: Unsupported element 'Connection'

As an alternative, I have converted the kiwi generated .vmx file to .ova using ovftool command, then the image got deployed properly without any issues.

ovftool CentOS-06.4.x86_64-1.2.0.vmx  CentOS-06.4.x86_64-1.2.0.ova


Regards,
Prakash.

Marcus Schäfer

unread,
Jun 18, 2015, 4:32:25 AM6/18/15
to Prakash Kumar, kiwi-...@googlegroups.com
Hi,

> I am getting the same error even after changing the format="ova". I am
> trying to deploy the image in VCenter Server 5.0.
> Looks like the kiwi generated .ovf file doesn't have the xml elements
> in correct order..
> Line 20: Missing child element 'Info'
> Line 21: Unsupported element 'osType'
> Line 22: Unsupported element 'Info'
> Line 42: Unsupported element 'Weight'
> Line 95: Unsupported element 'Automatic-Allocation'
> Line 95: Unsupported element 'Connection'
> As an alternative, I have converted the kiwi generated .vmx file to
> .ova using ovftool command, then the image got deployed properly
> without any issues.

right the ovf kiwi generates is usable for some systems like VirtualBox,
older Vsphere versions, powervm or zvm but is not up to date with VCenter 5
We have not enough resources to keep up with the format and requirements
on the VMware product side

Therefore kiwi uses ovftool too if it is installed on the system at
build time.

Prakash Kumar

unread,
Jun 18, 2015, 5:57:35 AM6/18/15
to kiwi-...@googlegroups.com, m...@suse.com
Thanks !!!  

Anyhow for now, let me go-ahead and follow the other approach (converting vmx to ova)

-Prakash

Mark Scott

unread,
Sep 22, 2015, 10:39:56 AM9/22/15
to kiwi, prak...@gmail.com, m...@suse.com
Hi,

How can I ensure that Kiwi uses the ovftool?

I am discovering the problems described by Prakash.  I am using the format 'ova', and the ovftool from VMware is in the path, so I would assume it should have used it.

Marcus Schäfer

unread,
Sep 22, 2015, 12:13:49 PM9/22/15
to kiwi-...@googlegroups.com, prak...@gmail.com
Hi,

> How can I ensure that Kiwi uses the ovftool?

which version of kiwi are we talking about ?

> I am discovering the problems described by Prakash. I am using the
> format 'ova', and the ovftool from VMware is in the path, so I would
> assume it should have used it.

yes this should be the case if the format attribute is set to 'ova'

format="ova"

See /usr/share/kiwi/modules/KIWIImageFormat::createOVFConfiguration()

#==========================================
# search for ovftool, needed for ova
#------------------------------------------
my $locator = KIWILocator -> instance();
my $ovftool = $locator -> getExecPath ('ovftool');
if (($format eq 'ova') && (! $ovftool)) {
$kiwi -> warning (
'--> ovftool not found, will create only ova tarball'
);
$kiwi -> skipped ();
}

So given you are using a relatively up to date kiwi version you should
either see a message that we did not find it or a call of it in an
[EXEC] block in the log file

If none of that applies I would assume this is an old kiwi version

Regards,
Marcus
--
Public Key available via: https://keybase.io
keybase search marcus_schaefer
-------------------------------------------------------
Marcus Schäfer (Res. & Dev.) SUSE Linux GmbH
Tel: 0911-740 53 0 Maxfeldstrasse 5
FAX: 0911-740 53 479 D-90409 Nürnberg
HRB: 21284 (AG Nürnberg) Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
http://www.suse.de
-------------------------------------------------------

Mark E. Scott Jr.

unread,
Sep 22, 2015, 1:39:50 PM9/22/15
to kiwi-...@googlegroups.com

Yes, I had seen that section.  My version is recent enough that it had it (dates to August 3rd – v7.03.13).

 

Sep-22 12:16:31 <1> : kiwi revision: 64fe4cbfc9fb134ad088a10d4213a56d9386fa97

 

Whether I choose OVF or OVA, I get an OVF with output similar to (but not exactly the same, for instance the ova returns ovf:href=”…-disk1.vmdk” which is invalid:

 

<?xml version="1.0" encoding="UTF-8"?>

<!-- KIWI generated ovf file -->

<ovf:Envelope xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1" xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData" xmlns:vmw="http://www.vmware.com/schema/ovf" xmlns:vssd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:vcloud="http://www.vmware.com/vcloud/v1.5" xsi:schemaLocation="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2.22.0/CIM_VirtualSystemSettingData.xsd http://www.vmware.com/schema/ovf http://www.vmware.com/schema/ovf http://schemas.dmtf.org/ovf/envelope/1 http://schemas.dmtf.org/ovf/envelope/1/dsp8023_1.1.0.xsd http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2.22.0/CIM_ResourceAllocationSettingData.xsd http://www.vmware.com/vcloud/v1.5 http://www.vmware.com/vcloud/v1.5 ">

<ovf:References>

                <ovf:File ovf:href="project.x86_64-0.0.1.vmdk" ovf:id="file-de3df643340a7ee6c23f0be07368e3d54b4064a0-1442942553" ovf:size="2096955392"/>

</ovf:References>

<ovf:DiskSection>

                <ovf:Info>Virtual disk information</ovf:Info>

                <ovf:Disk ovf:capacity="2096955392" ovf:capacityAllocationUnits="byte * 2^20" ovf:diskId="vmdisk-de3df643340a7ee6c23f0be07368e3d54b4064a0-1442942553" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" ovf:fileRef="file-de3df643340a7ee6c23f0be07368e3d54b4064a0-1442942553"/>

</ovf:DiskSection>

<ovf:NetworkSection>

                <ovf:Info>The list of logical networks</ovf:Info>

                <ovf:Network ovf:name="bridged">

                                <ovf:Description>The bridged network</ovf:Description>

                </ovf:Network>

</ovf:NetworkSection>

<ovf:VirtualSystem ovf:id="vm-de3df643340a7ee6c23f0be07368e3d54b4064a0-1442942553">

                <ovf:Info>A virtual machine</ovf:Info>

                <ovf:Name>project.x86_64-0.0.1</ovf:Name>

                <ovf:OperatingSystemSection ovf:id="36">

                                <vmw:osType>LINUX</vmw:osType>

                                <ovf:Info>Image cretaed by KIWI</ovf:Info>

                </ovf:OperatingSystemSection>

 

Kiwi run log file:

Sep-22 12:21:51 <1> : EXEC [/usr/bin/uname -m]

Sep-22 12:21:51 <1> : --> Starting image format conversion...

Sep-22 12:21:51 <1> : EXEC [parted /home/mark_scott_jr/code/project/appliance/vmdk/target/appliance/output/vmx/vmx-CentOS/project.x86_64-0.0.1.raw print 2>&1]

Sep-22 12:21:51 <1> : Starting raw => ovf conversion

Sep-22 12:21:51 <1> : Creating vmdk image...

Sep-22 12:21:51 <1> : EXEC [/usr/bin/qemu-img convert -f raw /home/mark_scott_jr/code/project/appliance/vmdk/target/appliance/output/vmx/vmx-CentOS/project.x86_64-0.0.1.raw -O vmdk /home/mark_scott_jr/code/project/appliance/vmdk/target/appliance/output/vmx/vmx-CentOS/project.x86_64-0.0.1.vmdk 2>&1]

Sep-22 12:22:17 <1> : EXEC [mkdir -p /home/mark_scott_jr/code/project/appliance/vmdk/target/appliance/output/vmx/vmx-CentOS/project.x86_64-0.0.1.ovf]

Sep-22 12:22:17 <1> : EXEC [ln -s ../project.x86_64-0.0.1.vmdk /home/mark_scott_jr/code/project/appliance/vmdk/target/appliance/output/vmx/vmx-CentOS/project.x86_64-0.0.1.ovf/project.x86_64-0.0.1.vmdk]

Sep-22 12:22:17 <1> : Creating vmdk image machine configuration

Sep-22 12:22:17 <1> : Creating image VMware configuration file...

Sep-22 12:22:17 <1> : Creating vmx image machine configuration

Sep-22 12:22:17 <1> : Creating image OVF configuration file

Sep-22 12:22:17 <1> : EXEC [/usr/bin/uname -m]

Sep-22 12:22:17 <1> : EXEC [/usr/bin/uname -m]

Sep-22 12:22:17 <1> : Write OVF configuration file

Sep-22 12:22:17 <1> : --> /home/mark_scott_jr/code/project/appliance/vmdk/target/appliance/output/vmx/vmx-CentOS/project.x86_64-0.0.1.ovf/project.x86_64-0.0.1.ovf

Sep-22 12:22:33 <2> : --> Unknown guest OS 'rhel7' using generic Linux setup

Sep-22 12:22:33 <2> : --> No nominal CPU count set, using 1

Sep-22 12:22:33 <2> : --> No disk disktype set, using "scsi"

Sep-22 12:22:33 <1> : EXEC [mv /home/mark_scott_jr/code/project/appliance/vmdk/target/appliance/output/vmx/vmx-CentOS/project.x86_64-0.0.1.ovf /home/mark_scott_jr/code/project/appliance/vmdk/target/appliance/output/vmx/vmx-CentOS/project.x86_64-0.0.1.ovf.tmp]

Sep-22 12:22:33 <1> : EXEC [mkdir -p /home/mark_scott_jr/code/project/appliance/vmdk/target/appliance/output/vmx/vmx-CentOS]

Sep-22 12:22:33 <1> : EXEC [mv -f /home/mark_scott_jr/code/project/appliance/vmdk/target/appliance/output/vmx/vmx-CentOS/project.x86_64-0.0.1.ovf.tmp/* /home/mark_scott_jr/code/project/appliance/vmdk/target/appliance/output/vmx/vmx-CentOS]

Sep-22 12:22:33 <1> : EXEC [rmdir /home/mark_scott_jr/code/project/appliance/vmdk/target/appliance/output/vmx/vmx-CentOS/project.x86_64-0.0.1.ovf.tmp]

Sep-22 12:22:34 <1> : EXEC [sync]

Sep-22 12:22:38 <1> : EXEC [sync]

Sep-22 12:22:38 <1> : EXEC [rm -rf /tmp/kiwiboot.JZe3no 2>&1]

Sep-22 12:22:38 <1> : EXEC [rm -rf /tmp/kiwiloop.jwpvqE 2>&1]

Sep-22 12:22:38 <1> : EXEC [rm -rf /tmp/kiwiboot.1Cz5EW 2>&1]

Sep-22 12:22:38 <1> : EXEC [sync]

Sep-22 12:22:38 <1> : EXEC [sync]

Sep-22 12:22:38 <1> : EXEC [/usr/bin/uname -m]

Sep-22 12:22:38 <1> : EXEC [mv -f /home/mark_scott_jr/code/project/appliance/vmdk/target/appliance/output/vmx/vmx-CentOS/* /home/mark_scott_jr/code/project/appliance/vmdk/target/appliance/output/vmx 2>&1]

Sep-22 12:22:38 <1> : Find build results at: /home/mark_scott_jr/code/project/appliance/vmdk/target/appliance/output/vmx

Sep-22 12:22:38 <1> : Closing session with ecode: 0

Sep-22 12:22:40 <1> : KIWI exited successfully

 

I didn’t get any errors about not being able to locate the ovftool.

 

I’ll try to look further into it, because I assume until I know otherwise, that it is still my mistake.

 

 

Kiwi config file:

                                <!--<type image="vmx" boot="vmxboot/rhel-07.0" filesystem="ext3" format="ova" kernelcmdline="selinux=1"-->

                                <type image="vmx" boot="vmxboot/rhel-07.0" filesystem="ext3" format="ovf" kernelcmdline="selinux=1"

                                                                                bootloader="grub2" primary="true">

                                                <machine memory="2048" guestOS="rhel7" ovftype="vmware">

                                                                <vmdisk id="0" controller="ide"/>

                                                                <vmnic driver="e1000" interface="0" mode="bridged"/>

                                                </machine>

                                                <size additive="true" unit="G">32</size>

                                                <systemdisk name="AppVG">

                                                                <!--volume name="home" freespace="500M"/-->

                                                                <volume name="swap" freespace="8192M"/>

                                                </systemdisk>

                                </type>

 

Regards,

 

Mark E. Scott, Jr.

msc...@scott-usa.com

--

You received this message because you are subscribed to the Google Groups "kiwi" group.

To unsubscribe from this group and stop receiving emails from it, send an email to kiwi-images...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Marcus Schäfer

unread,
Sep 23, 2015, 3:19:02 AM9/23/15
to kiwi-...@googlegroups.com
Hi,

> Yes, I had seen that section. My version is recent enough that it had
> it (dates to August 3^rd – v7.03.13).

yes that's pretty new. I have tried to reproduce the issue but had no
luck so far. My type definition for testing is:

<type image="vmx"
filesystem="ext3"
boot="vmxboot/suse-13.2"
format="ova"
bootloader="grub2"
kernelcmdline="splash"
firmware="efi">

This is the standard suse-13.2 JeOS template from the kiwi-template package
I build the image and in the log I see:

--------snip--------

Sep-23 09:05:40 <1> : Write OVF configuration file
Sep-23 09:05:40 <1> : --> /tmp/mytest/vmx-vmxFlavour/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ovf/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ovf
Sep-23 09:05:43 <2> : --> No nominal CPU count set, using 1
Sep-23 09:05:43 <2> : --> No disk disktype set, using "scsi"
Sep-23 09:05:43 <1> : EXEC [sha1sum /tmp/mytest/vmx-vmxFlavour/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ovf/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ovf | cut -f1 -d ' ' 2>&1]
Sep-23 09:05:43 <1> : EXEC [sha1sum /tmp/mytest/vmx-vmxFlavour/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.vmdk | cut -f1 -d ' ' 2>&1]
Sep-23 09:05:46 <1> : EXEC [rm -f /tmp/mytest/vmx-vmxFlavour/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ova && cd /tmp/mytest/vmx-vmxFlavour/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ovf && ovftool --diskMode=streamOptimized LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ovf /tmp/mytest/vmx-vmxFlavour/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ova 2>&1]
Sep-23 09:05:56 <1> : Replacing qemu's vmdk file with version from generated OVA
Sep-23 09:05:56 <1> : EXEC [rm -f /tmp/mytest/vmx-vmxFlavour/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.vmdk /tmp/mytest/vmx-vmxFlavour/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ovf/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.vmdk]
Sep-23 09:05:56 <1> : EXEC [tar -h -C /tmp/mytest/vmx-vmxFlavour/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ovf -xf /tmp/mytest/vmx-vmxFlavour/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ova LimeJeOS-openSUSE-13.2.x86_64-1.13.2-disk1.vmdk 2>&1]
Sep-23 09:05:57 <1> : EXEC [mv /tmp/mytest/vmx-vmxFlavour/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ovf/LimeJeOS-openSUSE-13.2.x86_64-1.13.2-disk1.vmdk /tmp/mytest/vmx-vmxFlavour/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ovf/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.vmdk]
Sep-23 09:05:57 <1> : Replacing kiwi's ovf file with version from generated OVA
Sep-23 09:05:57 <1> : EXEC [rm -f /tmp/mytest/vmx-vmxFlavour/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ovf/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ovf /tmp/mytest/vmx-vmxFlavour/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ovf/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.mf]
Sep-23 09:05:57 <1> : EXEC [tar -h -C /tmp/mytest/vmx-vmxFlavour/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ovf -xf /tmp/mytest/vmx-vmxFlavour/LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ova LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ovf]

--------snap--------

ovftool is installed on my machine in '/usr/bin/ovftool'

ovftool --version

VMware ovftool 3.5.1 (build-1743917)

A short look into the generated ovf told me:

<ovf:File ovf:href="LimeJeOS-openSUSE-13.2.x86_64-1.13.2-disk1.vmdk" ovf:id="file-3edd9e018fa9ecf4b1c729311c7e3564153614b9-1442991943" ovf:size="315464192"/>

which exists in the ova tarball:

tar -tf LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ova

LimeJeOS-openSUSE-13.2.x86_64-1.13.2.ovf
LimeJeOS-openSUSE-13.2.x86_64-1.13.2.mf
LimeJeOS-openSUSE-13.2.x86_64-1.13.2-disk1.vmdk

I'm sorry I could not find the bug at the moment
Reply all
Reply to author
Forward
0 new messages