Hi, I'm having a problem with ovftool. I'm running ovftool against a ESXi host with a trial license. The command shows the ovf properties that I've set on the commandline, but once I'm on the virtual machine, the ovf environment is not present at all. If I do the deployment through the vSphere client, it works perfectly, same OVA file.

I see the output from ovftool:

--> /prop/ip0 = "192.168.43.159"

--> /prop/ip1 = "192.168.43.185"

but also get the warnings:

Hi,

We have been trying to create the monolithicSparse Image for the Vapp Ovf using the following OVF Tool command-Line Options

/usr/bin/ovftool --acceptAllEulas -dm=monolithicSparse Test_Vapp.ovf NEW_Vapp.vmdk

But the Ovf tool fails to do the conversion with the following message

Error: OVF Package is not supported by target.

We have also tried validating the Vapp ovf file using the ovftool schemaValidate and did not find any issues with this.

Please let us know if the Ovf tool supports conversion for multiple virtual machines (i.e support for Vapp OVF)

Thanks in advance

I'm deploying OVA files to a vCenter using ovftool; it's working perfectly, but I want to go the extra mile and automatically set the hostname of the VM after it is deployed.

I found a reference to a 'hostname' property (--prop:hostname=myvm.example.com), but it doesn't actually work

Here's my command  line

ovftool --lax --acceptAllEulas --datastore=MySAN --overwrite --powerOn --vmFolder=TestFolder --diskMode=thin --powerOffTarget --prop:hostname=myvm.example.comhttp://myurl.com/path/input.ova vi://vcenteruser:password@mycenter.example.com/MyDC/host/MyD/Resources/OVFTest

So what is the proper way to do this?

Greetings

We have developed a perl script in Linux that uses ovftools to deploy our VMs onto a vCenter installation.  We recently tried this on a new customers lab and ran into a weird error not seen before.  The issue is when ovftool is called to deploy the VM it starts fine and a see the VM created in vCenter but after a period of time I have seen a couple different errors:


One time the error was:

mtc@orchestrator-vm-pristine:~$ ovftool --noSSLVerify --net:'data=data' --net:'ipc=ipc' --net:'mgmt=mgmt' --datastore='datastore1 (4)' --name='vmme01-mgmt-1' --machineOutput "/usr/local/epc/data/working/b98d9334-c966-4ff8-a2d3-ab8bcff6a3d8/epc-os-mgmt-vm/epc-os-mgmt-vm.ovf" vi://Administrator%40vSphere.local:WaffleMan5000%21@10.30.0.130/MTS-MME-LAB/host/side-1/10.30.0.79
MANIFEST
+ <ManifestValidate valid="true"/>
PROGRESS
ERROR
+ <Errors>
+ <Error>
+ <Type>ovftool.abort</Type>
+ <LocalizedMsg>
+ Execution aborted
+ </LocalizedMsg>
+ </Error>
+ </Errors>
/usr/bin/ovftool: line 23: 2288 Segmentation fault (core dumped) "$OVFTOOL_BIN" "$@"
mtc@orchestrator-vm-pristine:~$ ovftool -v
VMware ovftool 3.5.0 (build-1274719)

After trying a couple different times I started seeing a different error, <Type> Lost connection </Type>.  This all works fine in other installations so there is something unique to this install.  Is there a document that describes the packet flow and setup for ovftools pushing the ovf/ova's out to the host?  Were are logs stored to be able to track down the issue?


 


Thanks


Eric Wolf


 

Hello,

I'm attempting to do a vmware to ovf converstion.  However, I'm receiving some fairly generic errors from ovftool and was hoping I could get some help.

Here are the console messages when I attempt to convert:

[root@provisionvrpt ~]# /usr/bin/ovftool --machineOutput --X:logToConsole=true /var/lib/vmware/Virtual\ Machines/vm/test.vmx /var/lib/vmware/Virtual\ Machines/vmovf/test.ovf
[2011-08-16 00:42:55.990 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 2 (SIGINT)
[2011-08-16 00:42:55.990 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 4 (SIGILL)
[2011-08-16 00:42:55.990 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 6 (SIGABRT)
[2011-08-16 00:42:55.990 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 8 (SIGFPE)
[2011-08-16 00:42:55.990 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 15 (SIGTERM)
[2011-08-16 00:42:55.990 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 1 (SIGHUP)
[2011-08-16 00:42:55.990 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 3 (SIGQUIT)
[2011-08-16 00:42:55.990 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 5 (SIGTRAP)
[2011-08-16 00:42:55.990 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 9 (SIGKILL)
[2011-08-16 00:42:55.991 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 13 (SIGPIPE)
[2011-08-16 00:42:55.991 B7FAC6D0 verbose 'ovftool'] [ovfTool.cpp] Using home directory /root/.ovftool
[2011-08-16 00:42:55.991 B7FAC6D0 verbose 'ovftool'] [ovfTool.cpp] OvfTool Environment:
/X:fencedMode = "bridged"
/X:imageReadSize = "262144"
/X:logToConsole = "true"
/X:maxNumberOfTermSignals = "5"
/X:maxRedirects = "256"
/X:maximalDeltaConfSize = "8"
/X:maximalDeltaTreeSize = "6"
/X:progressSmoothing = "60"
/X:vimSessionTimeout = "600"
/authdPortSource = "902"
/authdPortTarget = "902"
/machineOutput = "true"
/prgPath = "/opt/vmware/ovftool"
/source = "/var/lib/vmware/Virtual Machines/vm/test.vmx"
/target = "/var/lib/vmware/Virtual Machines/vmovf/test.ovf"

[2011-08-16 00:42:56.000 B7FAC6D0 verbose 'ovftool'] [ovfTool.cpp] Done initializing libs
[2011-08-16 00:42:56.000 B7FAC6D0 verbose 'ovftool'] [ovfTool.cpp] Determining source
[2011-08-16 00:42:56.212 B7FAC6D0 verbose 'ovftool'] [ovfTool.cpp] Determining target
[2011-08-16 00:42:57.488 B7FAC6D0 verbose 'ovftool'] Failed to open disk: /var/lib/vmware/Virtual Machines/vm/test.vmdk
[2011-08-16 00:42:57.488 B7FAC6D0 verbose 'ovftool'] Exception: The specified virtual disk needs repair
Error: Failed to open disk: test.vmdk
[2011-08-16 00:42:57.493 B7FAC6D0 verbose 'ovftool'] Backtrace:
[00] rip 050210b3
[01] rip 04eb6e9e
[02] rip 04e55ec2
[03] rip 081c014b
[04] rip 08310271
[05] rip 08311b54
[06] rip 0831ad24
[07] rip 0831b1f7
[08] rip 0831b74c
[09] rip 081f871a
[10] rip 0816fa45
[11] rip 080cd318
[12] rip 0317be9c
[13] rip 080ae4f1

But when I attempt to repair the disk, I get the following:

vmware-vdiskmanager -R /var/lib/vmware/Virtual\ Machines/vm/test.vmdk
No errors were found on the virtual disk, '/var/lib/vmware/Virtual Machines/vm/test.vmdk'.

Any help would be apprecaited.  Is there a way to increase the verbosity of the logging?

Here is my ovftool version info: VMware ovftool 2.0.1 (build-260188)

Thanks!

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?

Installed ovftool 3.5 on CentOS 5.9.  Install went without any errors, says Installation Successful.

Running ovftool yields about 5 errors similar to:

/usr/lib/vmware-ovftool/ovftool.bin: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by /usr/lib/vmware-ovftool/libvmomi.so)

CentOS 5.9 doesn't support GLIBC 3.4.

The ovftool documentation says it supports CentOS 5 and 6.

What's the problem here?

Hi,

I'm getting the following error when trying to convert from VMX to OVF:

1. ovftool ./n1dps/Solaris\ 10\ 64-bit\ Single\ Partition.vmx ./ovf/n1dps.knerr.us.ovf

Opening VMX source: ./n1dps/Solaris 10 64-bit Single Partition.vmx

Error:

- Device 'cdrom1' has a backing type that is not supported. This is a general limitation of the virtual machine's virtual hardware version on the selected host.

System Information:

Host: CentOS 5.0 64bit

Vmware Server version=1.0.6 build=build-91891 option=Release.3.2.2

Instance: Solaris 10

I notice the target is Vmware Server 2.x and upgrading is on the task list.  I thought I'd post this in the mean time and see if anyone had any answers.

Thank you,

George

Update: I just removed the cdrom1 device and am now in the process of running the script as it did not give the cdrom1 error this time.

HI,

I'm trying to create an OVF using ovftool 3.0.1. When I issue the ovftool command from the command line I get:

Error: cURL error: Couldn't connect to server
Completed with errors

I used the following command:

/usr/bin/ovftool vi://username:password@XX.XX.XX.XX/datacenter/vm/folder/vmname /destination

I can issue the command as above without the vmname to see if I can access Vsphere and to make sure I have a valid source locator.  The command is successful and returns a list of VMs I can use. When I add the VM name to the source locator path, I get the above error. The VM is pysically about 14GB in size (that is the space alloacted).

I can use the same command to another Vpshere server and I'm successful in creating the OVF. Which leads me to think that it might be a configuration issue with this Vsphere server?

What sorts of issues can lead to the above error?

Thanks,

Fernando

I'm trying to use ovftool to automate OVA deployments to vCloud Director 5.1. I have installed ovftool 3.0.1 on Ubuntu and tested out some operations. Everything seems to work except that I always get a segmentation fault when I invoke a vcloud target.

Here is the logging output:

2013-04-12T09:38:22.261-07:00 [7F987B01E740 verbose 'Default'] [SSL_DB] Using /home/evan/.ovftool.ssldb as SSL DB
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 2 (SIGINT)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 4 (SIGILL)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 6 (SIGABRT)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 8 (SIGFPE)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 15 (SIGTERM)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 1 (SIGHUP)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 3 (SIGQUIT)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 5 (SIGTRAP)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 9 (SIGKILL)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 13 (SIGPIPE)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] OvfTool Version: VMware ovftool 3.0.1 (build-801290)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Using home directory: /home/evan/.ovftool
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] OvfTool Environment:
--> /X:httpTimeout = "0"
--> /X:imageReadSize = "262144"
--> /X:logToConsole = "true"
--> /X:maxNumberOfTermSignals = "5"
--> /X:maxRedirects = "256"
--> /X:maximalDeltaConfSize = "8"
--> /X:maximalDeltaTreeSize = "6"
--> /X:progressSmoothing = "60"
--> /X:useMacNaming = "false"
--> /X:vCloudEnableGuestCustomization = "false"
--> /X:vCloudKeepTemplate = "true"
--> /X:vCloudTimeout = "3600"
--> /X:vimSessionTimeout = "600"
--> /authdPortSource = "902"
--> /authdPortTarget = "902"
--> /fencedMode = "bridged"
--> /prgPath = "/usr/lib/vmware-ovftool"
--> /source = "vcloud://vclouddirector.intapp.net/"
--> /vCloudTemplate = "false"
-->
2013-04-12T09:38:22.270-07:00 [7F987B01E740 verbose 'Default'] Done initializing libs
2013-04-12T09:38:22.270-07:00 [7F987B01E740 verbose 'Default'] Determining source
2013-04-12T09:38:22.270-07:00 [7F987B01E740 verbose 'Default'] Determining target
2013-04-12T09:38:22.302-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.617-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.617-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.617-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.617-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.617-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.617-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.619-07:00 [7F987B01E740 verbose 'Default'] VCloud request body:
-->
2013-04-12T09:38:22.641-07:00 [7F987B01E740 verbose 'Default'] VCloud response body:
--> <?xml version="1.0" encoding="UTF-8"?>
--> <SupportedVersions xmlns="http://www.vmware.com/vcloud/versions" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.vmware.com/vcloud/versionshttp://vclouddirector/api/versions/schema/versions.xsd">
-->     <VersionInfo>
-->         <Version>1.5</Version>
-->         <LoginUrl>https://vclouddirector.intapp.net/api/sessions</LoginUrl>
   ... schema output snipped ...
-->
2013-04-12T09:38:22.648-07:00 [7F987B01E740 verbose 'Default'] VCloud version used: 5.1

The end of the strace output:

[pid 15407] munmap(0x7f8b32f7c000, 135168) = 0
[pid 15407] munmap(0x7f8b32f9d000, 135168) = 0
[pid 15407] munmap(0x7f8b3cadb000, 135168) = 0
[pid 15407] write(6, "\25\3\1\0\30B& 2\7\30\3259W0n~(4\216\375\"\35\310c\211{+\350", 29) = 29
[pid 15407] close(6)                    = 0
[pid 15407] brk(0x2c17000)              = 0x2c17000
[pid 15407] brk(0x2c38000)              = 0x2c38000
[pid 15407] write(1, "2013-04-12T09:40:54.198-07:00 [7"..., 882013-04-12T09:40:54.198-07:00 [7F8B3CB7F740 verbose 'Default'] VCloud version used: 5.1
) = 88
[pid 15407] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
Process 15404 resumed
Process 15407 detached
[pid 15410] +++ killed by SIGSEGV (core dumped) +++
[pid 15409] +++ killed by SIGSEGV (core dumped) +++
[pid 15408] +++ killed by SIGSEGV (core dumped) +++
[pid 15411] +++ killed by SIGSEGV (core dumped) +++
<... wait4 resumed> [{WIFSIGNALED(s) && WTERMSIG(s) == SIGSEGV && WCOREDUMP(s)}], 0, NULL) = 15407
write(2, "/usr/bin/ovftool: line 23: 15407"..., 91/usr/bin/ovftool: line 23: 15407 Segmentation fault      (core dumped) "$OVFTOOL_BIN" "$@"
) = 91
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
--- SIGCHLD (Child exited) @ 0 (0) ---
wait4(-1, 0x7fff27453e98, WNOHANG, NULL) = -1 ECHILD (No child processes)
rt_sigreturn(0xffffffffffffffff)        = 0
rt_sigaction(SIGINT, {SIG_DFL, [], SA_RESTORER, 0x7f70fceb44a0}, {0x43f140, [], SA_RESTORER, 0x7f70fceb44a0}, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
read(255, "", 409)                      = 0
exit_group(139)                         = ?

Hi All,

I have just come across ovftool and was giving a try to it. I am fairly new to VMware world.

I have a  .OVF which I exported using vSphere client 4.0. This .OVF comprises of 3 Suse Linux based virtual machines. i.e. I created a vApp on ESX (4.1) host, in this vApp I put my 3 SLES VMs and then exported it as OVF.

It has a total size of around 4.5GB.

Now I ran this command to compress this .OVF as well as gave an option to create deltadisks.

C:\> ovftool --compress=9 --makeDeltaDisks --skipManifestCheck  MyVMCluster\MyVMCluster.ovf   E:\

output:

{{{

The manifest does not validate
Generating delta disks for 2 disks (capacity 40960 MB)
Reading disks
Disk Transfer Completed

Determining optimal configuration for capacity group
Writing configuration to disk
Disk Transfer Completed

Completed successfully

}}}

Now when I checked my E:\ It had created a folder with the same name and put related files there. I saw a significant reduction in the new vmdk size. ( around 2.3GB now )

Now when I manually deploy this new ovf on vSphere client, it goes till certain %age and then flags an error:

{{{

Error uploading file to server ( E:\MyVMCluster\disk3.vmdk.gz ) Not a supported disk format ( Invalid sparse vmdk header )

}}}

and then it stops and everything rolledback.

Any pointers ?

Thanks

Nikunj

I'm trying to create an additional property in my VM that I build with VMware Studio so that I can use OVFTool to pass a value for the property when I deploy the VM to a vCenter.

The property looks like that shown in red.  But when I invoke OVFTool to give a value to this property, what am I supposed to be using? 

Something like this I can't get to work:

    ovftool  <...>  --prop.ConfigurationManagementServer.My_VM_Name= 10.1.2.3   <..>

Thanks for any hints,

CJ

        <Section xsi:type="vadk:IpAssignmentSection_Type">

                <Info>Supported IP assignment schemes</Info>

                <vmw:IpAssignmentSection ovf:required="false" vmw:protocols="IPv4,IPv6" vmw:schemes="">

                        <Info>Supported IP assignment schemes</Info>

                </vmw:IpAssignmentSection>

        </Section>

        <Section xsi:type="vadk:PropertySection_Type">

                <Info/>

                <Property ovf:key="ConfigurationManagementServer" ovf:type="string" ovf:userConfigurable="true" ovf:value="puppet" ovf:qualifiers="MinLen(0),MaxLen(65535)">

                        <Label>Configuration Management Server (Optional)</Label>

                        <Description>Your configuration management server&apos;s fully-qualified name (e.g. config.avamar.com ). Blank if none.</Description>

                </Property>

        </Section>

        <Section xsi:type="vadk:AnyOVFSection_Type">

                <Info>

            Unknown OVF elements in this element will be passed directly

            to the OVF output descriptor without interpretation

        </Info>

        </Section>

        <Section xsi:type="vadk:UpdateSection_Type">

                <Info/>

                <vadk:Repository vadk:url="" vadk:username="" vadk:password="" vadk:passwordFormat="base64"/>

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?

Hi,

I have a ESXi 5.0 server running which has a Guest VM running CentOS 5.6.

The ESXi server is a standalone server, not included in a datacenter, not managed by vCenter.

The server has a HDD of 80G which has both the ESXi host & the Guest OS running on top of it.

I installed ovftools on my Windows laptop & tried to create a ovf from the VM but am unsuccessful. I constantly get the following error -

c:\>ovftool vi://root:<rootpassword>@<ESXi Host IP>/datastore1/CentOS c:\testVM.ovf

Error: Cannot parse locater: vi://root:<rootpassword>@<ESXi Host IP>/datastore1/CentOS

Completed with errors

The local datastore name is "datastore1"

Can someone help me out here with forming the correct the ovftool command to create an ovf & possibly an OVA out of the running VM?

Thanks

Bhushan Pathak

I have VMware Player 5.0.0. It internally has ovftool 3.0.1

I used VMware Studio2.0 to build an appliance in  OVA format  - It opened successfully by Player 5.0

Converted OVA -> OVF again from OVF->OVA using ovftool 3.0.1. (This is just for testing. Later I need to change OVF according to my need).

Now this re-generated OVA file is not supported by Player5.0. When I tried to open OVA file, Player failed with error 'Failed to open virtual machine: Failed to open OVF descriptor.'

Is this an issue with OVFTool or Player ? Please suggest.

BTW, I have used the below commands for convertion

Thanks in advance

--hemanth

I am trying to convert a .ovf to a .vmx using the ovftool utility in terminal on OSX 10.6.8.

USING the --lax command, the result I get is as follows:

Any suggestions on how to fix this?  It seems to be a problem with ovftool itself?

I want to clone a VMware VM (RHEL6.5), export it as an OVF and when someone deploys it again, I want them to enter custom information like IP, DNS, VM name in the vSphere Deploy wizard. How do i make this happen? (I've commented all the lines in the persistent net rules file and made the file read-only.)

I have a setup where I am accessing vCenter and an ESXi host through a NAT layer. If I try to deploy directly to vCenter, ovftool automatically tries to connect to the ip address of the ESXi host behind the NAT layer, which fails.

It looks something like this:

[root@ovfimporter mnt]# date; ovftool --datastore="PayGo Storage" --net:"VLan 4=DedicatedPortGroup_NNNN" CUST/CUST.ovf vi://matthew.wallace@10.10.10.1/Customer\ Datacenter/host/PayGo\ Cluster/Resources/Paygo/NNNN\ \(abc44060-35dc-438a-8c79-6bc7586082ab\)/ ;date

Tue Oct  8 10:18:43 MDT 2013

Opening OVF source: CUST/CUST.ovf

The manifest validates

Enter login information for target vi://10.10.10.1/

Username: matthew.wallace

Password: *********

Opening VI target: vi://matthew.wallace@10.10.10.1:443/Customer%20Datacenter/host/PayGo%20Cluster/Resources/Paygo/NNNN%20(abc44060-35dc-438a-8c79-6bc7586082ab)/

Deploying to VI: vi://matthew.wallace@10.10.10.1:443/Customer%20Datacenter/host/PayGo%20Cluster/Resources/Paygo/NNNN%20(abc44060-35dc-438a-8c79-6bc7586082ab)/

Transfer Failed

Transfer Failed

Error: Lost connection to target

Completed with errors

Tue Oct  8 10:20:19 MDT 2013

Looking at netstat, I saw a hung connection to 443 of one of the ESX hosts in that PayGo Cluster:

In this case, 172.17.0.10 is the "real" IP of one of the esx hosts in the PayGo cluster managed by that vCenter, which I can reach from the client running the ovftool only by using the NAT ip of 10.10.10.100.

So, I tried to specify the external ip of that host. Per the ovftool 3.5 user guide:

Given that, I tried using several syntaxes:

ovftool --datastore="PayGo Storage" --net:"VLan 4=DedicatedPortGroup_NNNN" CUST/CUST.ovf vi://matthew.wallace@10.10.10.1/Customer\ Datacenter/host/PayGo\ Cluster/Resources/Paygo/NNNN\ \(abc44060-35dc-438a-8c79-6bc7586082ab\)/?ip=10.10.10.100

or even just the simplest version to see if I can get a prompt for going further down in the locator tree:

ovftool --datastore="PayGo Storage" --net:"VLan 4=DedicatedPortGroup_NNNN" "vi://matthew.wallace@10.10.10.1/?ip=10.10.10.100"

I invariably get a result like this:

The manifest validates

Enter login information for target vi://10.10.10.1/

Username: matthew.wallace

Password: *********

Error: Locator does not refer to an object: vi://matthew.wallace@10.10.10.1:443/?ip=10.10.10.100

Completed with errors

Outside of the brief mention of the "ip=xxx" param mentioned in the ovftool userguide I've been unable to find any reference to someone successfully using this parameter so I'm uncertain if this is a bug, my not understanding the intention of the parameter as specified in the OVF tool guide, or me using bad syntax.

I am trying to import OVF with custom propery set and getting folling error with vmware ovf tool. Any idea on how to resolve this issue?

Error:

- Line 107: Unsupported element 'Property'

Hello..

Is it possible to give vCenter appliance ip, gateway, netmask etc via ovftool? Same way as to Orchestrator.

--prop:vami.DNS.VMware_vCenter_Server_Appliance=10.0.0.69  --prop:vami.gateway.VMware_vCenter_Server_Appliance=10.0.0.1  --prop:vami.ip0.VMware_vCenter_Server_Appliance=10.0.0.96  --prop:vami.netmask0.VMware_vCenter_Server_Appliance=255.255.255.0

When running these commands with ovftool, it doesnt give any errors  or anything, but it doesnt pass the variables forward either. Clearly  vCenter appliance doesnt have any "intelligence" for such feature.

ovftool --acceptAllEulas --skipManifestCheck  --datastore=storage-1 --diskMode=thin --name=vcenter --prop:vami.DNS.VMware_vCenter_Server_Appliance=10.0.0.69   --prop:vami.gateway.VMware_vCenter_Server_Appliance=10.0.0.1   --prop:vami.ip0.VMware_vCenter_Server_Appliance=10.0.0.96   --prop:vami.netmask0.VMware_vCenter_Server_Appliance=255.255.255.0

/VMware-vCenter-Server-Appliance-5.0.0.3324-472350/VMware-vCenter-Server-Appliance-5.0.0.3324-472350_OVF10.ovf.backup  vi://10.0.0.10

So any tips? Do I need to create some external media and modify the appliance to add it in, which will pass the needed variables to appliance, and script which will run from init.d on start and read those?

-k-