Hi!
I'm trying to to deploy a OVF/OVA file into my vCenter but I'm getting a error message, pls help me.
"Line 61: No space left for device '5' on parent controller '4'."
(Tested to deploy other templates and it worked fine)
Any idea anyone?
Hi!
I'm trying to to deploy a OVF/OVA file into my vCenter but I'm getting a error message, pls help me.
"Line 61: No space left for device '5' on parent controller '4'."
(Tested to deploy other templates and it worked fine)
Any idea anyone?
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.
Hi Everyone,
I was trying to deploy a VM using the ovftool, I thought I would use the properties which are thrown from a "probe" of the OVA file.
ovftool http://server/files/builds/vpas/6.0.0/latest/vPAS-installer.ova
Properties:
ClassId: vami
Key: gateway
InstanceId vPAS
Category: Networking Properties
Label: Default Gateway
Type: string
Description: The default gateway address for this VM. Leave blank if DHCP is
desired.
ClassId: vami
Key: DNS
InstanceId vPAS
Category: Networking Properties
Label: DNS
Type: string
Description: The domain name servers for this VM (comma separated). Leave
blank if DHCP is desired.
ClassId: vami
Key: ip0
InstanceId vPAS
Category: Networking Properties
Label: Network 1 IP Address
Type: string
Description: The IP address for this interface. Leave blank if DHCP is
desired.
ClassId: vami
Key: netmask0
InstanceId vPAS
Category: Networking Properties
Label: Network 1 Netmask
Type: string
After having made sure that such properties exists from the probe, I tried to use them to give the VM a static IP post deployment, automatically.
ovftool --datastore="31_datastore" --acceptAllEulas --ipAllocationPolicy=fixedPolicy --name="vPAS_31_1" --powerOn --prop:ip0="172.16.121.115" --prop:netmask0="255.255.0.0" --prop:DNS="172.16.1.10" --prop:gateway="172.16.1.1" http://server/vpas/6.0.0/latest/vPAS-installer.ova vi://root:password@172.16.121.31/
Opening OVA source: http://server/files/builds/vpas/6.0.0/latest/vPAS-installer.ova
The manifest validates
Opening VI target: vi://root@172.16.121.31:443/
Deploying to VI: vi://root@172.16.121.31:443/
Transfer Completed
Powering on VM: vPAS_31_1
Warning:
- OVF property with key: 'DNS' does not exists.
- OVF property with key: 'gateway' does not exists.
- OVF property with key: 'ip0' does not exists.
- OVF property with key: 'netmask0' does not exists.
Completed successfully
Can someone please explain me whether this is a common problem ( from VMware ) or something I am doing wrong?
Thanks,
Hi all
I am running
ovftool -tt=vmx --lax --X:logFile=debug.log --X:logLevel=verbose ../backup/DataStax_Sandbox_1_0_0_for_VMWare.ova /u01/vmware
And it is failing with the error: Connection error during download
I am guessing that ovftool is attempting to d/l the xsd's for the vmdk schema, and the provider of the ova is using outdated xsd's
Here is the debug from the conversion showing the schema:
<Envelope vmw:buildId="build-1274719" xmlns="http://schemas.dmtf.org/ovf/envelope/1" xmlns:cim="http://schemas.dmtf.org/wbem/wscim/1/common" xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1" xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData" xmlns:vmw="http://www.vmware.com/schema/ovf" xmlns:vssd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
What should the provider be using?
I have attached the full debug file.
C:\Program Files\VMware\VMware OVF Tool>ovftool --machineOutput --acceptAllEula
s --verifyOnly E:\vmdk2008\Windows2008\Windows2008P2V.vmx vcloud://suresh:suresh1@10.137.90.73:443?vapp=my_test1_tempst1_temp
ERROR
+ <Errors>
+ <Error>
+ <Type>ovftool.system.error</Type>
+ <LocalizedMsg>
+ Incorrect login: vcloud://10.137.90.73/
+ </LocalizedMsg>
+ </Error>
+ </Errors>
RESULT
+ ERROR
But my login credentials are correct(VCD user details). Do I need to do any thing specifically
Hello
I've looked around in the forums, but couldn't find a resolution to this problem. I'm using ovftool (the latest version - 2.1.0) to deploy an ova consisting of 3 VMs to an ESXi 4.1 server, via a vcenter. I see frequent stalls in the data transfer from the vcenter to the server (did a packet capture), and ovftool frequently (but not always) gives up at some random point through the transfer, complaining that it encountered an unexpected end of stream.
Here's the commandline I'm using:
ovftool --name=foo --X:logToConsole=True --X:logLevel="verbose" --diskMode=thin --net:"VM Network"="VM Network" --vmFolder=bar --skipManifestCheck myova.ova vi://user:pass@localhost/my_dc/host/my_host/Resources/my_pool
Here's a log snippet if it might help:
2012-09-11T07:13:01.767-07:00 [07668 verbose 'Default'] [ViConnection] Using vim API version: 5.0
2012-09-11T07:13:01.891-07:00 [07384 warning 'Libs'] Encountered other certificate error: 27
2012-09-11T07:13:01.891-07:00 [07384 warning 'Libs'] Encountered other certificate error: 27
2012-09-11T07:13:01.938-07:00 [07668 verbose 'HttpConnectionPool'] HttpConnectionPoolImpl created. maxPoolConnections = 1; idleTimeout = 900000000; maxOpenConnections = 1; maxConnectionAge = 0
2012-09-11T07:13:01.954-07:00 [07668 verbose 'Default'] Keeping VI session alive
Opening VI target: vi://user:pass@localhost:443/my_dc/host/my_host/Resources/my_pool
2012-09-11T07:13:02.016-07:00 [07384 warning 'Libs'] Encountered other certificate error: 27
2012-09-11T07:13:02.016-07:00 [07384 warning 'Libs'] Encountered other certificate error: 27
Deploying to VI: vi://user:pass@localhost:443/my_dc/host/my_host/Resources/my_pool
2012-09-11T07:13:10.471-07:00 [07668 verbose 'Default'] Using file size as progress measure
Disk progress: 02012-09-11T07:13:10.518-07:00 [07668 verbose 'Default'] Opening disk target /nut4/client/VirtualLsiLogicController0:0
2012-09-11T07:13:10.534-07:00 [07384 verbose 'Default'] CURL: => Send header POST /nfc/52d3abc1-5c67-3e19-1db6-88303c597203/disk-0.vmdk HTTP/1.1
--> User-Agent: VMware-client/4.0.0 (ovfTool; libcurl)
--> Host: 1.1.1.2
--> Accept: */*
--> Transfer-Encoding: chunked
--> Content-Type: application/x-vnd.vmware-streamVmdk
-->
-->
2012-09-11T07:13:35.010-07:00 [07384 verbose 'Default'] Curl_perform error code 55 (Failed sending data to the peer)
Disk Transfer Failed
Error: Internal error: Unexpected end of stream
Interestingly, if I use the vsphere client to deploy the ova, it goes through quicker and I haven't seen it fail (I need to use ovftool to automate deployment).
Any help would be greatly appreciated.
Thanks
Using a seperate process (python-vm-builder), I am building an ESX/ESXi compliant image that I have confirmed can be uploaded, imported and started in Workstation, ESX 3.0, ESXi 3.5 and even Server 2.0+.
I'm trying to go into the next step now, and convert this ESXi Image into a single OVF archive for even easier deployments.
Using the latest OVF Tool I have successfully created the new .ovf and zipped it up inside a tar.gz'd. On my Windows box, I then extract it (using WinRAR), then using 'Import' in VIC try to import it. When I select the OVF and click next it then throws the below error:
An error occurred while parsing the OVF descriptor
Unable to parse XML element 'Envelope'
What am I doing wrong?
I have attached both the original VMX and the new OVF.
Please help!
Thank you.
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.
(Easy) Question… Regarding the use of global configuration file (ovftool.cfg) and local configuration file with OVFTOOL.
Syntax is given only for comments and parameters which are name-value pairs, e.g. datastore=DATASTORE-NAME.
For a single parameter without a corresponding value, e.g. –acceptAllEulas, should these parameters be expressly set to TRUE?
Or can they simply be present (no equals sign)? Both styles seem to work properly for --acceptAllEulas option.
Example: which of the following CFG files shows the expected syntax? Or are both acceptable?
acceptAllEulas=true
disableVerification=true
quiet=true
datastore=S123D0001
ipAllocationPolicy=fixed
or
acceptAllEulas
disableVerification
quiet
datastore=S123D0001
ipAllocationPolicy=fixed
(Yeah, I know - this question probably is a gimme. Just curious if there's anything to trip over here. )
=cjs
Message was edited by: cjstaples-emc -- sorry, original formatting garbage
Is there a way to map network devices that are both associated with "VM Network" in the ova to different networks on the target? The ova contains only "VM Network", but I would like to put one interface on "NET_A" and one on "NET_B".
Hello
I installed ovftool on SLES 11 SP1 but when I try to use it....says Error: Locale Initialization Failed =(
I am trying to create an OVF from a vm in vsphere - I'm running ovftool on a linux machine, and using the following syntax (I got this from the ovftool users guide):
ovftool username@myvcenter.aaa.com/"datacenter name"/vm/vmname /local/path/tostoreit/vnname.ovf
It prompts for a password, I enter the password, and it comes back with:
Opening VI source: vi://username@myvcenter.aaa.com/datacenter name/vmname
Error: Locator does not refer to an object:vi://username@myvcenter.aaa.com/datacenter name/vmname
Incidentally, I get the exact same error when I try using the mac version of ovftool, and the windows version.
Please help - I know this should work. I have no idea what I'm doing wrong, but I have to get this working pretty fast.
Thank you!!
Hi,
I am getting following error message while checking ovf file using --schemaValidate option.
C:\Program Files\VMware\VMware OVF Tool>ovftool.exe --schemaValidate "w:\Virtual Appliance\testVA.ovf"
Opening OVF source: w:\Virtual Appliance\testVA.ovf
Error:
- Line 5: Could not parse the document: 'w:\Virtual Appliance\testVA.ovf: Datatype error: Type:InvalidDatatypeValueException, Message:Value 'testVA-disk1.vmdk' is NOT a valid URI . (column 122)'.
Could you please let me know is this a serious error? Because I am able to deploy my VM in vCenter Server 4.0 amd also able to boot the VM.
Need to know if I continue with this error then where I will get problem? i.e. Deployment in other VMware products/Booting in other VMware products etc..
Hi all,
I have a problem in deploying Suse OVF image, built using Susestudio.
while deploying the OVF, there's a default SuSE Eula which comes up.
using --acceptAllEulas doesn't seem to accept it automatically.
This Eula blocks my automation work.
Did any of you face this issue ??
Any help/workaround would be appreciated.
Thanks in advance.
Hello,
I am seeking guidance on automation\customization of an OVA deployment.
Looking to use an OVA due to it's compression ability which is favorable when needing to transfer a VMWare virtual machine from Host to Host for deployment at different location across a WAN. In the past, we have created a VM template and provided customization file for deployment but the size of the template was too large for transfer across the WAN....so we would have to ship on seperate media.
I am looking to achieve the same end result of deployment of a vm template but through the deployment of the OVA template.
Here is where I am at so far:
1. Create the VM (in this case Windows XP SP3)
2. Export the VM to OVA Template.
3. Deploy OVA Template
All of the above works without any problem. However, during deployment of the OVA, I would like to prompt the end user to input computer name, Fixed IP information or DHCP, domain to join, etc. Additionally, I would like sysprep to run.
I have read the guide and numerous articles on the OVF descriptors, but not quite sure where or how to input these prompts so they appear during the OVA deployment. Additionally, if I sysprep the vm before exporting to OVA, how can I get sysprep and the input from the end user deployment to work hand in hand.
Thanks in advance for any guidance or tutorial reference you can supply to help me understand OVA deployment of a single vm and how to configure custom settings during deployment with sysprep running.
Hi All.
VMware OVF Tool 2.1.0 is now ready for download.
Go to the download link on the frontpage.
Eske
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
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-
Was giving an SSL error, now giving a connecgt error. No firewall involved. I wonder Windows does not have ssh, so, why is vConverter using ssh.
Any help much appreciated.
Hi,
I have an OVF file that refeneces a disk image from a webserver, e.g.:
<File ovf:href="http://myserver/cdrom.iso" ovf:id="file1"/>
When i try to deploy this OVF to a vSphere server, it fails at the disk transfer stage... it looks to me like ovftool is treating it like a local file:
$ ovftool my.ovf vi://root:@172.26.0.172
Opening OVF source: my.ovf
Warning: No manifest file
Opening VI target: vi://root@172.26.0.172:443/
Deploying to VI: vi://root@172.26.0.172:443/
Disk Transfer Failed
Error: Failed to open file: cdrom.iso
Here is the output with logging enabled:
When an OVF is deployed from a local file, does it mean the references also need to be local? I had a quick read of the OVF spec and it seems like file reference can be anywhere... local, relative, http or https... any ideas?