Hi fellows,

                       I had deployed a virtual ESXi host on a physical ESXi and then I created an OVA file of that virtual host and then was trying to deploy the OVA after changing the IP, subnet mask and gateway properties of the OVA file. But when i used the probe mode to have a look at the class ID and other properties, I found them to be missing.

C:\Users\abhinav.srivastava>ovftool test1.ovf

OVF version:   1.0

VirtualApp:    false

Name:          vhost1

Download Size:  283.32 MB

Deployment Sizes:

  Flat disks:   25.00 GB

  Sparse disks: 325.44 MB

Networks:

  Name:        VM Network

  Description: The VM Network network

Virtual Machines:

  Name:               vhost1

  Operating System:   otherlinux64guest

  Virtual Hardware:

    Families:         vmx-08

    Number of CPUs:   2

    Cores per socket: 1

    Memory:           2.18 GB

    Disks:

      Index:          0

      Instance ID:    8

      Capacity:       25.00 GB

      Disk Types:     SCSI-lsilogic

    NICs:

      Adapter Type:   E1000

      Connection:     VM Network

So right now I am not able to change the OVA properties and deploy the virtual host. I need to do this as I want this step automated. Does anybody know why am I not able to see the properties of the OVA file. Am I going wrong somewhere. Kindly help!!

Thanks,

Abhinav

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.

Hi All.

VMware OVF Tool 2.1.0 is now ready for download.

Go to the download link on the frontpage.

Eske

hello, I am stuck.  Any help is much appreciated.

I am simply trying to export an OVF template from a vm (.vmx) in vCenter 4.1.0 using the OVF Tool.

The vm is located here:

<vcenter>/<datacenter>/vm/Build Server/sles11-sp1-x8664/yoshi

I can probe the object like this:

[root@r2d2 bin]# ovftool vi://<user>:<password>@helios.blue.roguewave.com/Corvallis/vm/Build\ Server/sles11-sp1-x8664/yoshi

OVF version:   1.0

VirtualApp:    false

Name:          yoshi

Download Size:     Unknown

Deployment Sizes:

  Flat disks:     80.00 GB

  Sparse disks:   Unknown

Networks:

  Name:        CVO VM Network

  Description: The CVO VM Network network

Virtual Hardware:

  Family:       vmx-07

  Disk Types:   SCSI-lsilogic

[root@r2d2 bin]# ovftool vi://<user>:<password>@helios.blue.roguewave.com/Corvallis/vm/Build\ Server/sles11-sp1-x8664/yoshi vi://<user>:<password>@helios.blue.roguewave.com/Corvallis/vm/templates/ovf-templates/yoshi.ovf

Opening VI source: vi://bluoma@helios.blue.roguewave.com:443/Corvallis/vm/Build%20Server/sles11-sp1-x8664/yoshi

Error: Locator does not refer to an object: vi://bluoma@helios.blue.roguewave.com:443/Corvallis/vm/templates/ovf-templates/yoshi.ovf

Completed with errors

Can someone help identify the correct target locator?

I have also tried the following host path:

[root@r2d2 bin]# ovftool vi://<user>:<password>@helios.blue.roguewave.com/Corvallis/vm/Build\ Server/sles11-sp1-x8664/yoshi vi://<user>:<password>@helios.blue.roguewave.com/Corvallis/host/R\&D

Opening VI source: vi://bluoma@helios.blue.roguewave.com:443/Corvallis/vm/Build%20Server/sles11-sp1-x8664/yoshi

Opening VI target: vi://bluoma@helios.blue.roguewave.com:443/Corvallis/host/R&D

Error: No target datastore specified. Possible completions:

  DespinaLS

  DevVMs

  NFS Install

  VM template backup

  dominator-nfs-install

  nfs-ds1

  puffinSanMedia

  skillet-ds1

  skillet-ds2

Completed with errors

[root@r2d2 bin]# ovftool vi://<user>:<password>@helios.blue.roguewave.com/Corvallis/vm/Build\ Server/sles11-sp1-x8664/yoshi vi://<user>:<password>@helios.blue.roguewave.com/Corvallis/host/R\&D/skillet-ds2

Opening VI source: vi://bluoma@helios.blue.roguewave.com:443/Corvallis/vm/Build%20Server/sles11-sp1-x8664/yoshi

Error: Locator does not refer to an object: vi://bluoma@helios.blue.roguewave.com:443/Corvallis/host/R&D/skillet-ds2

Completed with errors

[root@r2d2 bin]# ovftool vi://<user>:<password>@helios.blue.roguewave.com/Corvallis/vm/Build\ Server/sles11-sp1-x8664/yoshi vi://<user>:<password>@helios.blue.roguewave.com/Corvallis/host/R\&D?ds=[skillet-ds2]

Opening VI source: vi://bluoma@helios.blue.roguewave.com:443/Corvallis/vm/Build%20Server/sles11-sp1-x8664/yoshi

Error: Datacenter object not found

Completed with errors

Hi All,

I'm unable to get ovftool to export a vm from my server that has spaces in the path to the vmx file.

Any help would be appreciated.  Thanks!

On the server:

~ # vim-cmd vmsvc/getallvms

Vmid Name             File Guest                              OS Version     Annotation

112  ar-vm            [sata3] har_vm/har_vm.vmx                rhel5_64Guest  vmx-07

16   eluefin          [sata1] eluefin/eluefin.vmx              rhel4_64Guest  vmx-07

32   igloo (RH5)      [sata0] igloo (RH5)/igloo (RH5).vmx      rhel5_64Guest  vmx-07           

When I try to export "igloo (RH5)":

C:\OVF_Tool>ovftool.exe  --compress=9 --X:logToConsole "vi://root:doublesecret@hoo.lgc.com/ha-datacenter?ds=[sata0] igloo (RH5)/igloo (RH5).vmx" F:\igloo

2013-05-23T12:55:47.089-05:00 [02908 verbose 'Default'] [SSL_DB] Using C:\Users\owjune\AppData\Roaming\VMware\ovftool_SSLDB as SSL DB

2013-05-23T12:55:47.105-05:00 [02908 verbose 'Default'] Subscribing to signal: 2 (SIGINT)

2013-05-23T12:55:47.105-05:00 [02908 verbose 'Default'] Subscribing to signal: 4 (SIGILL)

2013-05-23T12:55:47.120-05:00 [02908 verbose 'Default'] Subscribing to signal: 22 (SIGABRT)

2013-05-23T12:55:47.120-05:00 [02908 verbose 'Default'] Subscribing to signal: 8 (SIGFPE)

2013-05-23T12:55:47.120-05:00 [02908 verbose 'Default'] Subscribing to signal: 15 (SIGTERM)

2013-05-23T12:55:47.120-05:00 [02908 verbose 'Default'] OvfTool Version: VMware ovftool 3.0.1 (build-801290)

2013-05-23T12:55:47.120-05:00 [02908 verbose 'Default'] Using home directory: C:\Users\owjune\AppData\Roaming\VMware\ovftool.cfg

2013-05-23T12:55:47.120-05:00 [02908 verbose 'Default'] OvfTool Environment:

--> /X:httpTimeout = "0"

--> /X:imageReadSize = "262144"

--> /X:logToConsole = "true"

--> /X:maxNumberOfTermSignals = "5"

--> /X:maxRedirects = "256"

--> /X:maximalDeltaConfSize = "8"

--> /X:maximalDeltaTreeSize = "6"

--> /X:progressSmoothing = "60"

--> /X:useMacNaming = "false"

--> /X:vCloudEnableGuestCustomization = "false"

--> /X:vCloudKeepTemplate = "true"

--> /X:vCloudTimeout = "3600"

--> /X:vimSessionTimeout = "600"

--> /authdPortSource = "902"

--> /authdPortTarget = "902"

--> /compress = "9"

--> /fencedMode = "bridged"

--> /prgPath = "C:\OVF_Tool"

--> /source = "vi://root:doublesecret@hoo.lgc.com/ha-datacenter?ds=[sata0] igloo (RH5)/igloo (RH5).vmx"

--> /target = "F:\igloo"

--> /vCloudTemplate = "false"

-->

2013-05-23T12:55:47.152-05:00 [02908 verbose 'Default'] Done initializing libs

2013-05-23T12:55:47.152-05:00 [02908 verbose 'Default'] Determining source

2013-05-23T12:55:47.152-05:00 [02908 verbose 'Default'] Determining target

2013-05-23T12:55:47.152-05:00 [02908 verbose 'HttpConnectionPool-000000'] HttpConnectionPoolImpl created. maxPoolConnections = 20; idleTimeout = 900000000; maxOpenConnections = 20; maxConnectionAge = 0

2013-05-23T12:55:47.152-05:00 [02908 verbose 'Default'] Getting http page: https://hoo.lgc.com/sdk/vimServiceVersions.xml

2013-05-23T12:55:47.152-05:00 [02908 verbose 'Default'] Proxy host

2013-05-23T12:55:47.167-05:00 [00756 info 'Default'] Thread attached

2013-05-23T12:55:47.183-05:00 [03816 verbose 'Default'] CURL: header data removed

2013-05-23T12:55:47.183-05:00 [03816 verbose 'Default'] CURL: header data removed

2013-05-23T12:55:47.183-05:00 [03816 verbose 'Default'] CURL: header data removed

2013-05-23T12:55:47.183-05:00 [03816 verbose 'Default'] CURL: header data removed

2013-05-23T12:55:47.183-05:00 [03816 verbose 'Default'] CURL: header data removed

2013-05-23T12:55:47.183-05:00 [03816 verbose 'Default'] CURL: header data removed

2013-05-23T12:55:47.183-05:00 [03816 verbose 'Default'] CURL: header data removed

2013-05-23T12:55:47.183-05:00 [03816 verbose 'Default'] CURL: header data removed

2013-05-23T12:55:47.183-05:00 [02908 verbose 'Default'] [ViConnection] Using vim API version: 4.1

2013-05-23T12:55:47.183-05:00 [02168 info 'Default'] Thread attached

2013-05-23T12:55:47.183-05:00 [03780 info 'Default'] Thread attached

2013-05-23T12:55:47.198-05:00 [03920 info 'Default'] Thread attached

2013-05-23T12:55:47.198-05:00 [03192 info 'Default'] Thread attached

2013-05-23T12:55:47.198-05:00 [02752 info 'Default'] Thread attached

2013-05-23T12:55:47.245-05:00 [02908 verbose 'HttpConnectionPool-000001'] HttpConnectionPoolImpl created. maxPoolConnections = 1; idleTimeout = 900000000; maxOpenConnections = 1; maxConnectionAge = 0

2013-05-23T12:55:47.261-05:00 [02908 verbose 'Default'] Keeping VI session alive

Opening VI source: vi://root@hoo.lgc.com:443/ha-datacenter

2013-05-23T12:55:47.432-05:00 [02908 verbose 'Default'] Backtrace:

--> backtrace[00] rip 000007fef141722a

--> backtrace[01] rip 000007fef12df578

--> backtrace[02] rip 000007fef12e078e

--> backtrace[03] rip 000007fef129266b

--> backtrace[04] rip 000007feeeb0d3d1

--> backtrace[05] rip 000007fef0f703b8

--> backtrace[06] rip 000007fef0f707e9

--> backtrace[07] rip 000007fef0f8efbe

--> backtrace[08] rip 000007feee8b024e

--> backtrace[09] rip 000000013f83824d

--> backtrace[10] rip 000000013f7aca0d

--> backtrace[11] rip 000000013f7ad04a

--> backtrace[12] rip 000000013fa3a426

--> backtrace[13] rip 0000000076b5b1bd

--> backtrace[14] rip 0000000076d66861

-->

Error: vim.fault.FileNotFound

Completed with errors

From virtualmachine i have exported .ovf file from the following website http://www.techrepublic.com/blog/windows-and-office/how-do-i-convert-virtualbox-files-to-work-with-vmware-workstation/#.

and i recieved the following error in cmd prompt.

can anyone please help me to understand error line 84 and prove me solution .

........................................................................................

Error:

- Line 84: Could not parse the document: 'mismatched tag'

Warning:

- No manifest file found.

Completed with errors.

---------------------------------------------------------------------------------------

Steps followed:

Step 1: Export your virtual machine

The first step is to export your virtual machine from VirtualBox.

Step 2: Editing your .ovf file

The file you need to edit will be the .ovf file that serves as the descriptor for your virtual machine. You MUST open this in a text editor. Do NOT open it in a word processor as this will add extra characters to the file, which will render it unreadable by either VirtualBox or VMWare. The first section you need to edit is the format section. Look for a line of code (near the top) that contains this phrase:

ovf:format=

What follows that section needs to be changed to:

"http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized"

The next edit (in the same file) is the Virtual SystemType, and it must be one of the following:

<vssd:VirtualSystemType>vmx-07</vssd:VirtualSystemType> (for a esx 4.0)

<vssd:VirtualSystemType>vmx-04</vssd:VirtualSystemType> (for esx 3.5.x and 4.0 hosts)

Believe it or not, the next item to edit is the rsad for the sound card. The section will look similar to:

<Item>

<rasd:Caption>sound</rasd:Caption>

<rasd:Description>Sound Card</rasd:Description>

<rasd:InstanceId>6</rasd:InstanceId>

<rasd:ResourceType>35</rasd:ResourceType>

<rasd:ResourceSubType>ensoniq1371</rasd:ResourceSubType>

<rasd:AutomaticAllocation>false</rasd:AutomaticAllocation>

<rasd:AddressOnParent>3</rasd:AddressOnParent>

</Item>

To the above section, add the following after the first <Item> tag:

<Item ovf:required="false">

Step 3: Using the OVF tool

This step requires you to download and install the VMWare OVF Tool (you will have to log in first). The OVF tool is command-line only, and it will convert your newly prepped .ovf file into a .vmx that VMWare can use. To do this, follow these steps:

• Click Start | Run.
• Type cmd.
• In the command window, change to the directory you installed the OVF Tool into and then issue the command:ovftool appliance.ovf new_appliance.vmx(Where appliance.ovf is the name of the appliance you exported from VirtualBox and new_appliance.vmx is the name you want to give the new virtual appliance. Depending on the size of your virtual appliance, this could take a while.)

Hi,

I have about a dozen OVF's I'm importing into ESXi 5.5 via the Linux ovftool client. The VM's range from 5gb to 30gb and include VMDK files. I am still improrting the first one and it is taking a crazy long time. The CPU and Memory usage stays under 1% on the client, and getting up to 5% has taken me the better part of an hour. Network speeds don't seem to be an issue, I'm wired and can SCP files from the same source and destination at 30MB/s. Is there something I'm missing? please help

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

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 am creating ova file using VMware OVF tool .

And I want to use public Code Signing Certificate like published by Globalsign or Verisign.

But current OVF tool doucment is not introduce how to sign with timestamp.

So, when public cert is expired, just ova file is also expired.

This is problem.

Ex: Using vsphere client call deploying OVF Template, then display signing is expired.

Document

https://www.vmware.com/support/developer/ovf/ovf350/ovftool-350-userguide.pdf

Deploy an OVF Template

http://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic=/com.vmware.vsphere.vmadmin.doc_41/vsp_vm_guide/working_with_ovf_templates/t_import_a_virtual_appliance.html

Will signed code still be valid after the Code Signing Certificate expires?

The digital signature on code will not expire, when a timestamping service is used. A time stamp shows the validity of the certificate at the time the code was signed. Unless you’re adding additional code to your application, a new signature will not need to be applied even if the certificate used to initially sign the code expires. GlobalSign Code Signing Certificates include a time stamp feature.

https://www.globalsign.com/support/faq/objectfaq.php

Hi,


I have ovftool version (4.0.0).I am trying to create an ovf  of a VM with extra config parameters. How do i specify the exportFlags command line option to allows the config parameters to translate from the VM to the ovf ? The documentation says I need to specify a extraconfig vSphere source .


This works fine : ovftool --allowAllExtraConfig  --extraConfig:ethernet1.coalescingScheme=disabled --extraConfig:ethernet0.coalescingScheme=disabled


but this doesn't : ovftool --exportFlags=extraconfig 


I don't want to add the key:value in the command line , rather pick up these from the VM  I am using to create the ovf.


Is there something that I am missing out ?


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

"A line such as ide1:0.fileName = "/dev/cdrom" or a line such as ide1:0.fileName = "/dev/scd0" wil cause the ovftool to abort with the following message:

- Device 'cdrom1' has a backing type that is not supported. This is a general limitation of the virtual machine's virtual hardware version of the selected host.

By contrast if the vmx file cdrom setting is set to ide0:1.autodetect = "TRUE"  this error is not received.

We are not sure if this can be overcome with other tool options, although we have not seen anything that looks promising.

Additionally, many of our settings are not carried over to the ovf format, they are simply dropped, such as the isolation.* settings.

Also, the original VM consisted of several disk files (vmdk).  The ovftool created one vmdk file from this VM.  We will require creating vmware persistent and vmware non-persistent disks for some of our VMs.

We are concerned that the ovftool may lose such disk information. This would be a show stopper for us, and would require us find an alternative solution for transporting VMs.

We would like for VMware to advise us of possible workarounds and any recommendations for these issues."

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 have a VM running on ESX 4.0 which using pvscsi disks. I tried to export it into an OVF package but I got an error message said that 'pvscsi' is unsupported virtual hardware device.

I have two questions:

1. Is there any other options I have except to modify the VM to use 'lsilogic'?

2. Will ovftool support pvscsi in the future?

Thanks in advance!

I've been trying to import the ovf-based Oracle storage simulator to ESX4. Also tried importing to Workstation when that failed.

No luck. Not with integrated converter, not with standalone converter, not with ovftool. Changing/removing lines in .ovf file brings me a bit further but still no cigar.

The process stalls at different points, but typically I get an error about unknown OS or unsupported hardware, sometimes a parse error with no additional info.

Has anybody got this working?

The simulator is a virtual-box based Solaris appliance.

Ole Thomsen

I need to write a script to remotely shotdown a guest VM, export it to .ova format an restart it.

Is there any sample I can start from?

Regards

marius

Hi, I'm having a problem with ovftool. I'm running ovftool against a ESXi host with a trial license. The command shows the ovf properties that I've set on the commandline, but once I'm on the virtual machine, the ovf environment is not present at all. If I do the deployment through the vSphere client, it works perfectly, same OVA file.

I see the output from ovftool:

--> /prop/ip0 = "192.168.43.159"

--> /prop/ip1 = "192.168.43.185"

but also get the warnings:

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!