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

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

 

 

 

 

 


ovftool 1.0 and virtualcenter 2.5 update 4 Envelope error importing ovf

$
0
0

When I try to import an OVF vile created with ovftool 1.0 I get a compatibility error

 

an error occurred while parsing the ovf descriptor:

 

 

unable to parse xlm element ‘Envelope'

 

 

I made an ovf file using ovftool 1.0 from a virtual machine I was running on an ESX 3.5 server.

 

 

The tool created the file with no problems and when I run the following command I get no error:

 

 

ovftool --schemaValidate x:\OVF\clone.ovf

 

 

Opening OVF source: x:\OVF\clone.ovf

 

 

OVF version:   1.0

 

 

Name:          clone (1)

 

 

 

 

 

Download Size:     5.14 GB

 

 

 

 

 

Deployment Sizes:

 

 

  Flat disks:     32.00 GB

 

 

  Sparse disks:    8.13 GB

 

 

 

 

 

Networks:

 

 

  Name:        VM Network

 

 

  Description: The VM Network network

 

 

 

 

 

Virtual Hardware:

 

 

  Family:       vmx-04

 

 

  Disk Types:   SCSI-lsilogic

 

 

 

 

 

Completed successfully

 

 

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

 

 

no love for Fusion users?

$
0
0

 

I just found out that I cannot import any of my ovf images into Fusion. Very disappointing. It looks like there may have once been an ovftool binary for Mac users but I'm unable to find it anywhere. Does anyone know where I can get a copy of the tool for OS X? I could always do the conversion on my linux workstation but I'd rather do most of my work on the Mac.

 

 

Will ovf import/export be built into Fusion in a future version? That sure would make things easier.

 

 

Thanks.

 

 

Packaging from VMX to OVF removes information

$
0
0

 

Hello,

 

 

After conversion from VMX to OVF (vmplayer use) , the OVF file does not include the information for "Network Config/Setup Type" and "Shared Folders".

 

 

Because of that, Shared Folders need to be added and network interface set to NAT on VMplayer run-time. I am unable to find any such parameters in VMware and OVF-Specs documentations.

 

 

Here are the relevant details from VMX file:

 

 

Network Connections:

 

 

ethernet0.present = "TRUE"

ethernet0.connectionType = "nat"

 

 

Shared Folders:

 

 

sharedFolder0.present = "TRUE"

sharedFolder0.enabled = "TRUE"

sharedFolder0.readAccess = "TRUE"

sharedFolder0.writeAccess = "TRUE"

sharedFolder0.hostPath = "Z:\"

sharedFolder0.guestName = "Z-Drive"

 

 

Any help appreciated.

 

 

Thanks.

 

 

Trying to convert VirtualBox OVF

$
0
0

 

I'm trying to convert an VirtualBox OVF that we had prepared to use in a ESX environment, but am recieving errors.  First off, I just want to make sure we are able to do this and secondly if anyone is able to help me resolve the errors.

 

 

Initiall I received the following errors.  This is trying to do a conversion directly on the ovf I was given.

 

E:\Documents and Settings\user\Desktop>ovftool debian-server-32bit.ovf debian-s
erver-32bit.vmx
Opening OVF source: debian-server-32bit.ovf
Warning: No manifest file
Opening VMX target: debian-server-32bit.vmx
Error:
- Line 8: Unsupported value 'http://www.vmware.com/specifications/vmdk.html#spa
rse' for attribute 'format' on element 'Disk'.
- Line 37: Unsupported element 'Description'
- Line 45: Unsupported element 'Description'
- Line 48: Unsupported element 'AllocationUnits'
- Line 54: Unsupported element 'Description'
- Line 57: Unsupported element 'ResourceSubType'
- Line 58: Unsupported element 'Address'
- Line 63: Unsupported element 'Description'
- Line 66: Unsupported element 'AutomaticAllocation'
- Line 67: Unsupported element 'AddressOnParent'
- Line 74: Unsupported element 'ResourceSubType'
- Line 75: Unsupported element 'AutomaticAllocation'
- Line 76: Unsupported element 'Connection'
- Line 81: Unsupported element 'Description'
- Line 84: Unsupported element 'Address'
- Line 89: Unsupported element 'Description'
- Line 92: Unsupported element 'ResourceSubType'
- Line 93: Unsupported element 'AutomaticAllocation'
- Line 94: Unsupported element 'AddressOnParent'
- Line 99: Unsupported element 'Description'
- Line 102: Unsupported element 'HostResource'
- Line 103: Unsupported element 'Parent'
- Line 104: Unsupported element 'AddressOnParent'
- Line 109: Unsupported element 'Description'
- Line 112: Unsupported element 'AutomaticAllocation'
- Line 113: Unsupported element 'Parent'
- Line 114: Unsupported element 'AddressOnParent'

 

After this I tried importing into VirtualBox and then exporting will checking the use Legacy OVF setting.  Which resulted in the following error:

 

E:\Documents and Settings\user\My Documents>ovftool "Debian Server (32bit).ovf"
ian-server-32bit.vmx
Opening OVF source: Debian Server (32bit).ovf
Opening VMX target: ian-server-32bit.vmx
Error:
- Line 82: OVF hardware element 'ResourceType' with instance ID '7': No support
for the virtual hardware device type '35'.

 

Failed to import OVF 1.0 image into an ESX 3.5 server using ovftool 1.0

$
0
0

I followed the ovftool 1.0 user's guide to try to import an OVF 1.0 image into an ESX 3.5 server, the ovftool command I ran is like below:

 

C:\Program Files (x86)\VMware\VMware OVF Tool>ovftool.exe -ds="vitestbox3:storage1" "c:\temp\ovf\WebSphere_V7.ovf" "vi://root:xxxxxx@vitestbox3.rtp.raleigh

.ibm.com"

Opening OVF source: c:\temp\ovf\WebSphere_V7.ovf

Warning: No manifest file

Opening VI target: vi://root@vitestbox3.rtp.raleigh.ibm.com/

Warning:

- The operating system has been mapped to 'Other Linux (32-bit)' from '' (id: 84).

Error:

- Line 31: Unsupported hardware family 'vmx-04'.

 

Then I didn't change anything and ran the above command again in the same command line window, but this time, I got a different result:

 

C:\Program Files (x86)\VMware\VMware OVF Tool>ovftool.exe -ds="vitestbox3:storage1" "c:\temp\ovf\WebSphere_V7.ovf" "vi://root:xxxxxxt@vitestbox3.rtp.raleigh

.ibm.com"

Opening OVF source: c:\temp\ovf\WebSphere_V7.ovf

Warning: No manifest file

Opening VI target: vi://root@vitestbox3.rtp.raleigh.ibm.com/

Target: vi://vitestbox3.rtp.raleigh.ibm.com/

Disk Transfer Failed

Error: Target disk not found

Deleting VM: WebSphere_V7

 

On the ESX server side, I saw it tried to create a VM, but removed it immediately due to a failure. I am not sure if I need to specify other options in the command, or I need to change something in .ovf file. It would be appreciated if someone can give me some advices/suggestions. Thanks.

 

- Matt

OVF tool for Windows 64 bit OS VMs

$
0
0

 

Hi All,

 

 

Do we have an ovf tool

for Windows 64bit OS virtual machines? The ovf tool guide mentions tools

for Windows 32 bit OS and Linux 32 & 64 bit OS but not for Windows

64 bit OS virtual machines.

 

Pleas help.

 

Regards,

Andy

ankit_17@hotmail.com

 

 


Signed OVA package verification with ovftool failed

$
0
0

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.

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?

 

 

 

deploy on multiple hosts (ESXs)

$
0
0

 

Hello,

 

 

 

 

 

I have a vApp that consists of several VMs, is it possible to deploy on on a number of hosts (and determin what will be deployed where)?

 

 

 

 

 

thanks.

 

 

can i convert a windows VM to a OVF

$
0
0

it seems most OVF format is linux VM. so can i convert a windows VM to a OVF? if i have only windows eval license, what will microsoft count the start eval date? from the day when OVF is packaged or from the day OVF is downloaded?

Not able to deploy a VM from .ova format using ovf tool

$
0
0

I am trying to deploy a VM into ESXi 4.1  from .ova template using

ovftool.  My ESXi is having two datastores:- datastore1 and datastore-2.

 

This is the syntax I am using:-

 

ovftool.exe --name=test -nw="VM Network" -ds="datastore1" CentOS.ova vi://10.102.143.30

 

It is shows the following messages:-

 

Opening OVA source: CentOS.ova

Please enter login information for target vi://10.102.143.30/

 

After entering the login information nothing happens. It returned me the prompt. It also doesn't print any error message.

 

Below is my ova file information obtained by probing:-

 

 

Opening OVA source: CentOS.ova

 

OVF version:   1.0

Name:          CentOS

 

Download Size:     1.72 GB

 

Deployment Sizes:

+  Flat disks:     30.00 GB+

+  Sparse disks:    4.69 GB+

 

Networks:

+  Name:        VM Network+

+  Description: The VM Network network+

 

Virtual Hardware:

+  Family:       vmx-07+

+  Disk Types:   SCSI-lsilogic+

 

Warning: No manifest file

Completed successfully

ovftool doesn't support pvscsi?

$
0
0

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!

OVA to VMX using OVFTool in Mac OSx Terminal Problem

$
0
0

Hello,

 

I am new to OVFTool  and am having difficulty using it in Terminal on my MacBook Pro to convert an OVA (created by exporting my WinXp virtual machine from within VirtualBox), to a VMX file for use in VMWare Fusion on my MacBook Pro.

 

I have installed the OVFTool on my boot drive (partition) which is named "LFP OS", in the folder:  /Library/VMWare/OVFTool/.

 

I have the OVA file on my data drive (partition) which is named "LFP Data" in the folder: /Virtual Machines/WinXP.ova.

 

I want to create a virtual machine file (VMX) in the same location as the soure that I can then import into VMWare Fusion.  I have gone through the OVFTool User Guide, forums, Google etc. and cannot get it to work properly.  It may be as simple as my Terminal syntax being off.  Anyway, please help.

 

Here is what I used in Terminal:

 

LFP-MacBook-Pro:virtual machines nils$
LFP-MacBook-Pro:virtual machines nils$ pwd
/volumes/lfp data/virtual machines
LFP-MacBook-Pro:virtual machines nils$ ./Volumes/LFP\ OS/Library/VMWare/OVFTool/ovftool /Volumes/LFP\ Data/Virtual\ Machines/WinXP.ova /Volumes/LFP\ Data/Virtual\ Machines/WinXP.vmx
-bash: ./Volumes/LFP OS/Library/VMWare/OVFTool/ovftool: No such file or directory
LFP-MacBook-Pro:virtual machines nils$

 

Thanks for your time!

 

Regards,

SBNL


Converting OVA file to VMX

$
0
0

I downloaded the latest OVF converter tool but it looks like as per documentation, it cannot convert OVA to VMX?

If yes, how?  If no, how do I?  Thanks

Issue with --acceptAllEulas

$
0
0

Hi all,

 

I have a problem in deploying Suse OVF image, built using Susestudio.

while deploying the OVF, there's a default SuSE Eula which comes up.

using --acceptAllEulas doesn't seem to accept it automatically.

This Eula blocks my automation work.

 

Did any of you face this issue ??

Any help/workaround would be appreciated.

 

Thanks in advance.

Deploy ovf to a resource pool

$
0
0

Hi,

 

Ive read through the pdf and have tried a few different ways but couldnt figure it out. I was curious if anyone could give me an example syntax of deploying an ovf into a resource pool on the target.

 

Thanks for the help.

 

Ray

VMware OVF Tool 2.1.0 is now alive.

$
0
0

Hi All.

 

VMware OVF Tool 2.1.0 is now ready for download.

 

Go to the download link on the frontpage.

 

 

 

Eske

Lost network connection data during the OVF conversion process

$
0
0
Hi all,
My application converts an OVF format VM into VMX format, run a program to patch/insert file
into the vmdk file, re-convert the VMX format back to OVF format. During the process, the
original network connection changes from "VM Networks" to "bridge". I am trying to understand
if there is a solution to retain the original network connection setting.
Setup:
Virtual Center 4.1.0
OVF tool 2.1.0
A linux based on CentOS 5.5
Procedure:
1. Use the tool "Export OVF Template" on Virtual Center to export a Linux VM (other 32bit Linux).
2. Use command "ovftool sourcerfile1.ovf targetfile.vmx"
3. Use command "ovftool targetfile.vmk /tmp/test/sourcefile2.ovf"
When the VM was exported by VC (after step 1), the ovf file contains the following NetworkSection:
  <NetworkSection>
    <Info>The list of logical networks</Info>
    <Network ovf:name="VM Network">
      <Description>The VM Network network</Description>
    </Network>
  </NetworkSection>
 
When the OVF got converted from VMX (after step 3), the ovf file contains the following NetworkSection:
  <NetworkSection>
    <Info>The list of logical networks</Info>
    <Network ovf:name="bridged">
      <Description>The bridged network</Description>
    </Network>
  </NetworkSection>
I did have an older setup where it uses VC 3.5 and OVF tool 1.0. When I performed the same procedure,
the network section is unchanged in the final ovf file. When I compared the .vmx file between the
old and new procedure, they are almost identical, with the exception of number of CPU parameter.
So, what am I doing wrong here?
Any help is greatly appreciated.
Thanks.
Viewing all 34499 articles
Browse latest View live


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