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

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?


OVF

$
0
0

I would like to implement a scenario on XEN, KVM and OVF, after that i will make a compariasion, someone have a scenario??

 

Thanks

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

Not Able to Export to OVF

$
0
0

Not sure if I'm not getting the syntax correct, but I am attempting to export a vm in OVF format directly from a ESXi 4.1 host.

 

I have tried several different commands, but all have failed.

 

Any help with the Syntax to export the OVF directly from a Host would be greatly apprecaited.

 

ovftool --compress=9 "vi://host1/ha-datacenter/3PAR-LUN6/server1" "Z:\server1.ovf"

 

ovftool --compress=9  "vi://host1/DC1/3PAR-LUN6/server1/server1.vmx" "Z:\server1.ovf"

 

ovftool --compress=9  "https://host1/DC1/server1/server1.vmx" "Z:\server1.ovf"

VMware OVF Tool

$
0
0

Experts,

I downloaded and installed VMware OVF Tool i am running Vmware Workstation 9. I am trying to figure out how to use VMware OVF Tool and create my VMs. Any help with this ?

 

Regards,

SD

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

Automatic pre-installation of VMware Tools in an OVF

$
0
0

Hello,

 

We use a script to generate a Linux OVF using VMware automation commands. We would like VMs created from this template on ESXi to have VMware Tools pre-installed and configured so that no extra manual step is required from the user.

 

Can this be done with vmware-install.pl? We need the OVF generation process to be fully automated.

Best way to export a VM as an OVF/OVA ?

$
0
0

Hi All,

 

Everytime I manually export a VM using vsphere client, I am getting the resultant ovf of much larger size. ( i.e. size of .vmdk's are much larger, increases by 10% everytime )
I looked at various temporary files and log files and deleted them before taking the ovf, but it also doesnt reduces the size significantly.
My vm doesnt do any huge IO on the disks.

 

Is there a best practice for exporting an ovf .? ( Ex. SLES based vms. )


Thanks

Nikunj


OVFtool bug when specifying datastore

$
0
0

It appears that ovftool 3.0.1 has an issue while specifying the target datastore when importing an OVF when the VI is a vCenter 5.0 server with ESX 5.0 Update 1 hosts that have a large number of Datastores.  The cluster where this problem occurs has 148 Datastores.

 

Some datastores work, most don't.  This is a new problem since ovftool 2.0.1 worked fine when this cluster was at ESX 4.0 Update 3.

 

An example statement that will cause the problem (with all names replaced with "test" names):

 

"C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" --acceptAllEulas --name="TestVM" --datastore="TestDatastore" --network=TestNetwork --vmFolder="TestFolder" http://192.168.0.1/public/ovfs/testvm.ovf vi://"username:password"@vcenter.test.com/"Data Center"/host/"HA and DRS"/Resources/"Test Resource Pool"

 

Which results in this error (with the datastore names replaced with TestDatastoreX), even though the Datastore clearly exists.  It worked fine prior to vSphere 5.0 and vCenter 5.0.  Any ideas?

 

Note that all "possible completions" specified below work fine!  Those that I have tried that are "not" in the possible completions do "not" work.

 

Error: Invalid target datastore specified (TestDatastore): Possible completions:
  TestDatastore1
  TestDatastore2
  TestDatastore3
  TestDatastore4
  TestDatastore5
  TestDatastore6
  TestDatastore7
  TestDatastore8
  TestDatastore9
  TestDatastore10
  TestDatastore11
  TestDatastore12
  TestDatastore13
  TestDatastore14
  TestDatastore15
  TestDatastore16
  TestDatastore17
  TestDatastore18
  TestDatastore19
  TestDatastore20
  TestDatastore21
  TestDatastore22
  TestDatastore23
  TestDatastore24
  TestDatastore25
  TestDatastore26
  TestDatastore27
  TestDatastore28
  TestDatastore29
  TestDatastore30
  TestDatastore31
  TestDatastore32
  TestDatastore33
  TestDatastore34
  TestDatastore35
Completed with errors

Serious problem in ovftool VMDK input

$
0
0

All,

 

First of all, apologies if this is an inappropriate forum. I do not have a support contact for this issue. We are VMware customers, however our licenses are purchased through an academic reseller. Our concern is that this bug has crept into recent releases and perhaps gone unnoticed in QA. It's serious enough for us to consider moving to other hypervisor products.

 

I believe there may be a serious bug in OVFtool's disk read code. We observe that VMs are created OK after upload or import, but disk contents are zero-filled. No error conditions are reported at any time. It is only clear that the bug has been exercised, when an uploaded or imported VM fails to boot.

 

We have several research VMs with multiple LANs, which run FreeBSD 8.2 in VMware Fusion 5.0.2, MacOS X 10.8.2 Mountain Lion. I was also able to reproduce the bug with a fresh installation of vSphere ESXi 5.1 and ovftool 3.0.1. V

 

Using the separately packaged ovftool, I can export the VMs inside Fusion, by giving fully qualified paths to their VMX files. The bug appears to be in VMDK read. I exercised it in two use cases, Fusion OVA import and ESXi OVA upload, as follows:

 

  1. If I import an affected OVA into Fusion from the GUI, Fusion will invoke its own copy of ovftool 3.0.1 to perform the import. VMs are created with a sane VMX file. VMDKs are created. However their contents are zero-filled, and the VMDK contents in the OVA have been ignored.
  2. If I upload an affected OVA to ESXi, using ovftool and a vi:// target URL on the command line, the same bug is observed with ESXi. Again, the VMX is sane - we inspected this by SSHing into ESXi and manually reviewing the VMX on the VMFS data store with vi. The VMDK contents are zeroed on the VMFS datastore, and the VMDK contents in the OVA have been ignored.

 

ovftool seems, in some cases, to ignore the contents of the packaged VMDK files in OVAs, and those associated with VMX files from VMware products.

 

To date I have only been able to reproduce the issue with FreeBSD guests. The bug does not appear in all exported OVAs, however affected VM and OVA combinations will consistently demonstrate it.

 

  • We first noticed this problem in October 2012, and have not been in a position to exercise it thoroughly until now.

 

  • I can make an OVA available which demonstrates the issue. Please contact me privately to arrange. The files are typically 2GB in size.

 

 

Other observations:

 

 

  • There is no problem with OVA generation. I have inspected the OVAs manually using tar, extracted the embedded VMDKs inside, converted them back to 2GB sparse format using vmware-vdiskmanager (or vmkfstools under ESXi), and loaded them into ESXi and Fusion respectively.

 

  • Since ovftool was introduced, VMDKs must be uploaded manually using SFTP to avoid triggering the bug. The functionality in the vmware-vdiskmanager command which allows direct upload to ESXi servers has been removed.

 

  • Casual inspection with DTrace under OS X reveals that ovftool seems to be reading the full OVA file contents. We initially thought there may been a problem with VMDK upload, however other guests have not been affected.

 

  • The serialized format VMDK contents in the OVA are consistent with the original VMDKs. We verified this in one case with MD5 checksums. This requires denying all writes during the test.
  • We also reproduced this bug with out-of-box, unmodified FreeBSD installations, as our research VMs use ZFS in GPT partition containers.

 

  • We also noticed that Fusion's private copy of ovftool will break if ESXi specific options are specified in $HOME/.ovftool - although this is a separate issue from the main bug.
  • No source code is supplied for ovftool, so users are not able to fix this issue themselves.

 

Workarounds:

 

  • We load the OVA into Oracle VirtualBox, and re-export the OVA from there.
  • This is undesirable for many reasons, the main one being that it loses all the network binding information, which is critical to our work.

 

 

thanks,

Bruce

Custom OVF Property in my Virtual appliance

$
0
0

I'm trying to create an additional property in my VM that I build with VMware Studio so that I can use OVFTool to pass a value for the property when I deploy the VM to a vCenter.

 

The property looks like that shown in red.  But when I invoke OVFTool to give a value to this property, what am I supposed to be using? 

 

Something like this I can't get to work:

 

    ovftool  <...>  --prop.ConfigurationManagementServer.My_VM_Name= 10.1.2.3   <..>

 

Thanks for any hints,

CJ

 

        <Section xsi:type="vadk:IpAssignmentSection_Type">

                <Info>Supported IP assignment schemes</Info>

                <vmw:IpAssignmentSection ovf:required="false" vmw:protocols="IPv4,IPv6" vmw:schemes="">

                        <Info>Supported IP assignment schemes</Info>

                </vmw:IpAssignmentSection>

        </Section>

        <Section xsi:type="vadk:PropertySection_Type">

                <Info/>

                <Property ovf:key="ConfigurationManagementServer" ovf:type="string" ovf:userConfigurable="true" ovf:value="puppet" ovf:qualifiers="MinLen(0),MaxLen(65535)">

                        <Label>Configuration Management Server (Optional)</Label>

                        <Description>Your configuration management server&apos;s fully-qualified name (e.g. config.avamar.com ). Blank if none.</Description>

                </Property>

        </Section>

        <Section xsi:type="vadk:AnyOVFSection_Type">

                <Info>

            Unknown OVF elements in this element will be passed directly

            to the OVF output descriptor without interpretation

        </Info>

        </Section>

        <Section xsi:type="vadk:UpdateSection_Type">

                <Info/>

                <vadk:Repository vadk:url="" vadk:username="" vadk:password="" vadk:passwordFormat="base64"/>

Attempting to deploy .OVA from fileserver to ESXi host and/or vSphere cluster

$
0
0

I am attempting to determine an easy method to deploy .OVA templates for quick provisioning/deployment of VM's.

 

I have built VM baselines using a development vSphere cluster and exported the VM to .OVA using vSphere client. Those .OVA files reside on a Linux fileserver with ovftool installed on the system and network access to future ESXi and/or vSphere clusters.

 

Is it possible to 'deploy' the .OVA template from the Linux fileserver directly to a remote ESXi host's datastore and/or vSphere cluster datastore? I cant get it to work.

 

My OVA file:

 

 

[root@centos_lab1 u0]# ls -lha

total 5.9G

drwxr-xr-x.  3 root root 4.0K Jun 28 08:48 .

dr-xr-xr-x. 24 root root 4.0K Jun 25 11:30 ..

-rw-r--r--   1 root root 5.9G Jun 24 10:01 test.ova

 

 

Attempting to deploy to ESXi host:

 

 

[root@centos_lab1 u0]# ovftool test.ova vi://root:test123@172.16.16.81

Opening OVA source: test.ova

Opening VI target: vi://root@172.16.16.81:443/

Error: No target datastore specified. Possible completions:

  iSCSI-Large

  ESX1_local_datastore

  iSCSI-Equallogic

  fusionio

  Super_ISO

Completed with errors

 

 

[root@centos_lab1 u0]# ovftool test.ova vi://root:test123@172.16.16.81/iSCSI-Equallogic/

Opening OVA source: test.ova

Error: Locator does not refer to an object: vi://root@172.16.16.81:443ha-datacenter/host/esx1.lab.q9.com/Resources/iSCSI-Equallogic/

Completed with errors

 

 

 

 

 

 

Any idea what I am doing wrong here? Is what I am trying to do even possible with ovftool?

Query Compression on an OVF

$
0
0

Is it possible to query what compression was run against an OVF when it was created?

 

What is the default compression level for ovftool?

Unable To convert .vmx to .ovf

$
0
0

HI

 

I got Workstation 7.1.5

I want to migrate my VM on to Esxi5.5

I tried to convert .vmx to .ovf with Command (ovftool E:\VM\VM4\VM4.vmx E:\OVF\OVF4\VM4.ovf)

But its failing with error :

C:\Program Files\VMware\VMware OVF Tool>ovftool E:\VM\VM4\VM4.vmx E:\OVF\OVF4\VM

4.ovf

Opening VMX source: E:\VM\VM4\VM4.vmx

Error: Failed to open disk: Windows Server 2008 x64-cl2.vmdk

Completed with errors

Convertion of .OVF to .VMX

$
0
0

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

OVFTool - vmware tools ip assignment on esxi free hypervisor.

$
0
0



Hi.


I ran into a problem when deploying an ova using ovftool with pre-installed vmware-tools. Once the appliance is booted up the IP address isn't dynamically assigned to it even though the appliance has vmware-tools pre-installed. That only happens on the ESXi free hypervisor and it works fine on the licesed version of the ESXi. I was under impression that ESXi free hypervisor provides full functionality for vmware-tools? If that's not the case, is there any other way of dynamically assigning an IP address to newly created ova?


Thanks.

slow speeds ovf tool

$
0
0

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

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

Which should be used for export VM? OVF or OVA?

$
0
0

Dear all,

 

My company will be closed soon and we need export the finance related VM to keep for several years for audit purpose.

 

We are using vCenter 5.0 right now. Which format should we used for export VM? OVF or OVA?

 

There will have chance that the VM need import again and we hope the format will be more favour to be import in the future vCenter after  5-6 years.

 

Please kindly help.

 

Ivan

how to export multiple vm to one single OVA file

$
0
0


it is simple to export ONE vm in vsphere client to one OVA file (File ->Export->Export OVF template, and then select ova in dropbox). But is there a way to export multiple VM to ONE OVA files? Can use ovftool to do that?


 


Any comment or hint is highly appreciated!


 


Hobby

Viewing all 34499 articles
Browse latest View live