I have a compressed OVF file generated by OVF tool using "compress" option. However, I cannot convert the generated ovf file back to vmx. When I run OVF tool to perform conversion, it says "Disk Transfer Failed" and "Error: Failed to open source disk: disk1.vmdk.gz" .Any ideas how I should proceed with this?
↧
OVF tool fails to convert compressed OVF file to vmx
↧
VMworld Copenhagen.
Hi All
Just wanted to drop a line that we, the OVF and OVF tool team, will be at VMworld Copenhagen (october 12-14, 2010). If you want to meet up, ask questions, etc so please drop me a line and I will see what I can do.
Thanks,
Eske
↧
↧
ovftool sanfs://..../linux.iso was not found
Hi,
I'm trying to convert VM into ovf. But ovftool fails with the message:
./ovftool --powerOffSource vi://administrator:xxxxx@host/?ip=192.168.1.22 myovf.ovf
Opening VI source: vi://administrator@host/
Powering off VM: 0593498732-VM_Name
Error: File sanfs://vmfs_uuid:3c3693e8-f77a642a-1910-5c6bdcb26d3a/packages/4.1.0/vmtools/linux.iso was not found
Could you please help me with the issue above?
Thanks,
↧
OVFTool cannot set property successfully
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?
↧
Lost network connection data during the OVF conversion process
Hi all,
My application converts an OVF format VM into VMX format, run a program to patch/insert file
into the vmdk file, re-convert the VMX format back to OVF format. During the process, the
original network connection changes from "VM Networks" to "bridge". I am trying to understand
if there is a solution to retain the original network connection setting.
Setup:
Virtual Center 4.1.0
OVF tool 2.1.0
A linux based on CentOS 5.5
Procedure:
1. Use the tool "Export OVF Template" on Virtual Center to export a Linux VM (other 32bit Linux).
2. Use command "ovftool sourcerfile1.ovf targetfile.vmx"
3. Use command "ovftool targetfile.vmk /tmp/test/sourcefile2.ovf"
When the VM was exported by VC (after step 1), the ovf file contains the following NetworkSection:
<NetworkSection>
<Info>The list of logical networks</Info>
<Network ovf:name="VM Network">
<Description>The VM Network network</Description>
</Network>
</NetworkSection>
When the OVF got converted from VMX (after step 3), the ovf file contains the following NetworkSection:
<NetworkSection>
<Info>The list of logical networks</Info>
<Network ovf:name="bridged">
<Description>The bridged network</Description>
</Network>
</NetworkSection>
I did have an older setup where it uses VC 3.5 and OVF tool 1.0. When I performed the same procedure,
the network section is unchanged in the final ovf file. When I compared the .vmx file between the
old and new procedure, they are almost identical, with the exception of number of CPU parameter.
So, what am I doing wrong here?
Any help is greatly appreciated.
Thanks.
↧
↧
A quick note on using a domain login for ovftool
I didn't find this documented anywhere else, so I wanted to note that, if you want to use windows domain accounts in the authentication process for ovftool without specifying it interactively, you must specify the \ character using %5c, as in:
ovftool --acceptAllEulas --net:nat=mgmt-net --datastore=nfs-1 --name=Ubuntu-test Ubuntu.vmwarevm/Ubuntu.vmx vi://WINDOMAIN%5cAdministrator:password@10.10.10.100/dcName/host/cluster-name
↧
Trying to create an OVF file
To whom may help,
I’m currently trying to get an ovf file created from the command line. At the moment I am using ovftools, I’ve tried multiple variations on getting this to work but maybe I’m just not getting something. Any help would be great:
Here is the input and out put that I’m getting:
C:\Program Files\VMware\VMware OVF Tool>ovftool.exe vi://****:*********@10.*******/vmfs/volumes/4ee778f7-8fdOaf38-***********************/"MSP Virtual Machine #2"/"MS
P Virtual Machine #2" C:\tmp\test.ovf
Opening VI source: vi://****@10.*******:443/vmfs/volumes/4ee778f7-8fd************************/MSP Virtual Machine
Error: Locator does not refer to an object: vi://root@10.********:443ha-datacente
r/host/localhost./Resources/vmfs/volumes/4ee778f7-8fdOaf38-6589-842b2b47ee18/MSP
Virtual Machine
Completed with errors
Thanks
↧
OVFTool 2.1.0 with Active Directory Question (vSphere crashes)
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
↧
Maximum (realistic) sizes for OVA/OVF format and export?
Hi- has anyone hit any problems with exporting large (e.g. > 1TB) VMs in OVA/OVF format?
I realise that you can split the files generated, but leaving aside any issues to do with the file-system on which the files reside, are there any inherent gotchas with the export mechanism or the file format that would mean it's not a good idea to rely on this for exporting large VMs...?
Thanks!
↧
↧
Problem with converting vmworkstation vm(.vmx) to ovf by ovftool
Ovftool in VMworkstation·7.0 used to convet .vmx to ovf
display error:
ovftool version 2.0
Any help with this is super appreciated!!
Thanks,
↧
ovftool deploy failing with "Network connection was lost"
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
↧
How to add addition Hard disk space for the created VM in ESXi server using Ovftool command
Can anyone help me out on "how to add additional Hard Disk and Ethernet Adapter for VM created in an ESXi server using ovftool.exe commandline.
↧
Specifying ?ip=[ip] in locator results in "Locator does not refer to an object" error
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:
| tcp | 0 | 1 192.168.0.105:46167 | 172.17.0.10:443 | SYN_SENT |
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:
To convert an OVF package to a vCenter Server, use the following syntax:
> ovftool /ovfs/my_vapp.ovf vi://username:pass@my_vc_server/?ip=10.20.30.40
(Uses a managed ESXi host’s ip address.)
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.
↧
↧
Can not convert a VMX from vCenter server to a local vmx
I am trying to convent a vmx within vCenter server to a local vmx, i am trying with:
ovftool.exe "vi://user:password@my_vCenterserver/may_datacenter?ds=[my_datastore] my_vm/my_vm.vmx" C:\ovfs\my_vm.vmx
as the tool user guide Page 35, session "Converting a VM on ESXi or vCenter to an OVF" introduces.
But I got prompt as:
Opening VI source: vi://my_vCenterserver:443/
Error: Datacenter object not found
Completed with errors
But, i am sure the my_datacenter is INDEED exists.
Any suggestions what should i do?
Additional:
I even can NOT probe my VMX like this:
ovftool.exe vi://user:password@my_vCenterserver/my_datacenter/my_vm/my_vm.vmx
with Error:
Error: Locator does not refer to an object: vi://user:password@my_vCenterserver/my_datacenter/my_vm/my_vm.vmx
But I am very sure 'my_vmx' locates indeed there.
↧
No support for the virtual hardware device type '7'
Hello
When using ovftool:
# ovftool file.ova file
Opening OVA source: file.ova
The manifest validates
Opening VMX target: file
Error: OVF Package is not supported by target:
- Line 60: OVF hardware element 'ResourceType' with instance ID '3': No support for the virtual hardware device type '7'.
Completed with errors
When trying to deploy ova via vCenter i got similar error:
Details: Line 60: OVF hardware element Resource Type with instance ID 3. No support for the virtual hardware device type 7.
When looking at the xml file i can see that device type 7 is related to the following:
<rasd:Address>1</rasd:Address>
<rasd:Description>VIRTIO Controller</rasd:Description>
<rasd:ElementName>VIRTIOController 0</rasd:ElementName>
<rasd:InstanceID>3</rasd:InstanceID>
<rasd:ResourceType>7</rasd:ResourceType>
How can i make it working ?
Is there any way to exclude that element from ova file ?
Thanks,
Michal
↧
OVF Tool - VmWare File Systems and OVA Format conversion question
Greetings! Question in regards to OVFtool and how storage file systems are handled in VMWare.
I am using the OVFTool version 2.1.0 (Tried 3.5.0 with not much avail) to export multiple VMDK files or disks in a Virtual Machine (versions 7 and 8) to a multiple OVA files for each - at moment tool allows for consolidation of disks in a partitioned state into ONE OVA - Does anyone know of a work around or undocumented switch which can be used to create X # of virtual disks to X # of OVAs for import into another system?
Copying VMDKs is not a viable option in this case as want to remain with OVA standards.
Thank you!
↧
I HAVE a query can we install vSphere ESXi 4.1 U3 and ESXi 5.5 in HA cluster vCenter 5.5.
I HAVE a query can we install vSphere ESXi 4.1 U3 and ESXi 5.5 in HA cluster vCenter 5.5.
↧
↧
OVFTool - vmware tools ip assignment on esxi free hypervisor.
Hi.
I ran into a problem when deploying an ova using ovftool with pre-installed vmware-tools. Once the appliance is booted up the IP address isn't dynamically assigned to it even though the appliance has vmware-tools pre-installed. That only happens on the ESXi free hypervisor and it works fine on the licesed version of the ESXi. I was under impression that ESXi free hypervisor provides full functionality for vmware-tools? If that's not the case, is there any other way of dynamically assigning an IP address to newly created ova?
Thanks.
↧
VMware ThinApp
Hello,
when I created a portable app with thinapp while 60 days-testing phase and the 60 days are over - can I still use the created app?
Best regards
Nils
↧
Linux OVFTOOL 3.5.0 - Errored with "Lost Connection"
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
↧