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

Deployment from OVA format.

$
0
0

Hi,

I am deploying a VM using a OVA format. The  size of OVA format is 60 GB. Currently free space on my datastore is 388 GB.

At the time of selecting Disk Format type if shows me in red that the disk size required is 1 TB therefore you cannot select THICK provisioning.

Therefore, i selected THIN provisiong. It THIN provisioing i am showed that Estimated Disk Usage is 112 GB which is less than the free space available.

But even after selecting THIN proviosing at the time of deployment it throws an error that it cannot create disk as the size of disk is larger than the maximum specified limit. 

My block size is of 1 MB.


Not able to ipaddress/gateway/netmask field configuration for deployed ovf in VM using ovftool

$
0
0

Hi,

 

I want to config IP-address/gateway/netmask to the deployed ovf virtual machine and i getting the following info when i run ovftool.exe

Can anyone help me out in configure ipaddress fields.

Or is there any other way to do it.

 

 

C:\Program Files\VMware\VMware OVF Tool>ovftool.exe --powerOn --diskMode=thin --
ipProtocol=IPv4 --acceptAllEulas --name=pravin --network="VM Network" --prop:IpA
ddress="10.110.208.16" --prop:SubnetMask="255.255.252.0" --prop:Dns="10.110.188.
5" --prop:DefaultGateway="10.110.208.1" --datastore="datastore1" "C:\Sharing\v35
9\ovf_filename.ovf" " vi://root:password@10.110.209.214"
Opening OVF source: //:@WIN-1VPBHEDRE5M:80\Sharing\v359\ovf_filename.ovf
Opening VI target: vi://root@10.110.209.214:443/
Deploying to VI: vi://root@10.110.209.214:443/
Transfer Completed
Powering on VM: pravin
Warning:
- No manifest file found.
- OVF property with key: 'DefaultGateway' does not exists.
- OVF property with key: 'Dns' does not exists.
- OVF property with key: 'IpAddress' does not exists.
- OVF property with key: 'SubnetMask' does not exists.
- No manifest entry found for: 'system.vmdk'.
Completed successfully

Deploy OVF Template problems

$
0
0

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?

Not able use the ipaddress and netmask properties from ovf using ovftool

$
0
0

OVF Command option:

ovftool.exe "--acceptAllEulas=true" "--name=Robo_Naren_vApp_Temp" "--datastore=fiddleback-esx2:storage1" "-dm=thin" "--network=VM-Network" "C:/appliance-main-image-8.0.0.3.0.ova" "--prop:hostname=naren.am.com" "--prop:ip=10.0.0.xx9" "--prop:netmask=255.255.252.0" "--prop:gateway=x1.3x.2xx.1" "--powerOn" "vi://root:xxxxx@1x.xx.2xx.5x/"

 

When i try to execute the above command i'm getting the below error.

Error:

Error: Unexpected option: --prop:ip=10.0.0.xx9

Completed with errors


OVF properties

Here's is my ovf content for the properties

      <Property ovf:key="ip" ovf:required="true" ovf:type="string" ovf:userConfigurable="true" vmw:qualifiers="Ip">

        <Label>2. IP Address</Label>

      </Property>

      <Property ovf:key="netmask" ovf:required="true" ovf:type="string" ovf:userConfigurable="true" vmw:qualifiers="Ip">

        <Label>3. Subnet Mask</Label>

      </Property>

      <Property ovf:key="gateway" ovf:required="true" ovf:type="string" ovf:userConfigurable="true" vmw:qualifiers="Ip">

        <Label>4. Default Gateway</Label>

      </Property>

 

Using  "vSphere Client version 5.1.0"

 

Can anyone help me in resolving this problem ?

ovftool fails with Error: vim.fault.FileNotFound

$
0
0


Hi all.  I'm trying to archive some no-longer-used VMs with ovftool, and I've managed to save half of them.  The ovftool output looks like:

wpeters$ ovftool vi://root@zeus/Riverbed/VSH_250m /Volumes/Archive/VSH_250m.ova

Enter login information for source vi://zeus/

Username: root

Password: *********

Opening VI source: vi://root@zeus:443/Riverbed/VSH_250m

Opening OVA target: /Volumes/Archive/VSH_250m.ova

Writing OVA package: /Volumes/Archive/VSH_250m.ova

Transfer Completed                    

Completed successfully


 


The other half of the machines fail with the mysterious vim.fault.FileNotFound without saying which file isn't found.  I've looked at the settings for both successful and unsuccessful VMs and cannot figure out what the difference is:


 

wpeters$ ovftool vi://root@zeus/Riverbed/VSH_markt /Volumes/Archive/VSH_markt.ova

Enter login information for source vi://zeus/

Username: root

Password: *********

Opening VI source: vi://root@zeus:443/Riverbed/VSH_markt

Error: vim.fault.FileNotFound

Completed with errors

 

OVA export to ESXi

$
0
0


I used the ovf tool with the export of an ova created in VirtualBox. I am getting an error:


The OVF package requires unsupported  hardware.


Details: Line 83: OVF hardware element 'Resource Type' with instance ID 7: No support for the virtual hardware device type '35'.


 


I am not sure where to go and what value to change it to.  Thanks for any advice that you can provide.

Protecting an OVF/OVA

$
0
0

Hi,

I am working on vcenter server 5 standard. I am generating an OVA using vsphere client. Since OVA is a tar file, unauthorized user can get hold of the software. So i am looking at solutions to prevent this.
I could protect the tar file by using gcrypt or similar - however it will involve additional step of decrypting before deploying in vcenter or workstation.

Are there any other means to protect the OVA while still retaining the simplicity of deployment ?

I see that vcenter is generating OVA using OVF version 1.0 however OVF version 2.0 does have defined something for package protection.
There does not seem to be information available on web about VMWare product that can generate 2.0 OVF...

Any advise is appreciated

 

Thanks,
NV

ovftool errors for cluster names which contain url encoded characters

$
0
0

Cluster display name: cluster1/
Cluster edit properties: cluster%2f

 /usr/bin/ovftool--noSSLVerify vi://user:pass\@vcenterserver/"datacenter"/"host"/"cluster1%2f"/

 

Error: Locator does not refer to an object: vi://user@vcenterserver:443/datacenter/host/cluster1//

Error: Locator does not refer to an object: vi://jcrocker@ng-v28.sc.steeleye.com:443/VC_50_NG_DEV/host/ng-vc-50-dev-ha//

Error: Failed to open disk: Test.vmdk

$
0
0

Hello all,

 

I am having a problem with the ovftool.

 

Here's what i did.

 

1)I created a VM running CentOS.

 

2)These are the 3 files that i got.

 

Test.vmx

 

Test.vmdk (Descriptor File)

 

# Disk DescriptorFile

version=1

CID=5046e880

parentCID=ffffffff

createType="vmfsPreallocated"


# Extent description

RW 83886080 VMFS "Test-flat.vmdk" 0


# The Disk Data Base

#DDB


ddb.virtualHWVersion = "4"

ddb.geometry.cylinders = "83220"

ddb.geometry.heads = "16"

ddb.geometry.sectors = "63"

ddb.adapterType = "lsilogic"

 

Test-flat.vmdk

 

3) This is the command that i ran

 

ovftool "Test.vmx" "Test_New.ova"

 

4)This is the error that i got.
2012-09-05T12:24:57.817+05:30 [7F22134FE740 verbose 'Default'] [ovfTool.cpp] Done initializing libs
2012-09-05T12:24:57.817+05:30 [7F22134FE740 verbose 'Default'] [ovfTool.cpp] Determining source
2012-09-05T12:24:57.818+05:30 [7F22134FE740 verbose 'Default'] [ovfTool.cpp] Determining target
Opening VMX source: Test.vmx
2012-09-05T12:24:57.821+05:30 [7F22134FE740 verbose 'Default'] Failed to open disk: ./Test-1-0.vmdk
2012-09-05T12:24:57.821+05:30 [7F22134FE740 verbose 'Default'] Exception: Failed to open disk: ./Test-1-0.vmdk. Reason: The file specified is not a virtual disk
Error: Failed to open disk: Test-1-0.vmdk

Please help!

 

Thank you

OVA file generated using OVFTool not played by Player5.0

$
0
0

I have VMware Player 5.0.0. It internally has ovftool 3.0.1

 

I used VMware Studio2.0 to build an appliance in  OVA format  - It opened successfully by Player 5.0

Converted OVA -> OVF again from OVF->OVA using ovftool 3.0.1. (This is just for testing. Later I need to change OVF according to my need).

 

Now this re-generated OVA file is not supported by Player5.0. When I tried to open OVA file, Player failed with error 'Failed to open virtual machine: Failed to open OVF descriptor.'

 

Is this an issue with OVFTool or Player ? Please suggest.

 

BTW, I have used the below commands for convertion

 

OVA -> OVF      ovftool.exe -st=OVA -tt=OVF "d:\NEW-OVA\xxxxxxx.ova" "d:\NEW-OVF\xxxxxxx.OVF"
OVF -> OVA      ovftool.exe -st=OVF -tt=OVA "d:\NEW-OVF\xxxxxxx.ovf" "d:\NEW-OVA\xxxxxxx.OVA"
Without -st, -tt options, ovftool is assuming the VMX format.

 

Thanks in advance

 

--hemanth

How do I set target VM hostname when deploying OVA?

$
0
0

I'm deploying OVA files to a vCenter using ovftool; it's working perfectly, but I want to go the extra mile and automatically set the hostname of the VM after it is deployed.

 

I found a reference to a 'hostname' property (--prop:hostname=myvm.example.com), but it doesn't actually work

 

Here's my command  line

ovftool --lax --acceptAllEulas --datastore=MySAN --overwrite --powerOn --vmFolder=TestFolder --diskMode=thin --powerOffTarget --prop:hostname=myvm.example.comhttp://myurl.com/path/input.ova vi://vcenteruser:password@mycenter.example.com/MyDC/host/MyD/Resources/OVFTest

 

So what is the proper way to do this?

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

setting ovf properties with ovftool and vcloud

$
0
0

I'm trying to import an OVA file with settable OVF properties for configuration (product key, network configuration) into vCloud with ovftool. It seems from the documentation that I should be using the --prop option to set these values, but they don't seem to get passed through vCloud to the deployed vApp, and the system gives an error about unconfigured properties when it tries to start up. I can go in the vCloud interface and manually enter them for my vApp, but I was hoping to automate the process with ovftool.

 

At first I thought the issue was that the properties where at the VM level instead of the vApp level, but changing the OVA in vSphere to move the properties to the vApp itself produces the same result. Using the same command to import the OVA directly into vSphere correctly sets the properties with either version.

 

Is setting of OVF properties for vCloud supported by ovftool? If so, what is the correct syntax?

 

Currently running:

 

ovftool -o --acceptAllEulas --prop:productkey="XXXXX-XXXXX-XXXXX-XXXXX" --prop:ipaddress="10.146.3.1" --prop:netmask="255.255.0.0" --prop:gateway="10.146.1.254" vApp.ova vcloud://vclouddirector?org=IT&vdc=IT&catalog=IT&vapp=test1

 

Thanks.

OVF Specification 1.0 Annex D

$
0
0

 

The VMWare ovf-tool includes a few schema files in ovftool/schemas/vmware that include the header:

 

"Remark: The OVF Specification 1.0 Annex D defines a set of relaxations on how the this XML Schema 1.0 definition is to be interpreted."

 

The latest version of the OVF specification available on dmtf.org, 1.0.0, ends at Annex C - there is no Annex D.

 

 

Any idea where this may be obtained?

 

 

Thanks!

 

 

Mike

 

 

 

 

 

OVF tool crashing?

$
0
0

 

Anyone using OVF extensively?

 

 

Environment...

 

 

ESXi 4 box, with a single very simple VM, just a VM, no disks, nothing more than a VM shell really.

ESXi 3.5 U 4 running a single VM, which has vCenter 4 running in it.  Windows 2008, 32, 1.5GB RAM for VM

Windows XP SP3 fully patched desktop to run OVF CLI tool for Windows and VIClient 4

 

 

Attempted...

 

 

1) From VI client, try to use GUI to Export OVF Template, VirtualCenter Service stops.

 

2) From Windows XP SP3 full patched desktop, where Windows OVF1.0 Tool installed, Attempt to do OVF export as attempted above, generates an unexpected exception trap.  vCenter 4 VMware Virtual Center server stops.

 

 

C:\Program Files\VMware\VMware OVF Tool&gt;ovftool "vi://administrator@192.168.15.3/Home Office/vm/Test01" ./Test01.OVF

Please enter login information for source vi://192.168.15.3/

Username: administrator

Password: *********

Opening VI source: vi://administrator@192.168.15.3/Home Office/vm/Test01

Error: The specified network name is no longer available.

This application has requested the Runtime to terminate it in an unusual way.

Please contact the application's support team for more information.

Terminate process signal received - aborting operation

C:\Program Files\VMware\VMware OVF Tool&gt;

 

 

 

 

 


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 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?

 

 

 

 

 

 

 

 

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?

 

 

In search of vmware specific OVF schema (http://www.vmware.com/schema/ovf)

$
0
0

 

Hi,

 

 

I have been trying to work with OVF. I need to be able to read/write in OVF files using xml tools.

 

 

I have exported VM as OVF using the VI CLient and also programmatically. Each time I get and OVF file with the following namespace reference:

 

 

http://www.vmware.com/schema/ovf

 

 

I can't find this schema at the respective URL.

 

 

Does anyone know where I can find this .xsd?

 

 

Thanks in advance,

 

 

Derek

 

 

Can't import OVA in to a folder

$
0
0

 

I an trying to inport an OVA file in to a precreated folder named test under a datacenter.  I have created a fold under vCenterServer/datacenter/host/test and running the below command.

 

ovftool --powerOn C:\Images\cur\NAMEHERE.ova vi://Administrator:PASSWORD@192.168.1.100/vCenterServer/datacenter/host/test

 

 

 

 

When i run this command i get the below output

Opening OVA source: C:\Images\cur\NAMEHERE.ova

Error: Found wrong kind of object (Folder)

 

I have also tried the same but importing in to a VM folder vCenterServer/datacenter/VM/tes, this gives the same error as above.

 

What am i doing wrong?

 

 

 

Viewing all 34499 articles
Browse latest View live


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