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

Create OVF/OVA via ovftool

$
0
0

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


ovftool fails with curl error: couldn't connect to server

$
0
0

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

getting following error while login

$
0
0

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

getting following error while calling OVF tool.

$
0
0

C:\Program Files\VMware\VMware OVF Tool>ovftool  E:\vmdk2008\Windows2008\Windows
2008P2V.vmx   vcloud://suresh:suresh1@10.137.90.73:443?org=Org1-Cloud1&vapp=myVA
PPTets&catalog=cat2&vappTemplate=junk&vdc=OrgVDC-org1-Cloud1
Opening VMX source: E:\vmdk2008\Windows2008\Windows2008P2V.vmx
Error: Missing vappTemplate or vapp key in locator
Completed with errors
'vapp' is not recognized as an internal or external command,
operable program or batch file.
'catalog' is not recognized as an internal or external command,
operable program or batch file.
'vappTemplate' is not recognized as an internal or external command,
operable program or batch file.
'vdc' is not recognized as an internal or external command,
operable program or batch file.

C:\Program Files\VMware\VMware OVF Tool>

The OVF descriptor file could not be parsed.

$
0
0

Hi All,

 

    I have just exported an vApp using ovf from my vCenter v4u2. When I try to import into Vmware Workstation 7.1(running on Window 7 Ent 64bit) I get the following error message "The OVF descriptor file could not be parsed."  I have attached the log.

 

 

Cheers!

Attempting to Sign an OVF Package

$
0
0

Right now I'm trying to sign an OVF Package and I receive these sets of errors when I do:

 

C:\Program Files\VMware\VMware OVF Tool>ovftool.exe --privateKey= "C:\Documents
and Settings\jhamilto\My Documents\Downloads\bin\myself.pem" C:\tmp\test2.ovf
Opening OVF source: C:\Documents and Settings\jhamilto\My Documents\Downloads\bi
n\myself.pem
Warning: No manifest file
Error:
- Line 1: Could not parse the document: 'syntax error'.
Completed with errors

 

C:\Program Files\VMware\VMware OVF Tool>ovftool.exe --privateKey= "C:\Documents
and Settings\jhamilto\My Documents\Downloads\bin\myself.pem" \C:\tmp\test2.ovf \
C:\tmp\SignedTest.ovf
Error: Unexpected option: \C:\tmp\SignedTest.ovf
Completed with errors

 

C:\Program Files\VMware\VMware OVF Tool>ovftool.exe --privateKey="C:\Documents a
nd Settings\jhamilto\My Documents\Downloads\bin\myself.pem" \C:\tmp\test2.ovf \C
:\tmp\SignedTest.ovf
Error: Failed to open file:
Completed with errors

 

Do I have a syntax error or is there something else that I am missing?

ovftool : Specify Hardware version during a conversion ?

$
0
0



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

Unable to deploy an ovf to datacenter folder

$
0
0



We have a specific folder used for certain vm's that I need to deploy to.


As an example I can view the current list of vm's with:


ovftool vi://myadmin:mypass@ourvcenter/DATACENTER/vm/myvms

Error: Found wrong kind of object (Folder). Possible completions are:
vmname1
vmname2
vmname3
 


Now let’s say I want to import an ovf to myvms/vmname4 I get a "Locator does not refer to an object" error.


ovftool --datastore=mydatastore --network=mynetwork vi://myadmin:mypass@ourvcenter/DATACENTER/vm/myvms/vmname4 newvm.ovf

Opening VI source: vi://myadmin:mypass@ourvcenter/DATACENTER/vm/myvms/vmname4
Error: Locator does not refer to an object: vi://myadmin:mypass@ourvcenter/DATACENTER/vm/myvms/vmname4
Completed with errors


I have tried variations of using —name and —vmfolder and changing the vi: path without success.


I can import directly to esxi and to host through vcenter but we are then having to go back into vcenter to move these vms to the correct folder.


Is there a way to get this into the "right" place up front?


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?

$
0
0

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.)

OVA to VMX -> Target location inconsistent

$
0
0

Hello everyone,

When I run the command:

ovftool /Users/me/AutoDeployLocal/my.ova /tmp/AutoDeployVm/autodeploy.vmx

The program inconsistently gives me two possibilities. Either this:

Opening OVA source: /Users/me/AutoDeployLocal/my.ova

The manifest validates

Opening VMX target: /tmp/AutoDeployVm/autodeploy.vmx

Writing VMX file: /tmp/AutoDeployVm/autodeploy.vmwarevm/autodeploy.vmx

Or this will happen at (seemingly) random:

Opening OVA source: /Users/me/AutoDeployLocal/my.ova

The manifest validates

Opening VMX target: /tmp/AutoDeployVm/autodeploy.vmx

Writing VMX file: /tmp/AutoDeployVm/autodeploy.vmx

I want the second outcome to happen 100% of the time, as I am running this in a script, which relies on the VMX file being in the location I specify to the OVF Tool. Is there any reason why this is not happening?

I am running this on OSX 10.10.5 and OVF Tool is v4.10, the latest I could find. 

Thanks in advance for any help!

Unable to parse xml element 'Envelope'

$
0
0

 

I used ovftool (1.0 running in a RHEL 5.2 VM) to create an ovf of a powered off RHEL 5.1 VM.  All was successful and I can probe the OVF without issue.  However, when I try to import it as a virtual appliance using Virtual Center 2.5 Update 5 I receive:

 

 

An error occurred while parsing the OVF descriptor:  Unable to parse xml element 'Envelope'

 

I've attached the ovf file.

 

Any ideas?

 

 

Cannot Import OVF into ESXi 3.5

$
0
0

 

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.

 

 

getting following error while calling OVF tool.

$
0
0

C:\Program Files\VMware\VMware OVF Tool>ovftool  E:\vmdk2008\Windows2008\Windows
2008P2V.vmx   vcloud://suresh:suresh1@10.137.90.73:443?org=Org1-Cloud1&vapp=myVA
PPTets&catalog=cat2&vappTemplate=junk&vdc=OrgVDC-org1-Cloud1
Opening VMX source: E:\vmdk2008\Windows2008\Windows2008P2V.vmx
Error: Missing vappTemplate or vapp key in locator
Completed with errors
'vapp' is not recognized as an internal or external command,
operable program or batch file.
'catalog' is not recognized as an internal or external command,
operable program or batch file.
'vappTemplate' is not recognized as an internal or external command,
operable program or batch file.
'vdc' is not recognized as an internal or external command,
operable program or batch file.

C:\Program Files\VMware\VMware OVF Tool>

Properties lost when deployed a VM and exported it to OVF

$
0
0

Hi,

 

I have built a VM, using VMware Studio in OVA format. I defined some custom OVF environment properties in it.

After I built the VM, I opened the .OVF file to see the property values are appeared correctly. They look like the below

 

<ProductSection ovf:required="false">
      <Info>VM ISV branding information</Info>
      <Product>xxxxxxxxx</Product>
      <Vendor> xxxxxxxxx , Inc.</Vendor>
      <Version>x.x.x.x</Version>
      <FullVersion>x.x.x.x alpha</FullVersion>

</ProductSection>

 

I deployed this OVF to a ESXi 4.0 server. Later exported the same VM to OVF format using OVFTool, using the command line

 

ovftool.exe vi://root:xxxxxxxxxxx@IP/vmname  "d:\Virtual Machines\imported-OVF\newVM.ovf"

 

After the export, I opened the newVM.OVF file and found that the properties (like product, vendor, version etc.) are not retained.

 

What could be the issue. Please suggest.

 

--Hemanth

ovftool ova -> vmx conversion fails - Connection error during download

$
0
0



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:




getting error (core dumped) "$OVFTOOL_BIN" "$@" while using ovftool from jenkins instance

$
0
0

Hi,

 

When i try to configure deployment job from Jenkins, i am getting

/usr/bin/ovftool: line 23: 19723 Segmentation fault  (core dumped) "$OVFTOOL_BIN" "$@"

error in command line, Not sure how to find solution, i was able to use the same command from my local system directly from my user account.

This error i am getting after message

Opening OVF source: myfile.ovf

 

thanks in advance,

vduggirala

ovftool vCloudTemplate does nothing

$
0
0


Hi, 


We currently are building a vmx using packer via either vmware workstation or vmware fusion, depending on whther it's running on ubuntu or a mac. When the vmx is either converted into an OVF, it maintains the network + nat i.e. connectiontype=nat etc. Despite passing in --vCloudTemplate when uploading it to vcloud, the template once uploaded still seems to maintain the network so when we provision. the "nat" is transposed into being an actual network name. 


ovftool --version


VMware ovftool 4.0.0 (build-2060496)


 


Is the version i am using. I am not sure if when generating the ovf via ovftool with --vCloudTemplate whether the ovf generated should transform or whether it's purely just when you pass to vcloud:// protocol  If the former, then i can test locally without uploading it. 


 


Even using --nw:none causes it to want to find a network called "none". 


 


This is becoming very inflexible for managing different images in different ways, if there isn't a consistent way of creating an image suitable for vcloud director. Is there something we should be doing, we don't want to be editing the vmx directly, however, that's basically what it is going to boil down to. 


 


Any help gladly welcome. 

ovftool --version



VMware ovftool 4.0.0 (build-2060496)


Problems trying to convert a .iso to .ova file

$
0
0

I have a .iso image from which I want to create a .ova , But everytime I run into a problem

 

Error: Curl error: Couldn't connect to server

Completed with errors

 

Here is the command I used,

 

ovftool vi://user:master/@14.23.12.34:443/rt4/www/html/imgs/qweTER7.3/.tyRani/NEWCFT/CFT-NEW-5.23.23.iso /rt4/www/html/tmp_ova/CFT-NEW-5.23.23.ova

 

Not sure whats wrong with this command, I don't have special character in my password or username

 

please note that 14.23.12.34 is a linux machine and both source and target are in same machine and Im executing ovftool command in same linux machine.

 

Thank you

Mac

Static IP given during OVA deployment doesnt take effect post deployment

$
0
0

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,

Unsupported element 'Property'

$
0
0

 

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'

 

 

 

 

 

 

 

 

Viewing all 34499 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>