Hi,
I am trying to deploy OVA using ovftool. I see the option --network and --net available for selecting the network by name, though I was not able to find a way to assign a static IP in the ovftool command itself. Something like --ip0=10.10.10.10. Is there a way we can do this? From UI when we deploy an OVA, we have provision to provide IP, Gateway, Netmask and DNS.
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?
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,
CJ
I'm getting wildly different results while importing large OVF file into vCloud Director 1.0.1 via the ovftool than when performing the upload of the same OVF via the native JAva tool within vCloud Director itself. AS long as the file transfer compeltes through the vCD Java tool, the file is importing into vCenter correctly, and then being correctly registered within vCD.
The OVF I'm working with is 68.2 GB in size.
Below is a sanatized version of my command line and the output from the tool:
ovftool --net:"dvportgroup-48=company-Services_Internal" E:\OlioWebtest\oliowebtest.ovf "vcloud://user:password@testvcd1.company.com:443/?org=company_Services&vapp=OlioWebTest&vdc=company_Services_ALLO_vDC01&catalog=test"
Opening OVF source: E:\OlioWebtest\oliowebtest.ovf
The manifest validates
Warning: File is not referred in the manifest: oliowebtest.ovf
Opening vCloud target: vcloud://user@testvcd1.company.com:443/
Waiting for task on server .done
Deploying to vCloud: vcloud://user@testvcd1.company.com:443/
Disk Transfer Completed
Error: Invalid response from server
Completed with errors
Looking in the vCD GUI logs for the organization, I see the descriptor being processed, and the process for finalizing the upload completing, but the vApp is never added to the catalog. If I look in vCenter, I can find the VM on a valdi datastore for the org vDC and the correct resource pool in the proper state for a catalog vApp. The error "Error: Invalid response from server" is displayed immediately upon completion of the data transfer.
If I move the VM to the root of the datacenter, I can import the VM as a vApp and copy it to the caalog with no issue.
I tested with a much smaller OVF (1.3 GB), and received exactly the behavior I expected.
ovftool --net:"none=company-Services_Internal" E:\suse\descriptor.ovf "vcloud://user:password@testvcd1.company.com:443/?org=company_Services&vapp=SUSE32&vdc=company_Services_ALLO_vDC01&catalog=test"
Opening OVF source: E:\suse\descriptor.ovf
Warning: No manifest file
Opening vCloud target: vcloud://user@testvcd1.company.com:443/
Waiting for task on server .done
Deploying to vCloud: vcloud://user@testvcd1.company.com:443/
Disk Transfer Completed
Waiting for task on server ...................done
Waiting for task on server .......................................done
Waiting for task on server ..done
Completed successfully
Looking at the succesful transfer, I see an additonal action logged in the GUI logs for the organization. After the finalization record, there is a "Create virtual application" event logged on the smaller transfer that is never logged on the larger transfer.
The only item I can think of from a vCloud Director standpoint is that that vCD logon sesion timeout has expired on the large transfer long before the additional tasks are issued to vCD resulting in the invalid response. Is this the case, or is something else going on?
When looking at the vcloud-container-info.log file on the cells doing the processing for the succesful imports, I see a whole string of commands being executed in the current logged on user context.
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
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'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"/>
Hi,
i have some OVA files that when i try to deploy them, shows the following error :
Unable to access file :
C:\user\Administrator\Desktop\Backup\new-ova\ubuntu.18-file1.iso
End Of OVA file reached while looking for : ubuntu.18-file1.iso
I use VMWare ESXi 5.5
how can i resolved this issue ?
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>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
Hi,
trying to convert a "SUSEstudio" generated vmdk/vmx to our VI.
I have:
SLE_11.1JeOSPHR.x86_64-0.0.3.vmdk
SLE_11.1JeOSPHR.x86_64-0.0.3.vmx
christian@chrisw:/srv/ISO/JeOS/SLE_11.1JeOSPHR-0.0.3> ovftool SLE_11.1JeOSPHR.x86_64-0.0.3.vmx
Opening VMX source: SLE_11.1JeOSPHR.x86_64-0.0.3.vmx
OVF version: 1.0
Name: SLE_11.1JeOSPHR.x86_64-0.0.3
Download Size: Unknown
Deployment Sizes:
Flat disks: 4.04 GB
Sparse disks: Unknown
Networks:
Name: bridged
Description: The bridged network
Virtual Hardware:
Family: vmx-04
Disk Types: SCSI-lsilogic
Completed successfully
#####
When I try to convert it to vi (to correct datastore) I'm getting the mentioned error:
so what is the correct syntax ??
christian@chrisw:~/srv/ISO/JeOS/SLE_11.1JeOSPHR-0.0.3> ovftool -ds=CX300-OTC-02 -dm=thick SLE_11.1JeOSPHR.x86_64-0.0.3.vmx vi://i000156@vc.icw.int/DC%20OTC
Opening VMX source: SLE_11.1JeOSPHR.x86_64-0.0.3.vmx
Please enter login information for target vi://vc.icw.int/
Username: i000156
Password: ********
Error: Locator does not refer to an object: vi://i000156@vc.icw.int/DC%20OTC
DataCenter="DC OTC"
DataSource="CX300-OTC-2"
THX
Chris
hello.
I create a ova file from my ESXi 5.0.0 with ovftool 2.1.0-467744, then I deploy this ova file into ESXi 5.0.0 is success and work well.
But I can't deploy the same ova file into VMWare Player with ovftool 2.1.0-467744 installed. Why?
Anybody has any idea? Thanks.
Best Regards,
I have an OVA that have built and deployed via VIC many times successfully. I am now trying to automate the deployment via the OVFTOOL. However, I keep seeing this "transfer failed" message. Is there some way to enable a more verbose output?
Here is my current command/output:
ovftool --acceptAllEulas --datastore=dsRTPPOC1 --network="VM Network" z:\Jazzsm\IBM_Jazz_for_Service_Management___v1_1___Sprint_23.ova vi://admin:password@rtpvcpoc1.tivlab.raleigh.ibm.com/ZoneM/host/ZoneM/rtpesxpoc1.tivlab.raleigh.ibm.com/
Opening OVA source: z:\Jazzsm\IBM_Jazz_for_Service_Management___v1_1___Sprint_23.ova
Opening VI target: vi://admin@rtpvcpoc1.tivlab.raleigh.ibm.com:443/ZoneM/host/ZoneM/rtpesxpoc1.tivlab.raleigh.ibm.com/
Warning:
- The specified operating system identifier 'RedHat Enterprise Linux Server 6.2' (id: 80) is not supported on the selected host. It will be mapped to the following OS identifier: 'Other Linux (64-bit)'.
Deploying to VI: vi://labadmin@rtpvcpoc1.tivlab.raleigh.ibm.com:443/ZoneM/host/ZoneM/rtpesxpoc1.tivlab.raleigh.ibm.com/
Transfer Failed
Error: System error: (Unknown exception)
Completed with errors
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
So long story short I'm building a self deployment install using a Kickstart script that after the install uses wget to copyy the OVA files to the local data store and then deploys the OVAs, i have the script figured out however i can't seem to get ovftool installed on ESXi 5.5, everytime i try to run it i get the following error
env: can't execute 'bash': No such file or directory
this happens even after making the file executable, here's the whole command
~ # cd /tmp
/tmp # mkdir ovf
/tmp # cd ovf/
/tmp/ovf # wget http://10.10.10.4/OVA/VMware-ovftool-3.5.0-1274719-lin.x86_64.bundle
Connecting to 10.10.10.4 (10.10.10.4:80)
VMware-ovftool-3.5.0 100% |*******************************| 40125k 0:00:00 ETA
/tmp/ovf # chmod +x VMware-ovftool-3.5.0-1274719-lin.x86_64.bundle
/tmp/ovf # ./VMware-ovftool-3.5.0-1274719-lin.x86_64.bundle
env: can't execute 'bash': No such file or directory
/tmp/ovf # sh ./VMware-ovftool-3.5.0-1274719-lin.x86_64.bundle
env: can't execute 'bash': No such file or directory
/tmp/ovf # /bin/sh ./VMware-ovftool-3.5.0-1274719-lin.x86_64.bundle
env: can't execute 'bash': No such file or directory
I'm trying to export a VM using ovftool on linux.
ovftool --X:logFile=upload1.log --X:logLevel=verbose --noSSLVerify vi://[user]:[pass]@[ESXi IP]:[port]/my_datacenter/vm/my_vm_folder/my_vm_name /tmp/test.OVF and i get the following error in the log:
2016-11-11T11:40:30.287+02:00 verbose -[7F5C76E3F7C0] [Originator@6876 sub=Default] Getting version of the VI host :
[ESXi IP]2016-11-11T11:40:30.287+02:00 verbose -[7F5C76E3F7C0] [Originator@6876 sub=Default] Initializing new curl session
2016-11-11T11:40:30.288+02:00 verbose -[7F5C76E3F7C0] [Originator@6876 sub=Default] WebRequest set basic http authorization, username : [user]
2016-11-11T11:40:30.288+02:00 verbose -[7F5C76E3F7C0] [Originator@6876 sub=Default] Getting http page: https://
[ESXi IP]/sdk/vimServiceVersions.xml2016-11-11T11:40:30.299+02:00 verbose -[7F5C6F1CF700] [Originator@6876 sub=Default] Curl_perform error code 35 (SSL connect error)
2016-11-11T11:40:30.299+02:00 verbose -[7F5C76E3F7C0] [Originator@6876 sub=Default] CURL error buffer: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number
2016-11-11T11:40:30.299+02:00 verbose -[7F5C76E3F7C0] [Originator@6876 sub=Default] Curl session torn down
2016-11-11T11:40:30.300+02:00 verbose -[7F5C76E3F7C0] [Originator@6876 sub=Default] Backtrace:
-->
--> [backtrace begin] product: VMware Workstation, version: e.x.p, build: build-2459827, tag: -
--> backtrace[00] libvmacore.so[0x003D9C74]: Vmacore::System::Stacktrace::CaptureWork(unsigned int)
--> backtrace[01] libvmacore.so[0x001DBF37]: Vmacore::System::SystemFactoryImpl::CreateQuickBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&)
--> backtrace[02] libvmacore.so[0x0018481D]: Vmacore::Throwable::Throwable(std::string const&)
--> backtrace[03] ovftool.bin[0x0020DFB3]
--> backtrace[04] ovftool.bin[0x00248E5D]
--> backtrace[05] ovftool.bin[0x0024C5C9]
--> backtrace[06] ovftool.bin[0x00295BC4]
--> backtrace[07] ovftool.bin[0x0029714C]
--> backtrace[08] ovftool.bin[0x00299744]
--> backtrace[09] ovftool.bin[0x001EC2B4]
--> backtrace[10] ovftool.bin[0x001EEB04]
--> backtrace[11] libc.so.6[0x00021F45]
--> backtrace[12] ovftool.bin[0x001626B9]
--> [backtrace end]
-->
You'll note that the command is run with --noSSLVerify.
So I checked the SSL versions on both the client and the ESX server using:
openssl ciphers -v | awk '{print $2}' | sort | uniq and both returned:
SSLv3
TLSv1.2
no difference between the two...
looked around for this curl error and while it is fairly well known I haven't seen a solution applicable to my situation.
Any ideas?
4.2.0 is bundled into the current build of Fusion10:
ovftool --version
VMware ovftool 4.2.0 (build-6230482)
This version has a busted --allowAllExtraConfig flag, so some VMs will not export to OVA, instead you get a slew of errors like this one:
- Line -1: Unsupported value 'disk.EnableUUID' for attribute 'key' on element 'ExtraConfig'.
Hello all,
I am having a problem with the ovftool.
Here's what i did.
1)I created a VM running CentOS.
2)These are the 3 files that i got.
Test.vmx
Test.vmdk (Descriptor File)
# Disk DescriptorFile
version=1
CID=5046e880
parentCID=ffffffff
createType="vmfsPreallocated"
# Extent description
RW 83886080 VMFS "Test-flat.vmdk" 0
# The Disk Data Base
#DDB
ddb.virtualHWVersion = "4"
ddb.geometry.cylinders = "83220"
ddb.geometry.heads = "16"
ddb.geometry.sectors = "63"
ddb.adapterType = "lsilogic"
Test-flat.vmdk
3) This is the command that i ran
ovftool "Test.vmx" "Test_New.ova"
Please help!
Thank you
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 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'
Hi,
is it possible to include the nvram-file in the OVF-File oder how to tranport BIOS-Settings with OVF.
regards.
Hans-Peter
TAM, EMEA-Central
VMware
I am attempting to perform and document a roundtrip Export and Import using ovftool.
I performed the export as follows:
bowser:/tmp/ovfTool # mount 10.68.x.xx:/export/images /mnt/ovfExport bowser:/tmp/ovfTool # mkdir /mnt/ovfExport/ovfs bowser:/tmp/ovfTool # mkdir /mnt/ovfExport/ovfs/wario-sles11-sp1-x8664 bowser:/tmp/ovfTool # ovftool vi://bluoma:******@helios.blue.roguewave.com/Corvallis/vm/Build\ Server/sles11-sp1-x8664/wario /mnt/ovfExport/ovfs/wario-sles11-sp1-x8664/wario.ovf Opening VI source: vi://bluoma@helios.blue.roguewave.com:443/Corvallis/vm/Build%20Server/sles11-sp1-x8664/wario Opening OVF target: /mnt/ovfExport/ovfs/wario-sles11-sp1-x8664/wario.ovf Writing OVF package: /mnt/ovfExport/ovfs/wario-sles11-sp1-x8664/wario.ovf Disk Transfer Completed Completed successfully
Now I am attempting to import/deploy the ovf:
Any ideas why the SHA1 digest did not verify?
vCenter: 4.1.0
ESXi host: 4.1.0
Thanks,
Bryan