Quantcast
Channel: VMware Communities : Popular Discussions - Open Virtualization Format Tool
Viewing all 34499 articles
Browse latest View live

ovftool Failed to send http data

$
0
0

Hi,

 

Can someone provide an indication on what is generating the following error when running ovftool to deploy a vm on a host in a vCenter?

 

Opening OVA source: /usr/local/path/to/ova/file.ova

The manifest validates

Opening VI target: vi://user@vCenter_ip:443/

Deploying to VI: vi://user@vCenter_ip:443/

^MTransfer Failed

^MTransfer Failed

Error: Failed to send http data

Completed with errors

 

The error reproduced on client setup to which I don't have access so I have no other additional logs.

 

Thanks.


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

$
0
0

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!

difference between ovf version 0.9 and 1.0?

$
0
0

 

What is the difference between OVF 1.0 and 0.9 version? I would be interested in knowing about the major enchancements made in the newer versions and thereby the advantages of the same.

 

 

 

 

 

Thanks in advance

 

 

ovftool "locator does not refer to an object"

$
0
0

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!!

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

$
0
0

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!

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

$
0
0

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.

Error Deploying OVF to Host

$
0
0


Hi everyone,


When I tried to launch the deploy command without indicating the host domain (scivsd05), the following error was launched: 


ovftool "X:logToConsole" "datastore=myds" "network=mynet" "machineOutput" --name="test13" test.ova "vi://user:pass@vcenter.domain.lan/&lt;mydc&gt;/host/&lt;mycluster&gt;/scivsd05"

...



2014-12-02T16:11:24.881+01:00 verbose Curl_perform error code 6 (Couldn't resolve host name)

2014-12-02T16:11:24.882+01:00 verbose CURL error buffer: Could not resolve host: scivsd05 (Domain name not found)

2014-12-02T16:11:24.882+01:00 verbose Connection error during upload

2014-12-02T16:11:24.882+01:00 verbose Connection error, sleep then retry (10 remaining)

...




If I indicate the host domain, then an "Locator does not refer to an object" error is launched:


ovftool "X:logToConsole" "datastore=myds" "network=mynet" "machineOutput" --name="test13" test.ova "vi://user:pass@vcenter.domain.lan/&lt;mydc&gt;/host/&lt;mycluster&gt;/scivsd05.domain.lan"

...



ERROR



+ <Errors>



+ <Error>



+ <Type>ovftool.locator.object</Type>



+ <LocalizedMsg>



+ Locator does not refer to an object: vi://userr@vcenter.domain.lan:443/<mydc>/host/<mycluster>/scivsd05.domain.lan



+ </LocalizedMsg>



+ <Arg>



+ vi://userr@vcenter.domain.lan:443/<mydc>/host/<mycluster>//scivsd05.domain.lan



+ </Arg>



+ </Error>



+ </Errors>



...




The name resolution for the ESXi host "scivsd05.domain.lan" is correct from both machines, the vCenter machine and the machine where OVFTool is installed.


Any idea? Thanks in advance!


 

When I tried to launch the deploy command without indicating the host domain (scivsd05), the following error was launched: 



 



ovftool "X:logToConsole" "datastore=myds" "network=mynet" "machineOutput" --name="test13" test.ova "vi://user:pass@vcenter.domain.lan/&lt;mydc&gt;/host/&lt;mycluster&gt;/scivsd05"

 



...



2014-12-02T16:11:24.881+01:00 verbose Curl_perform error code 6 (Couldn't resolve host name)

2014-12-02T16:11:24.882+01:00 verbose CURL error buffer: Could not resolve host: scivsd05 (Domain name not found)

2014-12-02T16:11:24.882+01:00 verbose Connection error during upload

2014-12-02T16:11:24.882+01:00 verbose Connection error, sleep then retry (10 remaining)

...



 



If I indicate the host domain, then an "Locator does not refer to an object" error is launched:



 



ovftool "X:logToConsole" "datastore=myds" "network=mynet" "machineOutput" --name="test13" test.ova "vi://user:pass@vcenter.domain.lan/&lt;mydc&gt;/host/&lt;mycluster&gt;/scivsd05.domain.lan"

 



...



ERROR



+ <Errors>



+ <Error>



+ <Type>ovftool.locator.object</Type>



+ <LocalizedMsg>



+ Locator does not refer to an object: vi://userr@vcenter.domain.lan:443/<mydc>/host/<mycluster>/scivsd05.domain.lan



+ </LocalizedMsg>



+ <Arg>



+ vi://userr@vcenter.domain.lan:443/<mydc>/host/<mycluster>//scivsd05.domain.lan



+ </Arg>



+ </Error>



+ </Errors>



...



 



The name resolution for the ESXi host "scivsd05.domain.lan" is correct from both machines, the vCenter machine and the machine where OVFTool is installed.



 



Any idea? Thanks in advance!


Trying to convert .ova file to .vmx

$
0
0

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: -


Signed OVA package verification with ovftool failed

$
0
0

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.

MAC ovftool not working

$
0
0

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

export from esxi4 always locator not refer to an object error

$
0
0

I am using ESXI 4 and I have a VM what I want to export to OVF every week or two. I am trying to use ovf tools and write a script to make this easier. No matter what I do, I always get the error "locator does not refer to an object".

 

My setup is ESXI 4.
VM Name is: SUGARCRM
Datastore path is: [datastore1]/debian/debian.vmx

 

According the to the instructions, the following should work, but they do not work for me. What is the correct command syntax?

 

ovftool.exe vi://root:mypassword@192.168.1.60/ha-datacenter/?ds=[datastore1]/debian/debian.vmx c:\vm\sugarcrm.ovf
Error: Locator does not refer to an object

ovftool.exe vi://root:mypassword@192.168.1.60/ha-datacenter/vm/debian/debian c:\vm\sugarcrm.ovf
Error: Locator does not refer to an object

ovftool.exe vi://root:mypassword@192.168.1.60/ha-datacenter/vm/debian/SUGARCRM c:\vm\sugarcrm.ovf
Error: Locator does not refer to an object

ovftool.exe vi://root:mypassword@192.168.1.60/ha-datacenter/SUGARCRM c:\vm\sugarcrm.ovf
Error: Locator does not refer to an object

OVF tools Incompatible library version: libcurl.4.dylib

$
0
0

Tried to run:

$ ./ovftool ~/Documents/Virtual\ Machines1/Win7\ x64.vmwarevm/Windows\ 7\ x64.vmx ~/Documents/Win7\ x64.ova
dyld: Library not loaded: @loader_path/lib/libcurl.4.dylib
  Referenced from: /Applications/VMware OVF Tool/./ovftool
  Reason: Incompatible library version: ovftool requires version 9.0.0 or later, but libcurl.4.dylib provides version 7.0.0
Abort trap: 6

which is a bit confusing since the latest curl version as of this time is 7.55

Deploy ovf from within the datastore help

$
0
0

Hi,

 

I currently am trying to deploy an ovf onto an esxi machine. The ovf is currently located on the destination esxi machine.

 

Here is the command I was trying to use:

 

.\ovftool "https://<ip address>/folder/group1/Win7-5/Win7-5.ovf?dcPath=ha-datacenter&dsName=datastore1" vi://user:password@<ip address>

 

 

group1/Win7-5/Win7-5.ovf is the is the location of the ovf within the datastore.

 

When I try to execute this it has the error:

 

Error: Could not open URL https://<ip address>/folder/group1/Win7-5/Win7-5.ovf?dcPath=ha-datacenter&dsName=datastore1 (response code 404)

 

If i open up the vsphere UI and go through the deploy ovf wizard using

https://<ip address>/folder/group1/Win7-5/Win7-5.ovf?dcPath=ha-datacenter&dsName=datastore1  (same as above)

as the location of the ovf file it works fine.

 

If anyone can help me i would greatly appriciate it. I searched all over and couldnt find an answer anywhere else and couldnt figure it out when looking at the docs. Sorry if this is a repeat post.

 

Ray

ovftool.exe crashes when deploying OVA from Windows 7

$
0
0

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"?>
dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" x
-->   <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{&quot;none&quot;,&quot;local networks&quot;,&quot;public&quot;}">
-->         <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>
gData">1 virtual CPU</rasd:ElementName>
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>
gData">1024 MB of memory</rasd:ElementName>
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>
gData">Ethernet adapter on vmnet</rasd:ElementName>
Data">3</rasd:InstanceID>
-->         <rasd:ResourceSubType>VMXNET3</rasd:ResourceSubType>
-->         <rasd:ResourceType>10</rasd:ResourceType>
-->       </Item>
-->       <Item>
a">0</rasd:Address>
gData">SCSI Controller 0  - lsilogic</rasd:ElementName>
Data">4</rasd:InstanceID>
-->         <rasd:ResourceSubType>lsilogic</rasd:ResourceSubType>
-->         <rasd:ResourceType>6</rasd:ResourceType>
-->       </Item>
-->       <Item>
-->         <rasd:AddressOnParent>0</rasd:AddressOnParent>
gData">Harddisk 1</rasd:ElementName>
-->         <rasd:HostResource>ovf:/disk/system</rasd:HostResource>
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" ?>
--> <!--
-->    Copyright 2008-2011 VMware, Inc.  All rights reserved.
--> -->
--> <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)
-->

OVFtool bug when specifying datastore

$
0
0

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

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

$
0
0

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?

difference between ovf version 0.9 and 1.0?

$
0
0

 

What is the difference between OVF 1.0 and 0.9 version? I would be interested in knowing about the major enchancements made in the newer versions and thereby the advantages of the same.

 

 

 

 

 

Thanks in advance

 

 

How to specify which datastore to use with OVFtool

$
0
0

 

This is driving me crazy! How do you specify which datastore to use when there are multiple?

 

 

I ran exactly the same command on a box that had one datastore and it worked fine (as expected). It created the VM folder in the root of the DS and then pulled across the VM from the OVF. However with multiple it just says no target datstore specified. I've tried a million combinations of ?-ds= with square brackets, without. Sometimes it says not found in inventory. I guess it's looking for a folder. But surely this can't be that hard?

 

 

C:\Program Files\VMware\VMware OVF Tool&gt;ovftool P:\Downloads\PanoManagerVM-2.8.0

-ovf\panomanager.ovf "vi://root@192.168.1.5

Opening OVF source: P:\Downloads\PanoManagerVM-2.8.0-ovf\panomanager.ovf

Warning: No manifest file

Please enter login information for target vi://192.168.1.5/

Username: root

Password: *********

Opening VI target: vi://root@192.168.1.5/

Error: No target datastore specified

Datastores found on target:

  SAN Storage

  storage1

 

 

Converting OVF file using ovftool from VirtualBox produces error "Line 39: Unsupported element 'Caption'" and many more errors

$
0
0

Hi,

 

I would like to convert VirtualBox 3.2.4 virtual machine to VMWare ESX 4.0.

 

In VirtualBox I have exported appliance to 0.9 format and then follow the following tutorial: http://www.ctrip.ufl.edu/howto-convert-virtualbox-to-vmware

 

 

 

 

 

 

When executing command "ovftool my.ovf my.vmx" I got the following error:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Opening OVF source: e:\VMW\my.ovf

Warning: No manifest file

Opening VMX target: e:\VMW\my.vmx

Error:

 

 

 

 

 

  • Line 39: Unsupported element 'Caption'

  • Line 40: Unsupported element 'Description'

  • Line 41: Unsupported element 'InstanceId'

  • Line 42: Unsupported element 'ResourceType'

  • Line 43: Unsupported element 'VirtualQuantity'

  • Line 37: Missing child element 'InstanceID'.

  • Line 37: Missing child element 'ResourceType'.

  • Line 48: Unsupported element 'Caption'

  • Line 49: Unsupported element 'Description'

  • Line 50: Unsupported element 'InstanceId'

  • Line 51: Unsupported element 'ResourceSubType'

  • Line 52: Unsupported element 'ResourceType'

  • Line 45: Missing child element 'InstanceID'.

  • Line 45: Missing child element 'ResourceType'.

  • Line 57: Unsupported element 'Caption'

  • Line 58: Unsupported element 'Description'

  • Line 59: Unsupported element 'InstanceId'

  • Line 60: Unsupported element 'ResourceSubType'

  • Line 61: Unsupported element 'ResourceType'

  • Line 54: Missing child element 'InstanceID'.

  • Line 54: Missing child element 'ResourceType'.

  • Line 65: Unsupported element 'Caption'

  • Line 66: Unsupported element 'Connection'

  • Line 67: Unsupported element 'InstanceId'

  • Line 68: Unsupported element 'ResourceSubType'

  • Line 69: Unsupported element 'ResourceType'

  • Line 63: Missing child element 'InstanceID'.

  • Line 63: Missing child element 'ResourceType'.

  • Line 74: Unsupported element 'Caption'

  • Line 75: Unsupported element 'Description'

  • Line 76: Unsupported element 'InstanceId'

  • Line 77: Unsupported element 'ResourceType'

  • Line 71: Missing child element 'InstanceID'.

  • Line 71: Missing child element 'ResourceType'.

  • Line 81: Unsupported element 'AutomaticAllocation'

  • Line 82: Unsupported element 'Caption'

  • Line 83: Unsupported element 'Description'

  • Line 84: Unsupported element 'InstanceId'

  • Line 85: Unsupported element 'ResourceSubType'

  • Line 86: Unsupported element 'ResourceType'

  • Line 79: Missing child element 'InstanceID'.

  • Line 79: Missing child element 'ResourceType'.

  • Line 90: Unsupported element 'Caption'

  • Line 91: Unsupported element 'Description'

  • Line 92: Unsupported element 'HostResource'

  • Line 93: Unsupported element 'InstanceId'

  • Line 94: Unsupported element 'Parent'

  • Line 95: Unsupported element 'ResourceType'

  • Line 88: Missing child element 'InstanceID'.

  • Line 88: Missing child element 'ResourceType'.

  • Line 99: Unsupported element 'AutomaticAllocation'

  • Line 100: Unsupported element 'Caption'

  • Line 101: Unsupported element 'Description'

  • Line 102: Unsupported element 'InstanceId'

  • Line 103: Unsupported element 'Parent'

  • Line 104: Unsupported element 'ResourceType'

  • Line 97: Missing child element 'InstanceID'.

  • Line 97: Missing child element 'ResourceType'.

 

 

Please see attached ovf file.

 

 

 

What should I do? 

 

 

 

 

 

 

Thanks

Deploy ovf from within the datastore help

$
0
0

Hi,

 

I currently am trying to deploy an ovf onto an esxi machine. The ovf is currently located on the destination esxi machine.

 

Here is the command I was trying to use:

 

.\ovftool "https://<ip address>/folder/group1/Win7-5/Win7-5.ovf?dcPath=ha-datacenter&dsName=datastore1" vi://user:password@<ip address>

 

 

group1/Win7-5/Win7-5.ovf is the is the location of the ovf within the datastore.

 

When I try to execute this it has the error:

 

Error: Could not open URL https://<ip address>/folder/group1/Win7-5/Win7-5.ovf?dcPath=ha-datacenter&dsName=datastore1 (response code 404)

 

If i open up the vsphere UI and go through the deploy ovf wizard using

https://<ip address>/folder/group1/Win7-5/Win7-5.ovf?dcPath=ha-datacenter&dsName=datastore1  (same as above)

as the location of the ovf file it works fine.

 

If anyone can help me i would greatly appriciate it. I searched all over and couldnt find an answer anywhere else and couldnt figure it out when looking at the docs. Sorry if this is a repeat post.

 

Ray

Viewing all 34499 articles
Browse latest View live