OVFTool cannot set property successfully

September 15, 2011, 2:49 am

Latest and popular articles on VMWare Virtualization

≫ Next: ovftool.exe crashes when deploying OVA from Windows 7

≪ Previous: Is there a way to specify static IP for a deploying OVA in the ovftool command?

I want to set some properties to ovf files.

I use ovftool as bellow:

ovftool --prop:ip=10.32.23.123 --prop:dns=255.255.254.0

when this command has been executed without error showing, I still cannot see the property of ovf files.

Then I used ovftool myovffile.ovf

I still can not see the property I want to set.

what should I do?

↧

ovftool.exe crashes when deploying OVA from Windows 7

January 13, 2012, 8:54 am

Latest and popular articles on VMWare Virtualization

≫ Next: MAC ovftool not working

≪ Previous: OVFTool cannot set property successfully

I'm experiencing a coredump when attempting to deploy an OVA into vCenter 5.0.0. I have downloaded the OVA to the Windows 7 PC locally and have run the ovftool from that path as follows:

ovftool --X:logToConsole=true --X:logLevel="verbose" --name=ovf-test --datastore=datastore-local-113 --network=VLAN-603 MVF-ver-2_OVF10.ova "vi://Administrator:**********@10.45.99.10/MitelDesignCenter/host/VLabCluster-03 (Intel G6, stand-alone)/10.45.12.113"

The verbose output looks like this:

2012-01-13T11:45:23.595-05:00 [04492 verbose 'Default'] Subscribing to signal: 2 (SIGINT)

2012-01-13T11:45:23.596-05:00 [04492 verbose 'Default'] Subscribing to signal: 4 (SIGILL)

2012-01-13T11:45:23.596-05:00 [04492 verbose 'Default'] Subscribing to signal: 22 (SIGABRT)

2012-01-13T11:45:23.598-05:00 [04492 verbose 'Default'] Subscribing to signal: 8 (SIGFPE)

2012-01-13T11:45:23.599-05:00 [04492 verbose 'Default'] Subscribing to signal: 15 (SIGTERM)

2012-01-13T11:45:23.600-05:00 [04492 verbose 'Default'] [ovfTool.cpp] Using home directory C:\Users\hinchleg\AppData\Roa

ming\VMware\ovftool.cfg

2012-01-13T11:45:23.601-05:00 [04492 verbose 'Default'] [ovfTool.cpp] OvfTool Environment:

--> /X:httpTimeout = "600"

--> /X:imageReadSize = "262144"

--> /X:logLevel = "verbose"

--> /X:logToConsole = "true"

--> /X:maxNumberOfTermSignals = "5"

--> /X:maxRedirects = "256"

--> /X:maximalDeltaConfSize = "8"

--> /X:maximalDeltaTreeSize = "6"

--> /X:progressSmoothing = "60"

--> /X:useMacNaming = "false"

--> /X:vCloudKeepTemplate = "true"

--> /X:vCloudTimeout = "3600"

--> /X:vimSessionTimeout = "600"

--> /authdPortSource = "902"

--> /authdPortTarget = "902"

--> /datastore = "datastore-local-113"

--> /fencedMode = "bridged"

--> /name = "ovf-test"

--> /network = "VLAN-603"

--> /prgPath = "C:\Program Files\VMware\VMware OVF Tool"

--> /source = "MVF-ver-2_OVF10.ova"

--> /target = "vi://Administrator:**********@10.45.99.10/MitelDesignCenter/host/VLabCluster-03 (Intel G6, stand-alone)

/10.45.12.113"

-->

2012-01-13T11:45:23.609-05:00 [04492 verbose 'Default'] [ovfTool.cpp] Done initializing libs

2012-01-13T11:45:23.609-05:00 [04492 verbose 'Default'] [ovfTool.cpp] Determining source

2012-01-13T11:45:23.630-05:00 [04492 verbose 'Default'] [ovfTool.cpp] Determining target

Opening OVA source: MVF-ver-2_OVF10.ova

2012-01-13T11:45:23.634-05:00 [04492 verbose 'Default'] Manifest file present. Parsing file.

2012-01-13T11:45:23.635-05:00 [04492 verbose 'Default'] Manifest file entry: SHA(MVF-ver-2_OVF10.ovf) = 2926495bbde18cdb

3e738e390258bd2009996156

2012-01-13T11:45:23.637-05:00 [04492 verbose 'Default'] Manifest file entry: SHA(system.vmdk) = e1fe00f518356b3741789fa6

7567e9c8bf3fffe7

The manifest validates

2012-01-13T11:45:23.642-05:00 [04492 verbose 'Default'] Verifying that the files references in manifest are valid

2012-01-13T11:45:23.644-05:00 [04492 verbose 'Default'] OVF Descriptor: <?xml version="1.0" encoding="UTF-8"?>

--> <ovf:Envelope xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1" xmlns="http://schemas.dmtf.org/ovf/envelope/1" xmln

s:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData" xmlns:vssd="http://schemas.

dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" x

mlns:vmw="http://www.vmware.com/schema/ovf">

--> <References>

--> <File ovf:href="system.vmdk" ovf:size="488976384" ovf:id="system.vmdk_id"/>

--> </References>

--> <NetworkSection>

--> <Info>List of logical networks used in the package</Info>

--> <Network ovf:name="Network 1">

--> <Description>Network 1</Description>

--> </Network>

--> </NetworkSection>

--> <vmw:IpAssignmentSection ovf:required="false" vmw:protocols="IPv4" vmw:schemes="ovfenv">

--> <Info>Supported IP assignment schemes</Info>

--> </vmw:IpAssignmentSection>

--> <DiskSection>

--> <Info>List of the virtual disks and partitions needed</Info>

--> <Disk ovf:diskId="system" ovf:capacity="5120" ovf:capacityAllocationUnits="byte * 2^20" ovf:format="http://www.v

mware.com/interfaces/specifications/vmdk.html#streamOptimized" ovf:fileRef="system.vmdk_id" ovf:populatedSize="135456358

4"/>

--> </DiskSection>

--> <VirtualSystem ovf:id="MVF-ver-2">

--> <Info>A virtual machine</Info>

--> <ProductSection ovf:required="false">

--> <Info>VM ISV branding information</Info>

--> <Product>MVF-ver-2</Product>

--> <Vendor>Mitel Networks Corporation</Vendor>

--> <!--

--> Version is the actual product version in the

--> form X.X.X.X where X is an unsigned 16-bit integer.

-->

--> FullVersion is a descriptive version string

--> including, for example, alpha or beta designations

--> and other release criteria.

--> -->

--> <Version>1.0.13.0</Version>

--> <FullVersion>MVF 1.0.13.0 (design) on MSL 9.4.12.0</FullVersion>

--> <ProductUrl/>

--> <VendorUrl/>

--> <AppUrl>http://${vami.ip0.MVF-ver-2}/</AppUrl>

--> <Category>Application</Category>

--> <Property ovf:key="admin_pass" ovf:type="string" ovf:userConfigurable="true" ovf:value="" ovf:qualifiers="MinL

en(0),MaxLen(32)" ovf:password="true">

--> <Label>Initial Administrator Password</Label>

--> <Description>The initial password to use to when accessing this deployed virtual appliance.</Description>

--> </Property>

--> <Property ovf:key="domain_name" ovf:type="string" ovf:userConfigurable="true" ovf:value="xyzcorp.com" ovf:qual

ifiers="MinLen(0),MaxLen(256)">

--> <Label>Domain Name</Label>

--> <Description>The domain name this virtual appliance should belong to.</Description>

--> </Property>

--> <Property ovf:key="ssh_access" ovf:type="string" ovf:userConfigurable="true" ovf:value="none" ovf:qualifiers="

ValueMap{"none","local networks","public"}">

--> <Label>Remote SSH Access</Label>

--> <Description>The level of accessibility for remote shell access to this system.</Description>

--> </Property>

--> <Property ovf:key="local_net_ip" ovf:type="string" ovf:userConfigurable="true" ovf:value="0.0.0.0" vmw:qualifi

ers="Ip">

--> <Label>Local Network Network Address</Label>

--> <Description>The network address where remote access, including web admin access, is available.</Description

--> </Property>

--> <Property ovf:key="local_net_netmask" ovf:type="string" ovf:userConfigurable="true" ovf:value="0.0.0.0" vmw:qu

alifiers="Ip">

--> <Label>Local Network Netmask</Label>

--> <Description>The netmask to define the subnet range within the local network address.</Description>

--> </Property>

--> <Property ovf:key="mitel_arid" ovf:type="string" ovf:userConfigurable="true" ovf:value="" ovf:qualifiers="MinL

en(0),MaxLen(20)">

--> <Label>Mitel Application Record ID</Label>

--> <Description>The license key to apply to this virtual appliance.</Description>

--> </Property>

--> </ProductSection>

--> <ProductSection ovf:class="vami" ovf:instance="MVF-ver-2" ovf:required="false">

--> <Info>VAMI Properties</Info>

--> <Category>Networking Properties</Category>

--> <Property ovf:key="ip0" ovf:userConfigurable="true" ovf:type="string" vmw:qualifiers="Ip('Network 1')">

--> <Label>Network 1 IP Address</Label>

--> <Description>The IP address for this interface.</Description>

--> </Property>

--> <Property ovf:key="netmask0" ovf:userConfigurable="true" ovf:type="string" vmw:qualifiers="Netmask('Network 1'

)">

--> <Label>Network 1 Netmask</Label>

--> <Description>The netmask or prefix for this interface.</Description>

--> </Property>

--> <Property ovf:key="gateway0" ovf:userConfigurable="true" ovf:type="string" vmw:qualifiers="Gateway('Network 1'

)">

--> <Label>Network 1 Default Gateway</Label>

--> <Description>The default gateway address for this VM.</Description>

--> </Property>

--> <Property ovf:key="DNS0" ovf:userConfigurable="true" ovf:type="string" vmw:qualifiers="Dns('Network 1')">

--> <Label>Network 1 DNS</Label>

--> <Description>The domain name servers for this VM (comma separated).</Description>

--> </Property>

--> </ProductSection>

--> <ProductSection ovf:class="vm" ovf:required="false">

--> <Info>VM specific properties</Info>

--> <Property ovf:key="vmname" ovf:type="string" ovf:value="MVF-ver-2"/>

--> </ProductSection>

--> <AnnotationSection>

--> <Info/>

--> <Annotation/>

--> </AnnotationSection>

--> <OperatingSystemSection ovf:id="79" ovf:version="5" vmw:osType="mslGuest">

--> <Info>Guest Operating System</Info>

--> <Description>MSL 9.3</Description>

--> </OperatingSystemSection>

--> <VirtualHardwareSection ovf:transport="com.vmware.guestInfo" ovf:required="false">

--> <Info>Virtual Hardware Requirements</Info>

--> <System>

--> <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>

--> <vssd:InstanceID>0</vssd:InstanceID>

--> <vssd:VirtualSystemType>vmx-07</vssd:VirtualSystemType>

--> </System>

--> <Item>

--> <rasd:AllocationUnits>hertz * 10^6</rasd:AllocationUnits>

--> <rasd:Description>Number of virtual CPUs</rasd:Description>

--> <rasd:ElementName xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettin

gData">1 virtual CPU</rasd:ElementName>

--> <rasd:InstanceID xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSetting

Data">1</rasd:InstanceID>

--> <rasd:ResourceType>3</rasd:ResourceType>

--> <rasd:VirtualQuantity>1</rasd:VirtualQuantity>

--> </Item>

--> <Item>

--> <rasd:AllocationUnits>byte * 2^20</rasd:AllocationUnits>

--> <rasd:Description>Memory Size</rasd:Description>

--> <rasd:ElementName xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettin

gData">1024 MB of memory</rasd:ElementName>

--> <rasd:InstanceID xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSetting

Data">2</rasd:InstanceID>

--> <rasd:ResourceType>4</rasd:ResourceType>

--> <rasd:VirtualQuantity>1024</rasd:VirtualQuantity>

--> </Item>

--> <Item>

--> <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>

--> <rasd:Connection>Network 1</rasd:Connection>

--> <rasd:ElementName xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettin

gData">Ethernet adapter on vmnet</rasd:ElementName>

--> <rasd:InstanceID xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSetting

Data">3</rasd:InstanceID>

--> <rasd:ResourceSubType>VMXNET3</rasd:ResourceSubType>

--> <rasd:ResourceType>10</rasd:ResourceType>

--> </Item>

--> <Item>

--> <rasd:Address xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingDat

a">0</rasd:Address>

--> <rasd:ElementName xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettin

gData">SCSI Controller 0 - lsilogic</rasd:ElementName>

--> <rasd:InstanceID xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSetting

Data">4</rasd:InstanceID>

--> <rasd:ResourceSubType>lsilogic</rasd:ResourceSubType>

--> <rasd:ResourceType>6</rasd:ResourceType>

--> </Item>

--> <Item>

--> <rasd:AddressOnParent>0</rasd:AddressOnParent>

--> <rasd:ElementName xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettin

gData">Harddisk 1</rasd:ElementName>

--> <rasd:HostResource>ovf:/disk/system</rasd:HostResource>

--> <rasd:InstanceID xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSetting

Data">5</rasd:InstanceID>

--> <rasd:Parent>4</rasd:Parent>

--> <rasd:ResourceType>17</rasd:ResourceType>

--> </Item>

--> </VirtualHardwareSection>

--> </VirtualSystem>

--> </ovf:Envelope>

-->

2012-01-13T11:45:23.802-05:00 [04492 verbose 'HttpConnectionPool'] HttpConnectionPoolImpl created. maxPoolConnections =

20; idleTimeout = 900000000; maxOpenConnections = 20; maxConnectionAge = 0

2012-01-13T11:45:24.876-05:00 [05124 verbose 'Default'] CURL: => Send header GET /sdk/vimServiceVersions.xml HTTP/1.1

--> Authorization: Basic QWRtaW5pc3RyYXRvcjpQQVNTd29yZDEyMzQ=

--> User-Agent: VMware-client/4.0.0 (ovfTool; libcurl)

--> Host: 10.45.99.10

--> Accept: */*

-->

2012-01-13T11:45:24.879-05:00 [05124 verbose 'Default'] CURL: <= Recv header HTTP/1.1 200 OK

-->

2012-01-13T11:45:24.879-05:00 [05124 verbose 'Default'] CURL: <= Recv header Date: Fri, 13 Jan 2012 16:45:25 GMT

-->

2012-01-13T11:45:24.884-05:00 [05124 verbose 'Default'] CURL: <= Recv header Cache-Control: no-cache

-->

2012-01-13T11:45:24.887-05:00 [05124 verbose 'Default'] CURL: <= Recv header Connection: Keep-Alive

-->

2012-01-13T11:45:24.889-05:00 [05124 verbose 'Default'] CURL: <= Recv header Content-Type: text/xml; charset=utf-8

-->

2012-01-13T11:45:24.891-05:00 [05124 verbose 'Default'] CURL: <= Recv header Content-Length: 492

-->

2012-01-13T11:45:24.893-05:00 [05124 verbose 'Default'] CURL: <= Recv header

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

--> <!--

--> -->

--> <namespaces version="1.0">

--> <namespace>

--> <name>urn:vim25</name>

--> <version>5.0</version>

--> <priorVersions>

--> <version>4.1</version>

--> <version>4.0</version>

--> <version>2.5u2</version>

--> <version>2.5</version>

--> </priorVersions>

--> </namespace>

--> <namespace>

--> <name>urn:vim2</name>

--> <version>2.0</version>

--> </namespace>

--> </namespaces>

-->

2012-01-13T11:45:24.896-05:00 [04492 verbose 'Default'] [ViConnection] Using vim API version: 5.0

2012-01-13T11:45:24.947-05:00 [04492 verbose 'HttpConnectionPool'] HttpConnectionPoolImpl created. maxPoolConnections =

1; idleTimeout = 900000000; maxOpenConnections = 1; maxConnectionAge = 0

2012-01-13T11:45:24.967-05:00 [04492 verbose 'Default'] Keeping VI session alive

Opening VI target: 2012-01-13T11:45:24.994-05:00 [04492 info 'Default'] CoreDump: Writing minidump

2012-01-13T11:45:25.044-05:00 [04492 panic 'Default']

-->

--> Panic: Win32 exception: Access Violation (0xc0000005)

--> Read (0) at address 0000000000000018

--> rip: 00000001401e4dcb rsp: 000000000012f470 rbp: 0000000000000018

--> rax: 0000000000000000 rbx: 000000000012f5c0 rcx: ffffffffffffffff

--> rdx: 0000000140000000 rdi: 0000000000000018 rsi: 0000000000000001

--> r8: 0000000000000003 r9: 0000000000000000 r10: 000000000012f828

--> r11: 000000000012f640 r12: 00000000036451cb r13: 0000000000000002

--> r14: 0000000000000075 r15: 0000000000000000

-->

--> Backtrace:

--> backtrace[00] rip 000000000055693a (no symbol)

--> backtrace[01] rip 000000000042d008 (no symbol)

--> backtrace[02] rip 000000000042dc1e (no symbol)

--> backtrace[03] rip 000000000056db28 (no symbol)

--> backtrace[04] rip 000000000056dc97 (no symbol)

--> backtrace[05] rip 0000000000570b56 (no symbol)

--> backtrace[06] rip 0000000068975129 (no symbol)

--> backtrace[07] rip 00000000689742d6 (no symbol)

--> backtrace[08] rip 00000000689749de (no symbol)

--> backtrace[09] rip 0000000068974c1d (no symbol)

--> backtrace[10] rip 000000006897502b (no symbol)

--> backtrace[11] rip 000000014025f1ae (no symbol)

--> backtrace[12] rip 0000000077289d0d (no symbol)

--> backtrace[13] rip 00000000772791af (no symbol)

--> backtrace[14] rip 00000000772b1278 (no symbol)

--> backtrace[15] rip 00000001401e4dcb (no symbol)

--> backtrace[16] rip 00000001401e6c73 (no symbol)

--> backtrace[17] rip 00000001401e1b04 (no symbol)

--> backtrace[18] rip 00000001401cbfd9 (no symbol)

--> backtrace[19] rip 00000001400dbae5 (no symbol)

--> backtrace[20] rip 00000000003d7b65 (no symbol)

--> backtrace[21] rip 00000000003d7c8e (no symbol)

--> backtrace[22] rip 00000001400986f9 (no symbol)

--> backtrace[23] rip 000000014001af4b (no symbol)

--> backtrace[24] rip 000000014001b76a (no symbol)

--> backtrace[25] rip 000000014025f62e (no symbol)

--> backtrace[26] rip 000000007715652d (no symbol)

--> backtrace[27] rip 000000007728c521 (no symbol)

-->

↧

MAC ovftool not working

April 16, 2012, 1:42 pm

Latest and popular articles on VMWare Virtualization

≫ Next: ovftool deploy failing with "Network connection was lost"

≪ Previous: ovftool.exe crashes when deploying OVA from Windows 7

When I try to fun ovftool from the terminal I get the error message

'ovftool: command not found'

i.e. m'ovftool Photo_[Work]/VirtualBoxMachines/copyxp\ Base\ V.vmx Photo_[Work]/VBConversions/xpvb.ovf'

???

Thanks.

Pedro

↧

ovftool deploy failing with "Network connection was lost"

February 23, 2013, 8:49 pm

Latest and popular articles on VMWare Virtualization

≫ Next: Attempting to deploy .OVA from fileserver to ESXi host and/or vSphere cluster

≪ Previous: MAC ovftool not working

Hey,

Is anybody aware of what network flows exist when deploying an ovf file using ovftool through a vCenter? Right now ovftool is continually erroring out with the following message:

Transfer Failed
Error: Network connection was lost.
Completed with errors

When watching on the vCenter I can see that the virtual machine is created but then it looks like data is never actually transferred. So I know that the initial connection to vCenter is successful.

I'm guessing the initial connection happens with vCenter and then the data transfer occurs directly with the ESX. Would be very appreciative if somebody could confirm this and identify the port that the data transfer happens on.

Thanks,

-Chris

↧

Attempting to deploy .OVA from fileserver to ESXi host and/or vSphere cluster

June 28, 2013, 7:08 am

Latest and popular articles on VMWare Virtualization

≫ Next: Escaping backslashes (or other special characters) in the FTP locator

≪ Previous: ovftool deploy failing with "Network connection was lost"

I am attempting to determine an easy method to deploy .OVA templates for quick provisioning/deployment of VM's.

I have built VM baselines using a development vSphere cluster and exported the VM to .OVA using vSphere client. Those .OVA files reside on a Linux fileserver with ovftool installed on the system and network access to future ESXi and/or vSphere clusters.

Is it possible to 'deploy' the .OVA template from the Linux fileserver directly to a remote ESXi host's datastore and/or vSphere cluster datastore? I cant get it to work.

My OVA file:

[root@centos_lab1 u0]# ls -lha

total 5.9G

drwxr-xr-x. 3 root root 4.0K Jun 28 08:48 .

dr-xr-xr-x. 24 root root 4.0K Jun 25 11:30 ..

-rw-r--r-- 1 root root 5.9G Jun 24 10:01 test.ova

Attempting to deploy to ESXi host:

[root@centos_lab1 u0]# ovftool test.ova vi://root:test123@172.16.16.81

Opening OVA source: test.ova

Opening VI target: vi://root@172.16.16.81:443/

Error: No target datastore specified. Possible completions:

iSCSI-Large

ESX1_local_datastore

iSCSI-Equallogic

fusionio

Super_ISO

Completed with errors

[root@centos_lab1 u0]# ovftool test.ova vi://root:test123@172.16.16.81/iSCSI-Equallogic/

Opening OVA source: test.ova

Error: Locator does not refer to an object: vi://root@172.16.16.81:443ha-datacenter/host/esx1.lab.q9.com/Resources/iSCSI-Equallogic/

Completed with errors

Any idea what I am doing wrong here? Is what I am trying to do even possible with ovftool?

↧

Escaping backslashes (or other special characters) in the FTP locator

December 12, 2013, 6:00 pm

Latest and popular articles on VMWare Virtualization

≫ Next: Static IP given during OVA deployment doesnt take effect post deployment

≪ Previous: Attempting to deploy .OVA from fileserver to ESXi host and/or vSphere cluster

Using ovftool 3.0.1, I cannot figure out how to escape the backslash character when specifying the username and password in an FTP locator on the command line.

$ ovftool ftp://<DOMAIN>%5C<username>:<password>@<host>/Image.ova

keeps prompting me for the password, even if I repeatedly enter the correct one.

The same thing happens when I specify "ftp://<DOMAIN>%5C%5C<username>:<password>@<host>/Image.ova" instead.

Using the literal backslash character (i.e. <DOMAIN>\<username> or <DOMAIN>\\<username>) results in an error message saying "Error: cURL error: Couldn't resolve host name."

However, if I do not provide any credentials for the locator, ovftool prompts for the username and password. In that case, providing "<DOMAIN>\<username>" does work, though "<DOMAIN>%5C<username>" does not.

Please note that the FTP server unfortunately will not properly authenticate without prepending the domain.

↧

Static IP given during OVA deployment doesnt take effect post deployment

March 4, 2014, 2:29 pm

Latest and popular articles on VMWare Virtualization

≫ Next: getting error (core dumped) "$OVFTOOL_BIN" "$@" while using ovftool from jenkins instance

≪ Previous: Escaping backslashes (or other special characters) in the FTP locator

Hi Everyone,

I was trying to deploy a VM using the ovftool, I thought I would use the properties which are thrown from a "probe" of the OVA file.

ovftool http://server/files/builds/vpas/6.0.0/latest/vPAS-installer.ova

Properties:

ClassId: vami

Key: gateway

InstanceId vPAS

Category: Networking Properties

Label: Default Gateway

Type: string

Description: The default gateway address for this VM. Leave blank if DHCP is

desired.

ClassId: vami

Key: DNS

InstanceId vPAS

Category: Networking Properties

Label: DNS

Type: string

Description: The domain name servers for this VM (comma separated). Leave

blank if DHCP is desired.

ClassId: vami

Key: ip0

InstanceId vPAS

Category: Networking Properties

Label: Network 1 IP Address

Type: string

Description: The IP address for this interface. Leave blank if DHCP is

desired.

ClassId: vami

Key: netmask0

InstanceId vPAS

Category: Networking Properties

Label: Network 1 Netmask

Type: string

After having made sure that such properties exists from the probe, I tried to use them to give the VM a static IP post deployment, automatically.

ovftool --datastore="31_datastore" --acceptAllEulas --ipAllocationPolicy=fixedPolicy --name="vPAS_31_1" --powerOn --prop:ip0="172.16.121.115" --prop:netmask0="255.255.0.0" --prop:DNS="172.16.1.10" --prop:gateway="172.16.1.1" http://server/vpas/6.0.0/latest/vPAS-installer.ova vi://root:password@172.16.121.31/

Opening OVA source: http://server/files/builds/vpas/6.0.0/latest/vPAS-installer.ova

The manifest validates

Opening VI target: vi://root@172.16.121.31:443/

Deploying to VI: vi://root@172.16.121.31:443/

Transfer Completed

Powering on VM: vPAS_31_1

Warning:

- OVF property with key: 'DNS' does not exists.

- OVF property with key: 'gateway' does not exists.

- OVF property with key: 'ip0' does not exists.

- OVF property with key: 'netmask0' does not exists.

Completed successfully

Can someone please explain me whether this is a common problem ( from VMware ) or something I am doing wrong?

Thanks,

↧

getting error (core dumped) "$OVFTOOL_BIN" "$@" while using ovftool from jenkins instance

January 14, 2015, 1:33 pm

Latest and popular articles on VMWare Virtualization

≫ Next: Error exploit ova to vmx

≪ Previous: Static IP given during OVA deployment doesnt take effect post deployment

Hi,

When i try to configure deployment job from Jenkins, i am getting

/usr/bin/ovftool: line 23: 19723 Segmentation fault

(core dumped) "$OVFTOOL_BIN" "$@"

error in command line, Not sure how to find solution, i was able to use the same command from my local system directly from my user account.

This error i am getting after message

Opening OVF source: myfile.ovf

thanks in advance,

vduggirala

↧

Error exploit ova to vmx

September 25, 2015, 5:24 am

Latest and popular articles on VMWare Virtualization

≫ Next: Trying to convert .ova file to .vmx

≪ Previous: getting error (core dumped) "$OVFTOOL_BIN" "$@" while using ovftool from jenkins instance

hi,

i'm very newbie on terminal and i get this error when i tried to convert ova file to vmx. It says completed with errors but I can't locate any file, anywhere, and also the whole process is to fast for OVF Tolls to do anything.

What am i missing? Thanks

Miguel

MCR:~ mcr$ /Applications/VMware\ OVF\ Tool/ovftool --lax /Users/mcr/Downloads/untitled\ folder/Ubuntu\ FEUP/Ubuntu\ FEUP.ova exploit.vmx

Opening OVA source: /Users/mcr/Downloads/untitled folder/Ubuntu FEUP/Ubuntu FEUP.ova

Opening VMX target: exploit.vmx

Error: OVF Package is not supported by target:

- Line 92: Unsupported element 'StorageItem'

- Line 101: Unsupported element 'StorageItem'

- Line 110: Unsupported element 'EthernetPortItem'

Completed with errors

↧

Trying to convert .ova file to .vmx

January 14, 2016, 11:56 pm

Latest and popular articles on VMWare Virtualization

≫ Next: OVF property --nic to configure IP Address for multiple interfaces

≪ Previous: Error exploit ova to vmx

Hi ALL,

We are facing the below issue while trying to convert .ova file to .vmx in windows.

Command used: -:\Program Files\VMware\VMware OVF Tool>ovftool.exe --lax G:\PUM16\FSCM-920-UPD-016.ova G:\PUM16\FSCM-920-UPD-016.vmx

Error: -

2016-01-14T08:27:00.088-05:00 verbose -[07464] [Originator@6876 sub=Default] Creating disk Y:\\FSCM-920-UPD-016-disk1.vmdk, 20225836 sectors, ide

2016-01-14T08:27:00.135-05:00 verbose -[07464] [Originator@6876 sub=Default] Creating disk Y:\\FSCM-920-UPD-016-disk2.vmdk, 16803990 sectors, lsilogic

2016-01-14T08:27:00.166-05:00 verbose -[07464] [Originator@6876 sub=Default] Creating disk Y:\\FSCM-920-UPD-016-disk3.vmdk, 102430440 sectors, lsilogic

2016-01-14T08:27:00.260-05:00 verbose -[07464] [Originator@6876 sub=Default] Creating disk Y:\\FSCM-920-UPD-016-disk4.vmdk, 30748410 sectors, lsilogic

2016-01-14T08:27:00.291-05:00 verbose -[07464] [Originator@6876 sub=Default] Creating disk Y:\\FSCM-920-UPD-016-disk5.vmdk, 48196 sectors, lsilogic

2016-01-14T08:27:00.307-05:00 verbose -[07464] [Originator@6876 sub=Default] Creating disk Y:\\FSCM-920-UPD-016-disk6.vmdk, 54283636 sectors, lsilogic

2016-01-14T08:27:00.385-05:00 verbose -[07464] [Originator@6876 sub=Default] Using capacity as progress measure

2016-01-14T08:27:00.385-05:00 verbose -[07388] [Originator@6876 sub=Default] Opening disk target /FSCMDB-SES-854-16/VirtualIDEController0:0

2016-01-14T08:27:00.432-05:00 verbose -[07388] [Originator@6876 sub=Default] Capacity mismatch for disk Y:\\FSCM-920-UPD-016-disk1.vmdk: Existing 20225836 < incoming 20225920

2016-01-14T08:27:00.432-05:00 verbose -[07464] [Originator@6876 sub=Default] Backtrace:

-->

--> [backtrace begin] product: VMware Workstation, version: e.x.p, build: build-2444548, tag: -

↧

OVF property --nic to configure IP Address for multiple interfaces

April 17, 2017, 3:12 am

Latest and popular articles on VMWare Virtualization

≫ Next: Import OVA Template errors with "Could not convert field 'spec' of structure 'com.vmware.vcenter.vdcs.floppy_model'

≪ Previous: Trying to convert .ova file to .vmx

hi,

I am looking for an option to configure the IP Address while deploying the OVF template. In documentation it talks about

What Is New in OVF Tool 3.5.0

The following new ovftool options: --allowExtraConfig, --computerName, --coresPerSocket, --defaultStorageProfile, --diskSize, --maxVirtualHardwareVersion, --memorySize, --nic, --numberOfCpus, and --storageProfile.

But i do not see an exaple of how to configure the IP address for multiple interfaces. Only detail i see is:

--nic = Specifies NIC configuration in a VM using the syntax --nic:,=,,,. Possible values for ipAddressingMode are: DHCP, POOL, MANUAL, and NONE. ipAddress is optional and should only be used when ipAddressingMode is set to MANUAL. Only applies to vCloud targets of version 5.5 or newer.

↧

Import OVA Template errors with "Could not convert field 'spec' of structure 'com.vmware.vcenter.vdcs.floppy_model'

November 17, 2017, 2:38 pm

Latest and popular articles on VMWare Virtualization

≫ Next: Signed OVA package verification with ovftool failed

≪ Previous: OVF property --nic to configure IP Address for multiple interfaces

Hopefully this is the right place to ask this.

We have a product that's distributed as an OVA and have done so for years. We're finally getting around to supporting vSphere 6.5 but are running into an issue. If we deploy the OVA directly to a 6.5 host, the import works fine. However if we deploy via vCenter, it fails with the following error:

Failed to deploy OVF package.

Cause:

A general system error occurred:

An error occurred: Could not convert field 'spec' of structure 'com.vmware.vcenter.vdcs.floppy_model'

This only happens on vSphere 6.5. It works fine with vSphere 6.0 and earlier. When we create the template, we do have a floppy device (it's needed as we do our OS install during the build process) so I changed it so right before it creates the OVA using ovftool 4.1, I edit the vmx (while the vm is powered off) and remove all references to the floppy device. However the corresponding ovf file still has references to the floppy.

Any ideas what's going on and how to fix? I'm not sure why all of a sudden it stopped working in 6.5. From our end, the build process hasn't changes in years. I can attach the vmx and ovf files if that helps. Thanks!

↧

Signed OVA package verification with ovftool failed

March 25, 2010, 12:26 am

Latest and popular articles on VMWare Virtualization

≫ Next: ovftool "locator does not refer to an object"

≪ Previous: Import OVA Template errors with "Could not convert field 'spec' of structure 'com.vmware.vcenter.vdcs.floppy_model'

Greetings!

I'm currently trying to sign created OVA package with trusted certificate from Thawte.

This cert is valid (till 2013) and could be easily verified with openssl (`openssl verify sign.cert`) or with Windows tools.

Signing works as follows and it is okay:

ovftool --sourceType=vmx --targetType=ova --privateKey=sign.pem package.vmx package.ova

But when I try to check it with ovftool (`ovftool package.ova`) it shows:

Error: Verification of package.cert failed

Also verification of package.cert itself with openssl is also fine.

Can anybody help me on what could cause such problem?

Thanks in advance.

↧

ovftool "locator does not refer to an object"

March 20, 2011, 10:22 am

Latest and popular articles on VMWare Virtualization

≫ Next: OVFTool 2.1.0 with Active Directory Question (vSphere crashes)

≪ Previous: Signed OVA package verification with ovftool failed

I am trying to create an OVF from a vm in vsphere - I'm running ovftool on a linux machine, and using the following syntax (I got this from the ovftool users guide):

ovftool username@myvcenter.aaa.com/"datacenter name"/vm/vmname /local/path/tostoreit/vnname.ovf

It prompts for a password, I enter the password, and it comes back with:

Opening VI source: vi://username@myvcenter.aaa.com/datacenter name/vmname
Error: Locator does not refer to an object:vi://username@myvcenter.aaa.com/datacenter name/vmname

Incidentally, I get the exact same error when I try using the mac version of ovftool, and the windows version.

Please help - I know this should work. I have no idea what I'm doing wrong, but I have to get this working pretty fast.

Thank you!!

↧

OVFTool 2.1.0 with Active Directory Question (vSphere crashes)

January 23, 2012, 10:03 am

Latest and popular articles on VMWare Virtualization

≫ Next: Unsupported element 'Property' from ovftool and ESXi server

≪ Previous: ovftool "locator does not refer to an object"

When I try to export one of my VMs using File/Export/Export OVF Template....it crashes vSphere with a nice assertion window.

To see what the cause of this is, I decided to try using ovftool 2.1.0 on Linux to export the VM instead, to see what happens (like does it crash ovftool?).

I got stuck though because when I log into the vCenter I have to specify a domain\username format and I can't figure out how to pass this to ovftool in a way that doesn't cause errors.

For example, I tried things like this:

# ovftool vi://myvcenter.domain.com/DataCenterName/vm/

Username: MYDOMAIN\Administrator

Password: whatever

Didn't work, I don't think it likes the backslash.

So I tried stuffing it in a variable:

# DF="MYDOMAIN\Administrator"

# ovftool vi://"$DF"@myvcenter.domain.com/DataCenterName/vm/

Error: Curl error: Couldn't connect to server

Anyone have any ideas?

Thanks,

↧

Unsupported element 'Property' from ovftool and ESXi server

July 3, 2012, 8:39 am

Latest and popular articles on VMWare Virtualization

≫ Next: OVFtool bug when specifying datastore

≪ Previous: OVFTool 2.1.0 with Active Directory Question (vSphere crashes)

I'm trying to use the ovftool to import a OVA file into a ESXi server. However I get the following error

Error: OVF Package is not supported by target:
- Line 118: Unsupported element 'Property'
Completed with errors

The related lines in the OVF file are:

    <ProductSection ovf:class="vami" ovf:instance="*******">
      <Info>Information about the installed software</Info>
      <Category>Networking Properties</Category>
118-->      <Property ovf:key="gateway" ovf:type="string" ovf:userConfigurable="true">
        <Label>Default Gateway</Label>
        <Description>The default gateway address for this VM. Leave blank if DHCP is desired.</Description>
      </Property>
      <Property ovf:key="DNS" ovf:type="string" ovf:userConfigurable="true">

Based on some initial investigation I have done I beleive this is because the ProductSection is defaulting to required="true" which forces ESXi to use these fields, however ESXi doesn't seem to support this and it errors out as shown above.

The OVA file was generated using ovftoolto export VM in a vcenter instance. This OVA file imports fine into vcenter, but not ESXi

Is there anyway to configure ovftoolwhen run against vcenter to generate required="false" in the ProductSection elements?

<ProductSection ovf:class="vami" ovf:instance="*******" ovf:required="false">

Or some otherway to get ovftoolto export a VM from vcenter as an OVA that will import into ESXi?

ovftool 2.1, ESXi 4.1, vCenter 4.1

↧

OVFtool bug when specifying datastore

December 7, 2012, 6:16 pm

Latest and popular articles on VMWare Virtualization

≫ Next: Could not look up host [username]. Proper password, but will not convert

≪ Previous: Unsupported element 'Property' from ovftool and ESXi server

It appears that ovftool 3.0.1 has an issue while specifying the target datastore when importing an OVF when the VI is a vCenter 5.0 server with ESX 5.0 Update 1 hosts that have a large number of Datastores. The cluster where this problem occurs has 148 Datastores.

Some datastores work, most don't. This is a new problem since ovftool 2.0.1 worked fine when this cluster was at ESX 4.0 Update 3.

An example statement that will cause the problem (with all names replaced with "test" names):

"C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" --acceptAllEulas --name="TestVM" --datastore="TestDatastore" --network=TestNetwork --vmFolder="TestFolder" http://192.168.0.1/public/ovfs/testvm.ovf vi://"username:password"@vcenter.test.com/"Data Center"/host/"HA and DRS"/Resources/"Test Resource Pool"

Which results in this error (with the datastore names replaced with TestDatastoreX), even though the Datastore clearly exists. It worked fine prior to vSphere 5.0 and vCenter 5.0. Any ideas?

Note that all "possible completions" specified below work fine! Those that I have tried that are "not" in the possible completions do "not" work.

Error: Invalid target datastore specified (TestDatastore): Possible completions:

TestDatastore1

TestDatastore2

TestDatastore3

TestDatastore4

TestDatastore5

TestDatastore6

TestDatastore7

TestDatastore8

TestDatastore9

TestDatastore10

TestDatastore11

TestDatastore12

TestDatastore13

TestDatastore14

TestDatastore15

TestDatastore16

TestDatastore17

TestDatastore18

TestDatastore19

TestDatastore20

TestDatastore21

TestDatastore22

TestDatastore23

TestDatastore24

TestDatastore25

TestDatastore26

TestDatastore27

TestDatastore28

TestDatastore29

TestDatastore30

TestDatastore31

TestDatastore32

TestDatastore33

TestDatastore34

TestDatastore35

Completed with errors

↧

Could not look up host [username]. Proper password, but will not convert

December 16, 2012, 12:01 pm

Latest and popular articles on VMWare Virtualization

≫ Next: Problems trying to convert a .iso to .ova file

≪ Previous: OVFtool bug when specifying datastore

Hey all. I know I am using proper syntax, but it seems like there's a missing service running on my esx cluster. I am able to log in with vSphere, but cannot use ovftool to export a stopped server in my ESX 4.0 cluster environment.

command I am using:

ovftool vi://[username]:[password]@vi://192.168.77.111/[serverid] d:\[serveridoutput].ovf

the error I am receiving is as follows:

Error: Could not lookup host: [username]

Completed with errors

Now it's interesting because the server does seem to know that I am using a proper user/pass because if I make a mistake on the password, I am given another chance to log in, until I miss three tries. If I enter the correct password, it seems to almost connect, then fails out with the above error. I would *REALLY* appreciate some help with this guys.

Thanks in advance!

↧

Problems trying to convert a .iso to .ova file

September 12, 2013, 9:19 pm

Latest and popular articles on VMWare Virtualization

≫ Next: ovftool : Specify Hardware version during a conversion ?

≪ Previous: Could not look up host [username]. Proper password, but will not convert

I have a .iso image from which I want to create a .ova , But everytime I run into a problem

Error: Curl error: Couldn't connect to server

Completed with errors

Here is the command I used,

ovftool vi://user:master/@14.23.12.34:443/rt4/www/html/imgs/qweTER7.3/.tyRani/NEWCFT/CFT-NEW-5.23.23.iso /rt4/www/html/tmp_ova/CFT-NEW-5.23.23.ova

Not sure whats wrong with this command, I don't have special character in my password or username

please note that 14.23.12.34 is a linux machine and both source and target are in same machine and Im executing ovftool command in same linux machine.

Thank you

Mac

↧

ovftool : Specify Hardware version during a conversion ?

June 20, 2014, 3:27 am

Latest and popular articles on VMWare Virtualization

≫ Next: Question Installing OVFtool in ESXi 5.5U1

≪ Previous: Problems trying to convert a .iso to .ova file

Hi everybody,

I'd like to change the hardware version during an export using ovftool. Is there a way to specify it ?
I've seen the "--maxVirtualHardwareVersion" but I'm unable to understand how to use it. I can't find any documentation on the supported syntax anywhere.

Any advice ?

Jean-Baptiste

↧

Latest Images