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

Can not convert a VMX from vCenter server to a local vmx

$
0
0

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.


How to alter "Power on after deployment" checkbox's default behavior?

$
0
0

Hi All,

I want to alter the "Power on after deployment" checkbox's default behavior, which is part of the last page of deployment. By default this box is not checked, is there a setting I can include in the OVF file to toggle its behavior? Is it even possible? I tried to google it but hard luck!

Poweron.JPG

Thanks in Advance!

- Punit

Does anyone know how to sign ova with timestamp?

$
0
0

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

OVFTool: How to add description while exporting a VM as OVF file

$
0
0

I am using OVFTool to export a VM as an OVF file. I want to know if there is any way to add description during export. I can add EULA and other stuff but i am stuck at description.

Adding description is easy via vSphere client but i OVFTool doesn't seem to have such a provision. Any advice would be greatly helpful.

Regards.

How do I set IPaddress when deloploying an OVF using Vsphere APIs

$
0
0



What is the format of the ovf and what APIs do I use to set the ipaddress of a Vm when deploying it as an ovf?

Cannot convert OVA to VMX using OVFTOOL / Using workstation throws system Error

$
0
0

I am facing an issue. I have an ova file of size 362 MB. I am using OVFTOOL to convert ova to vmx file. I get the below error during conversion,

Also tried with option --chunkSize=200mb, but with no luck. Same error as below.

 

Transfer Failed

Error: System error: (Unknown exception)

Completed with errors.

 

In Vmware workstation 8, i get the below error when i am trying to import the OVA file with the below steps,

a). From the File menu on the VMware Workstation 8 menu bar, select Open.

b).  Browse to the .ovf or .ova file and click Open and Import.

 

I get the below error.  Anyone who could help me with this?

workstation.jpg

OVF Tool memory range error

$
0
0

 

I'm using the ovf tool to convert a virtual appliance to virtual machine format and getting a memory size limitation error based on the OVF source.  The source ovf file specifies 4GB of memory for guest OS:

 

 

Error:

- Virtual machine has 4,096 megabytes of memory, which is outside the range of 4 to 3,600 megabytes supported on the host.  This may be a general limitation of the host software, or specific to the guest OS selected for the virtual machine.

 

 

The work around is to edit the source ovf file and decrease the RAM size to  3 GB and conversion works fine.  But I'm curious why this limitation is occuring.  Is 3,600 MB the maximum virtual memory size supported byVMware workstation or server?

 

 

 

 

 

 

 

 

Locator does not refer to an object:

$
0
0

 

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

 

 


how to deploy ova/ovf into VMware Player?

$
0
0

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,

ovftool - Defining the 'Product', 'Version' and 'Vendor'?

$
0
0

Hi,

 

Am trying to export an ova from a VM using ovftool.  Something along the lines of...

 

ovftool --prop:Version=100 --privateKey=./id_rsa.pem --eula@=./eula.txt vi://root:mypass@myserver.mydomain.com/myVM ./myOVA.ova

 

Everything looks good except that I haven't been able to define the 'Product', 'Version' and 'Vendor'  that appears in the initial dialog when customers deploy the template into a running ESX / vCenter instance.

 

Assume this must be a v common question but have not found how this might be done from the ovftool user guide (http://www.vmware.com/support/developer/ovf/ovf301/ovftool-301-userguide.pdf) or the VMware communities.  Closest I've found is http://communities.vmware.com/thread/328504 which indicates that defining a vCenter vApp allow configurable properties to be set.

 

Is there any way to define these parameters via ovftool?  If not, is there a way to hack the .ova manually to define them?

 

Thanks in advance,

Frank.

Large OVF imports into vCloud Director 1.0.1 fail, smaller imports succeed

$
0
0

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.

Problem running OVF Tool 3.0.1 on Mac (Locale initialization failed)

$
0
0

There is unfortunately a bug in OVF Tool 3.0.1 on Mac that causes OVF Tool not to work if the current directory is not the same as the installation directory! For example, if you have made a symbolic link to OVF Tool or have OVF Tool in the path, you will see the following error:

  > ovftool
  Error: Locale initialization failed.
  Completed with errors
If you execute it directly from the installation directory, it would work:
  > cd /Applications/VMware\ OVF\ Tool/
  > ovftool
  Error: No source or target specified. Try 'ovftool --help' for more options.
  Completed with errors
The workaround is to:
  1. Save the attached script (ovftool.txt)  and store it in your home directory (~/).
  2. Perform the following commands in a terminal window:
  >cd /Applications/VMware\ OVF\ Tool/
  >sudo mv ovftool ovftool.bin
  >sudo cp ~/ovftool.txt ovftool
  >sudo chmod a+x ovftool
We are working on an OVF Tool 3.0.2 release where this will be fixed.
/renes

difference between ovf version 0.9 and 1.0?

$
0
0

 

What is the difference between OVF 1.0 and 0.9 version? I would be interested in knowing about the major enchancements made in the newer versions and thereby the advantages of the same.

 

 

 

 

 

Thanks in advance

 

 

Failure on disk import

$
0
0

Hello, I'm having some trouble getting both the vSphere Client and ovftool to

import my OVF's.  When using the vSphere Client, I successfully walk through

the wizard to "Deploy OVF Template", I click Finish on the final wizard screen

and progress dialog pops up.  It counts up to 100% complete while showing

"Deploying disk 1 of 1..." and then always fails with the following error

displayed on a popup window:

 

"Failed to deploy OVF package: The remote server returned an error: (500)

Internal Server Error"

 

I then tried using ovftool, to convert my OVF to VMX format.  Similarly, the

"Disk Progress" percentage counts up to 100% and then errors with:

 

Opening OVF source: stout-1-x86_64.ovf

Warning: No manifest file

Opening VMX target: stout-out/

Target: stout-out/stout-1-x86_64/stout-1-x86_64.vmx

Disk Transfer Failed           

Error: Failed to open source disk: stout-1-x86_64.vmdk

 

In both cases, it seems the problem is with my disk file, which is a

stream optimized VMDK.  Just to check, I verified that I was able to import

this exact same disk file built into an OVF 0.9 using Virtual Infrastructure

Client 2.5.0.  So, I'm at a loss as to what the problem may be.  Do you have

to build the stream optimized vmdk any differently?  Any other suggestions on

how I may be able to debug this further?

 

Thanks for any help,

James Slagle

 

OVF Tool HELP!!!!!!

$
0
0

 

i installed the OVF tool yesterday, i followed every step in the "OVF Tool User Guide" and when i open the comman prompt and typed "ovftool" its work  but when i retype again i get an error saying "no source of target "specified".  Also, i dont really understand how to use it, what exactly does typing "ovftool <source locator> <destination locator>" do?  what exactly do u type in the brackets?  And can some please post an easy guide on how to make an OVF file.  THANK YOU

 

 


ovftool coredumped

$
0
0

 

I use ovftool to deploy an appliance to a host (esx 3.5i). after disk copy done, I got an error message and the tool core dumped.

 

 

What does the message means ?

 

 

Thanks in advance.

 

 

 

 

 

Opening OVF source: /home/luger_lee/tmpout/VMware-VIPerl-Toolkit-1.6.0-104313-Appliance/VMware-RCLI-3.5-U2-Appliance.ovf

Warning: No manifest file

Opening VI target: vi://root@alaska/

Target: vi://alaska/

 

Disk progress: 1%

...

Disk progress: 99%

Disk Transfer Failed           

Error: Unable to get NFC ticket for target disk

Error: Failed to clean up after failure. Reason: vim.fault.NotAuthenticated

terminate called after throwing an instance of 'Vim::Fault::NotAuthenticated::Exception'

 

  what():  vim.fault.NotAuthenticated

Terminate process signal received - aborting operation/usr/bin/ovftool: line 23: 32361 Aborted                 (core dumped) $OVFTOOL_BIN "$@"

 

 

 

OVF entry to embed .vmx data?

$
0
0

 

Hi,

 

 

Does anyone know of a way to add .vmx key/value pairs from an OVF?

 

 

As in: foo="bar"

 

 

 

 

 

As it stands I would have my newly imported OVF use VMware API (with host' ESX credentials) modify the .vmx file after boot but those changes aren't preserved unless the VM is powered down. Catch 22!

 

 

 

 

 

VMware's ovftool doesn't install/work on VMware vMA 4.0?

$
0
0

Tried to install 64bit ovftool on VMware vMA 4.0 today and it failed to install or yield any useful information:

 

[vi-admin@scofield]$ ./VMware-ovftool-installer-1.0.0-166674-lin.x86_64.sh

VMware OVF Tool installer script
Copyright VMware 2009
.........extracting archive........

Checksum validation failed for archive.
(If you use FTP, make sure to set it to binary mode)

 

As far as I can tell, the binary is actually included in the install script though I'm not sure why 'FTP' is being referenced here unless VMware is expecting to download the actual source? I would hope that since vMA is a VMware virtual appliance that it should support any "VMwae" utilities but from what I've seen in the past with VDDK and VIX, that is not always and generally is not the case.

 

Can anyone comment on or know how to get it to install?

 

Thanks for your time

 

 

 

 

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

Twitter: @lamw

vGhetto Script Repository

Getting Started with the vMA (tips/tricks)

Getting Started with the vSphere SDK for Perl

VMware Code Central - Scripts/Sample code for Developers and Administrators

VMware Developer Community

 

http://engineering.ucsb.edu/~duonglt/vmware/vexpert_silver_icon.jpg

 

If you find this information useful, please award points for "correct" or "helpful".

OVFTOOL Deployment - syntax determination problem

$
0
0

 

I have a vApp which consists of an OVF file and three VMDK files, one for each VM.  All VMDK files are co-resident with the OVF file. 

 

 

NOTE:  This vApp deploys successfully from vSphere 4.0 client.

 

I am attempting to deploy the vApp using OVFTOOL.  However, I am unable to derive the proper OVFTOOL syntax. 

 

  • Potentially pertinent facts:  Datacenter is clustered; OVF to be deployed has multiple VMs, OVFTOOL version is 1.0.0

 

 

Using the command below, when the vApp already exists, produces a "specified parameter" error as shown.

 

  • ovftool --acceptAllEulas --datastore=(dsid) 
           --net:"HOST-A Network 1"=VMNET2 --net:"HOST-B Network 1"=VMNET2 --net:"HOST-C Network 1"=VMNET2 
           appliance.ovf vi://(VSERVER)/(DATACENTER)/vm/(FOLDER)/(vAPP)

 

Opening OVF source: appliance.ovf
Warning: No manifest file
Please enter login information for target vi://VSERVER/
Username: DOMAIN
USER
Password: *********
Opening VI target: vi://DOMAIN
USER@VSERVER/DATACENTER/vm/FOLDER/vAPP
Error:
- A specified parameter was not correct.
folder

Using the same command as above, when the vApp does not already exist, produces a "does not refer to an object" error.

 

Error: Locator does not refer to an object: vi://DOMAIN
USER@VSERVER/DATACENTER/vm/FOLDER/vAPP

 

However, if I change the command to deploy to a target "folder", an error message appears, indicating a "wrong kind of object" error:

 

  • ovftool --acceptAllEulas --datastore=(dsid)
           --net:"HOST-A Network 1"=VMNET2 --net:"HOST-B Network 1"=VMNET2 --net:"HOST-C Network 1"=VMNET2
           appliance.ovf vi://(VSERVER)/(DATACENTER)/vm/(FOLDER)

 

<snip>
Error: Found wrong kind of object (Folder)

 

 

Assuming my first syntax is the correct one, the " - A specified parameter was not correct. (/p) folder" message throws me.  It seems inappropriate to the command.

 

I've tried several variations but no luck so far. I'm not seeing anything specific in the documentation as far as special handling in the cases of deployment of multiple-VM OVFs or deployment to clusters.  I tried looking at the commands with the debug parameters "--X:logToConsole --X:logLevel=trivial" , but saw nothing immediately helpful (to me anyway :P).

 

 

 

What should my expected target be for this... vApp or folder?  Should the vApp exist, or not?  Am I missing something else entirely?

 

 

thanks for any input,

 

 

=chuck

 

 

OVF tool fails to convert compressed OVF file to vmx

$
0
0

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?

Viewing all 34499 articles
Browse latest View live


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