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

Deploy OVF Template in VMWare Workstation 10 using ovf-tool

$
0
0

Hi All,

 

I just started exploring the ovf-tools. I have an ovf template available for a VM and I was able to deploy it in Workstation using the GUI.

Is there a way / command available to use this pre-existing .ovf template and deploy a Virtual Machine in workstation using this; through ovf-tool?

 

Any help would be appreciated.


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 Tries to Open vmx File Directory

$
0
0


I've been given a backup of a VMWare Virtual Machine that I'm trying to move to ESXi.  Running ovftool on this produces an error that says it can't open a file.  However, the file it can't open is actually the directory containing the VM files:


C:\Program Files\VMware\VMware OVF Tool>ovftool.exe i:\MFTsrv-Win2008-Teacher\POT_2008R2_DEMO.vmx d:\MQFTE.ovf
Opening VMX source: i:\MFTsrv-Win2008-Teacher\POT_2008R2_DEMO.vmx
Error: Failed to open file: i:\MFTsrv-Win2008-Teacher\
Completed with errors



I've also tried under Linux with the same results:


[eddieath@oc5321677557 ~]$ sudo ovftool --X:logFile=logit --X:logLevel=verbose /media/MFTsrv-Win2008-Teacher/POT_2008R2_DEMO.vmx MQFTE.ovf
Opening VMX source: /media/MFTsrv-Win2008-Teacher/POT_2008R2_DEMO.vmx
Error: Failed to open file: /media/MFTsrv-Win2008-Teacher/
Completed with errors


 


The attached logfile contains this:


2015-04-15T07:37:39.237-07:00 verbose /media/MFTsrv-Win2008-Teacher/ is not a file

 


 


What am I doing wrong here.


 


Cheers.


 

OVF tool fails to convert .vmx to ova

$
0
0

Hello, new to here and couldnt find a solution to my issuue.

Downloaded VMware OVF Tool 4.1.0

I am trying to convert GNS3 WorkBench 12.3a into an OVA to install as a guest on ESXi 5.5

GNS3WB123.vmx is the file that I'm trying to convert to OVA

 

I have tried following the directions from https://www.vmware.com/support/developer/ovf/ovf10/ovftool_10_userguide.pdf

 

I continue to get failed messages. Is there anyone here that can assist with the OVF tool so I can run GNS3 as a guest, instead of installing on a guest Windows or Linux program?

 

Thanks

Cannot Import OVF into ESXi 3.5

$
0
0

 

Using a seperate process (python-vm-builder), I am building an ESX/ESXi compliant image that I have confirmed can be uploaded, imported and started in Workstation, ESX 3.0, ESXi 3.5 and even Server 2.0+.

 

 

I'm trying to go into the next step now, and convert this ESXi Image into a single OVF archive for even easier deployments.

 

 

Using the latest OVF Tool I have successfully created the new .ovf and zipped it up inside a tar.gz'd.  On my Windows box, I then extract it (using WinRAR), then using 'Import' in VIC try to import it.  When I select the OVF and click next it then throws the below error:

 

 

 

 

 

An error occurred while parsing the OVF descriptor

Unable to parse XML element 'Envelope'

 

 

 

 

 

What am I doing wrong? 

 

 

I have attached both the original VMX and the new OVF.

 

 

Please help!

 

 

 

 

 

Thank you.

 

 

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?

 

 

Scripting ovftool

$
0
0

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

OVA template deployment - sysprepping and customizing the deployment

$
0
0

Hello,

I am seeking guidance on automation\customization of an OVA deployment.

 

Looking to use an OVA due to it's compression ability which is favorable when needing to transfer a VMWare virtual machine from Host to Host for deployment at different location across a WAN.  In the past, we have created a VM template and provided customization file for deployment but the size of the template was too large for transfer across the WAN....so we would have to ship on seperate media.

 

I am looking to achieve the same end result of deployment of a vm template but through the deployment of the OVA template.

Here is where I am at so far:
1. Create the VM (in this case Windows XP SP3)
2. Export the VM to OVA Template.
3. Deploy OVA Template

 

All of the above works without any problem.  However, during deployment of the OVA, I would like to prompt the end user to input computer name, Fixed IP information or DHCP, domain to join, etc.  Additionally, I would like sysprep to run.

 

I have read the guide and numerous articles on the OVF descriptors, but not quite sure where or how to input these prompts so they appear during the OVA deployment.  Additionally, if I sysprep the vm before exporting to OVA, how can I get sysprep and the input from the end user deployment to work hand in hand.

 

Thanks in advance for any guidance or tutorial reference you can supply to help me understand OVA deployment of a single vm and how to configure custom settings during deployment with sysprep running.


vCenter 5 virtual appliance configuration

$
0
0

Hello..

 

Is it possible to give vCenter appliance ip, gateway, netmask etc via ovftool? Same way as to Orchestrator.

 

--prop:vami.DNS.VMware_vCenter_Server_Appliance=10.0.0.69  --prop:vami.gateway.VMware_vCenter_Server_Appliance=10.0.0.1  --prop:vami.ip0.VMware_vCenter_Server_Appliance=10.0.0.96  --prop:vami.netmask0.VMware_vCenter_Server_Appliance=255.255.255.0

 

When running these commands with ovftool, it doesnt give any errors  or anything, but it doesnt pass the variables forward either. Clearly  vCenter appliance doesnt have any "intelligence" for such feature.

 

ovftool --acceptAllEulas --skipManifestCheck  --datastore=storage-1 --diskMode=thin --name=vcenter --prop:vami.DNS.VMware_vCenter_Server_Appliance=10.0.0.69   --prop:vami.gateway.VMware_vCenter_Server_Appliance=10.0.0.1   --prop:vami.ip0.VMware_vCenter_Server_Appliance=10.0.0.96   --prop:vami.netmask0.VMware_vCenter_Server_Appliance=255.255.255.0

/VMware-vCenter-Server-Appliance-5.0.0.3324-472350/VMware-vCenter-Server-Appliance-5.0.0.3324-472350_OVF10.ovf.backup  vi://10.0.0.10

 

So any tips? Do I need to create some external media and modify the appliance to add it in, which will pass the needed variables to appliance, and script which will run from init.d on start and read those?

 

-k-

How to use ovftool command line utility Video Tutorial

VMware Workstation Natively

$
0
0

okay, I know this isn't developed yet, but I thought I would ask about.

first I love VMware workstation, amazing tool. and most VMware products are quick and easy for the average user.

 

okay to meat of the topic. What would it take to install VMware natively withOUT a host operating system"

 

hear me out. I really love virtualization, and the option it gives to run ANY OS, but the drawback would be the HOST OS, I WISH there was a way to install a very simple OS that VMware creates or uses, to launch it's workstation. maybe call it "LiteStation". then with the same use of the workstation, load your OS, or OS's in many cases, being able to with such a low foot print might be able to open some doors for new technology.

 

now, the simple OS, it need limited capabilities, like driver install (preferably win drivers as they are the most common and most ready, but Linux drivers would be the most understandable), limited programs or possibly no program installs. but it need enough to use the full potential of the machine, so x64 would be required along with VT-x/EPT or AMD-V/RVI + acceleration etc.... with no browsers there won't be a need to install much security, just force it to connect, but not use the network connection except to switch it over to bridge the OS's in VM-LS.

 

I'm sure this software is not out there yet. but think of the possibilities, it would become a 'virtual' boot-loader... running all OS's in a virtual environment, utilizing the max potential of multi-platform. I could see the diminish of speed as we allocate a % of the native hardware for use by the VM's, but still. No longer would dual booting be a norm, having to restart just to use a different OS, but booting both would increase. sure we have native, but sometimes I don't want to mess with Win/Lin/OS just to get to the one I want. and I feel the native OS limits the use of the virtual machine.

 

or maybe something like this is already running.... I just haven't found out.

 

Anyways thanks for the listening... who knows maybe VMware might want to implement something like LiteStation in their software arsenal....

Accipitor

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

ovftool 3.5.0 not running on CentOS 5 (needs GLIBC 3.4?)

$
0
0

Installed ovftool 3.5 on CentOS 5.9.  Install went without any errors, says Installation Successful.

 

Running ovftool yields about 5 errors similar to:

/usr/lib/vmware-ovftool/ovftool.bin: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by /usr/lib/vmware-ovftool/libvmomi.so)

 

CentOS 5.9 doesn't support GLIBC 3.4.

 

The ovftool documentation says it supports CentOS 5 and 6.

 

What's the problem here?

Static IP given during OVA deployment doesnt take effect post deployment

$
0
0

Hi Everyone,

 

I was trying to deploy a VM using the ovftool, I thought I would use the properties which are thrown from a "probe" of the OVA file.

 

ovftool http://server/files/builds/vpas/6.0.0/latest/vPAS-installer.ova

 

Properties:

  ClassId:     vami

  Key:         gateway

  InstanceId   vPAS

  Category:    Networking Properties

  Label:       Default Gateway

  Type:        string

  Description: The default gateway address for this VM. Leave blank if DHCP is

               desired.

 

  ClassId:     vami

  Key:         DNS

  InstanceId   vPAS

  Category:    Networking Properties

  Label:       DNS

  Type:        string

  Description: The domain name servers for this VM (comma separated). Leave

               blank if DHCP is desired.

 

  ClassId:     vami

  Key:         ip0

  InstanceId   vPAS

  Category:    Networking Properties

  Label:       Network 1 IP Address

  Type:        string

  Description: The IP address for this interface. Leave blank if DHCP is

               desired.

 

  ClassId:     vami

  Key:         netmask0

  InstanceId   vPAS

  Category:    Networking Properties

  Label:       Network 1 Netmask

  Type:        string

 

 

After having made sure that such properties exists from the probe, I tried to use them to give the VM a static IP post deployment, automatically.

 

 

ovftool --datastore="31_datastore" --acceptAllEulas --ipAllocationPolicy=fixedPolicy --name="vPAS_31_1" --powerOn --prop:ip0="172.16.121.115" --prop:netmask0="255.255.0.0" --prop:DNS="172.16.1.10" --prop:gateway="172.16.1.1" http://server/vpas/6.0.0/latest/vPAS-installer.ova vi://root:password@172.16.121.31/

Opening OVA source: http://server/files/builds/vpas/6.0.0/latest/vPAS-installer.ova

The manifest validates

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

Deploying to VI: vi://root@172.16.121.31:443/

Transfer Completed                   

Powering on VM: vPAS_31_1

Warning:

- OVF property with key: 'DNS' does not exists.

- OVF property with key: 'gateway' does not exists.

- OVF property with key: 'ip0' does not exists.

- OVF property with key: 'netmask0' does not exists.

Completed successfully

 

Can someone please explain me whether this is a common problem ( from VMware ) or something I am doing wrong?

 

Thanks,

ovftool VM->ova/f fails with SHA1 digest of file . . . disk.iso does not match manifest"

$
0
0

I'm trying to create an OVA file from an installed VM.  If I try creating it with ovftool 3.5, it downloads everything completely then gives me the following error:

SHA1 digest of file https://172.31.68.10:443/ha-nfc/52cca89a-6cde-c7a7-0810-25ff2197d3d6/disk-1.iso does not match manifest
and then deletes the file(s) it generated.

 

I am using compress=0 and --noImageFiles so i don't get the install iso.

 

If I manually go into Edit Settings and remove the cdrom, then 3.5 creates the ova correctly.

 

If I use ovftool 2.0, it succeeds even without manually removing the cdrom iso.

 

I've seen posts where users get the same error I do when they are going ova/f to vm and the answer is to delete the manifest.   Since all of the files are deleted after the error message, I don't have the option to delete the locally created manifest.

 

Is there a way to keep the files around even after a manifest error?

 

Does anyone know why ovftool 3.5 would fail in this case and 2.0 would word?  Has there been some deprecation between the two of them?

 

Thanks,
Mike


question regarding adding extra config parameters to ovf

$
0
0


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


 

Failed to deploy

$
0
0

Hi All,

 

Please help me as I am trying to deploy my OVF in an esxi and I get the following error

 

"Failed to deploy OVF package: File ds:///vmfs/volumes/546b400f-680d4bc0-11f7-001517d3b60c/_deviceImage-0.iso was not found"

 

I don't know if I am correct if i deduce that the export might have an iso image mounted on it and now it can't locate it?

 

I exported the OVF from esxi 5.5 and the destination esxi is also 5.5.

 

I have also attached the screenshot of the error mentioned above.

 

Please help

 

Appreciate all the help I could get and thank you in advance

 

Regards,

Error converting OVF to VMX -- virtualbox-3?

$
0
0

I am trying to convert a .ovf to a .vmx using the ovftool utility in terminal on OSX 10.6.8.

 

USING the --lax command, the result I get is as follows:

 

 

Opening OVF source: /Users/Andrew/Desktop/CS50/appliance50-17/appliance50.ovf
Opening VMX target: /Users/Andrew/Desktop/CS50/appliance50-17/appliance50.vmx
Warning:
- Line 39: Unsupported hardware family 'virtualbox-3'.
- Line 107: OVF hardware element 'ResourceType' with instance ID '10': No support for the virtual hardware device type '35'.
- Line 63: OVF hardware element 'ResourceType' with instance ID '5': No support for the virtual hardware device type '20'.
- Missing hardware element 'CPU' with RASD type '3'.
- Line 127: Duplicate element 'AddressOnParent'.
Writing VMX file: /Users/Andrew/Desktop/CS50/appliance50-17.vmwarevm/appliance50.vmx
Transfer Failed                      
Error: Capacity mismatch for disk /Users/Andrew/Desktop/CS50/appliance50-17.vmwarevm//appliance50-disk1.vmdk
Deleting directory tree below: /Users/Andrew/Desktop/CS50/appliance50-17.vmwarevm
Warning:
- No manifest file found.
Completed with errors

 

 

Any suggestions on how to fix this?  It seems to be a problem with ovftool itself?

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&gt; 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&gt; 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

 

 

ERROR: Not a supported disk format(Invalid sparse VMDK header)

$
0
0

Hi All,

 

I have just come across ovftool and was giving a try to it. I am fairly new to VMware world.

I have a  .OVF which I exported using vSphere client 4.0. This .OVF comprises of 3 Suse Linux based virtual machines. i.e. I created a vApp on ESX (4.1) host, in this vApp I put my 3 SLES VMs and then exported it as OVF.

It has a total size of around 4.5GB.

 

Now I ran this command to compress this .OVF as well as gave an option to create deltadisks.

C:\> ovftool --compress=9 --makeDeltaDisks --skipManifestCheck  MyVMCluster\MyVMCluster.ovf   E:\

 

output:

{{{

The manifest does not validate
Generating delta disks for 2 disks (capacity 40960 MB)
Reading disks
Disk Transfer Completed

 

Determining optimal configuration for capacity group
Writing configuration to disk
Disk Transfer Completed

 

Completed successfully

}}}

 

Now when I checked my E:\ It had created a folder with the same name and put related files there. I saw a significant reduction in the new vmdk size. ( around 2.3GB now )

 

Now when I manually deploy this new ovf on vSphere client, it goes till certain %age and then flags an error:

{{{

Error uploading file to server ( E:\MyVMCluster\disk3.vmdk.gz ) Not a supported disk format ( Invalid sparse vmdk header )

}}}

and then it stops and everything rolledback.

 

 

Any pointers ?

 

Thanks

Nikunj

Viewing all 34499 articles
Browse latest View live


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