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

ovftool terminating before starting the deployment of the ova

$
0
0

Hi Guys,

 

I want to get some feed back about the below stack trace after setting the --X:logfile and loglevel

 

 

2013-04-29T04:47:37.841-07:00 [02188 verbose 'Default'] [SSL_DB] Using C:\Documents and Settings\Default User\Application Data\VMware\ovftool_SSLDB as SSL DB
2013-04-29T04:47:37.856-07:00 [02188 verbose 'Default'] Subscribing to signal: 2 (SIGINT)
2013-04-29T04:47:37.856-07:00 [02188 verbose 'Default'] Subscribing to signal: 4 (SIGILL)
2013-04-29T04:47:37.856-07:00 [02188 verbose 'Default'] Subscribing to signal: 22 (SIGABRT)
2013-04-29T04:47:37.856-07:00 [02188 verbose 'Default'] Subscribing to signal: 8 (SIGFPE)
2013-04-29T04:47:37.856-07:00 [02188 verbose 'Default'] Subscribing to signal: 15 (SIGTERM)
2013-04-29T04:47:37.856-07:00 [02188 verbose 'Default'] OvfTool Version: VMware ovftool 3.0.1 (build-801290)
2013-04-29T04:47:37.856-07:00 [02188 verbose 'Default'] Using home directory: C:\Documents and Settings\Default User\Application Data\VMware\ovftool.cfg
2013-04-29T04:47:37.872-07:00 [02188 verbose 'Default'] OvfTool Environment:
--> /X:httpTimeout = "0"
--> /X:imageReadSize = "262144"
--> /X:logFile = "c:\ovftool.log"
--> /X:logLevel = "trivia"
--> /X:maxNumberOfTermSignals = "5"
--> /X:maxRedirects = "256"
--> /X:maximalDeltaConfSize = "8"
--> /X:maximalDeltaTreeSize = "6"
--> /X:progressSmoothing = "60"
--> /X:useMacNaming = "false"
--> /X:vCloudEnableGuestCustomization = "false"
--> /X:vCloudKeepTemplate = "true"
--> /X:vCloudTimeout = "3600"
--> /X:vimSessionTimeout = "600"
--> /authdPortSource = "902"
--> /authdPortTarget = "902"
--> /datastore = "cisvlcloud na2"
--> /diskMode = "thin"
--> /fencedMode = "bridged"
--> /name = "dev"
--> /net/eth0 = "VM Network"
--> /noSSLVerify = "true"
--> /powerOn = "true"
--> /prgPath = "C:\Progra~1\VMware\VMware_OVF_Tool"
--> /source = "z:\on\dev.ova"
--> /target = "vi://admin:password@dns.address.com"
--> /vCloudTemplate = "false"
-->
2013-04-29T04:47:37.888-07:00 [02188 verbose 'Default'] Done initializing libs
2013-04-29T04:47:37.888-07:00 [02188 verbose 'Default'] Determining source
2013-04-29T04:47:37.888-07:00 [02188 verbose 'Default'] Determining target
2013-04-29T04:47:37.888-07:00 [02188 verbose 'Default'] Backtrace:
--> backtrace[00] rip 00bae353
--> backtrace[01] rip 00ab00be
--> backtrace[02] rip 00ab1311
--> backtrace[03] rip 00a724fa
--> backtrace[04] rip 0040ea83
--> backtrace[05] rip 004c19c0
--> backtrace[06] rip 00421493
--> backtrace[07] rip 00421af8
--> backtrace[08] rip 00442dd9
--> backtrace[09] rip 0040e54a
--> backtrace[10] rip 00419ad8
--> backtrace[11] rip 0041a9c4
--> backtrace[12] rip 00628faf
--> backtrace[13] rip 77e523dd
-->

 

and then if fails.  I'm not sure why this is happening from my another machine.  I have the same thing running fine from my Win 7 machine.

 

Any help on why this is happening?

 

-Mahesh


How to start machine after OVF export?

$
0
0

I'm running OVF tool to export a running virtual machine (ESXi 5.0) from a command line. One of the options is shutting down the virtual machine before the export that works fine. Is there an option to start this machine automatically after the export?

 

Thanks a lot!

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?

OVFtool error - Line 38: Unsupported value '16' for element 'VirtualQuantity'.

$
0
0

Hi Guys,

 

I'm getting the below error when using the OVFtool to convert an OVA file to VMX.

 

Error:

- Line 38: Unsupported value '16' for element 'VirtualQuantity'.

- Virtual machine has 16 virtual CPUs, but the host only supports 8. The number of virtual CPUs may be limited by the guest OS selected for the virtual machine or by the licensing for the host.

 

I am trying to solve it using the syntax option --viCpuResource=<shares>:<reservation>:<limit>

 

However I don't know what to denote in the placeholder <shares>

 

I have also read the OVFtool user guide, but it does not give any info on the viCpuResource option.

 

Can anyone give me some guidance here?

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

ovftool fails to deploy vApp (containing 12VMs) with its ova file while vsphere client GUI works

$
0
0

We found ovftool fails to deploy a vApp instance, within which 12VMs are to be created, from an ova file, while it succeeds if the ova file contains a slimmer version ovf file (VMs' no is decreased to 8). The host where ovftool runs is in the same LAN with VCenter server so network is probably not a problem. Besides, it also succeeds to deploy the package.ova file using VSphere Client GUI.


ovftool --X:logToConsole --noSSLVerify --name=DBaaS-fail --vmFolder=BuildValidation --powerOffTarget --overwrite '--net:VMNetwork=VLAN138' --datastore=store1800-1 --diskMode=thin

--prop:BaseIP=ww.xx.yy.zz --prop:Netmask=255.255.255.128 --prop:Gateway=ww.xx.yy.253 '--prop:DNS_Servers=10.132.71.1 10.132.71.2' --acceptAllEulas --powerOn /mnt/DATA/release/XXXXX/ova-demo/package.ova vi://user:password@10.ab.cc.dd/vCHS-DBaaS/host/ALMA/Resources/BuildValidation

 

The progress bar indicating complete percentage never shows up for the 12VM-version's deployment. The verbose log shows that the upload never starts. Has anybody encountered this issue? And you'll be appreciated if you can give us a hand. And we are willing to provide our ova file to troubleshooting this issue.


Background

We generate an OVA file which contains multiple VMs. Every VM specified in the ovf file refers to either a Linux vmdk or a Win vmdk within the OVA file. With two vmdk files contained in the ova file, the file size is almost 3G. We used the above command to deploy an vApp instance, but it always fail.

 

The following are what we have tried.

- The machine to run ovftool always keeps in the same LAN as VCenter server. This ensures network low latency.

- We tried ovftool both with its linux's version and windows's version. Deploying the ova containing 12VMs, always fail; deploying the slimmer version with 8VMs, it works;

- The difference between 12VM and 8VM ovafiles are very simple: both has two vmdk files, file-size are almost the same(~3G). It's just the latter ovf file choose to generate small number of homogenous VMs.

 

The verbose logs are attached below.

 

ovftool --X:logToConsole --noSSLVerify --name=DBaaS-fail --vmFolder=BuildValidation --powerOffTarget --overwrite '--net:VMNetwork=VLAN138' --datastore=store1800-1 --diskMode=thin

--prop:BaseIP=ww.xx.yy.zz --prop:Netmask=255.255.255.128 --prop:Gateway=ww.xx.yy.253 '--prop:DNS_Servers=10.132.71.1 10.132.71.2' --acceptAllEulas --powerOn /mnt/DATA/release/XXXXX/ova-demo/package.ova vi://user:password@10.ab.cc.dd/vCHS-DBaaS/host/ALMA/Resources/BuildValidation

ŠŠŠŠŠŠŠŠ.

-->

Opening VI target:

vi://root@10.146.25.129:443/vCHS-DBaaS/host/ALMA/Resources/BuildValidation

2014-01-17T08:15:55.791Z [7FCDED7D2740 verbose 'Default'] Hostsystem used

as deploy target: vim.HostSystem:host-16

Deploying to VI:

vi://root@10.146.25.129:443/vCHS-DBaaS/host/ALMA/Resources/BuildValidation

2014-01-17T08:16:24.172Z [7FCDED7D2740 verbose 'Default'] Using file size

as progress measure

2014-01-17T08:16:24.189Z [7FCDE4FB0700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.190Z [7FCDE416F700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.190Z [7FCDE412E700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.190Z [7FCDE40ED700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.191Z [7FCDE40AC700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.192Z [7FCDE406B700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.192Z [7FCDBFFFF700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.195Z [7FCDE4FB0700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.197Z [7FCDE416F700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.197Z [7FCDE412E700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.197Z [7FCDE40ED700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.198Z [7FCDE40AC700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.199Z [7FCDE406B700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.199Z [7FCDBFFFF700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:42.512Z [7FCDBFF7D700 verbose

'HttpConnectionPool-000001'] [RemoveConnection] Connection removed; cnx:

<SSL(<io_obj p:0x00007fcde0014b00, h:-1, <TCP '0.0.0.0:0'>, <TCP

'10.146.25.129:443'>>)>; pooled: 0

work@boxbuilder:~$ lsof -i TCP

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

ovftool.b 31731 work 7u IPv4 574157 0t0 TCP

10.146.25.131:33750->10.146.25.129:https (ESTABLISHED)

ovftool.b 31731 work 9u IPv4 575678 0t0 TCP

10.146.25.131:33752->10.146.25.129:https (ESTABLISHED)

ovftool.b 31731 work 10u IPv4 574954 0t0 TCP

10.146.25.131:57555->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 11u IPv4 574159 0t0 TCP

10.146.25.131:57556->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 12u IPv4 576636 0t0 TCP

10.146.25.131:57557->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 13u IPv4 574955 0t0 TCP

10.146.25.131:57558->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 14u IPv4 574160 0t0 TCP

10.146.25.131:57559->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 15u IPv4 576637 0t0 TCP

10.146.25.131:57560->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 16u IPv4 574956 0t0 TCP

10.146.25.131:57561->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

I HAVE a query can we install vSphere ESXi 4.1 U3 and ESXi 5.5 in HA cluster vCenter 5.5.

$
0
0

I HAVE a query can we install vSphere ESXi 4.1 U3 and ESXi 5.5 in HA cluster vCenter 5.5.

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

The OVF descriptor file could not be parsed.

$
0
0

Hi All,

 

    I have just exported an vApp using ovf from my vCenter v4u2. When I try to import into Vmware Workstation 7.1(running on Window 7 Ent 64bit) I get the following error message "The OVF descriptor file could not be parsed."  I have attached the log.

 

 

Cheers!

OVA vs OVF in ovftool

$
0
0

Hi all,

I am trying to implement an OVF support for some virtualization software, which is using raw images for disks. I use qemu-img to convert raw images to vmdk format. Then I use ovftool to convert ovf file into vmware instance.

When the file I have is a simple ovf descriptor + manifest + disk - all is fine, it works even if I'm using qemu-img without "compat6" option

When the disk is compressed or the OVF package is packed into OVA - there are errors being thrown. Moreover when I create OVA package with no disk, the conversion works.

 

Here is the fragment of results for the OVA file:

 

Writing VMX file: test_ova.vmx
[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Using file size as progress measure
Disk progress: 0%[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Ovf::GetFileSource as StreamVmdk failed. Exception: Cannot open disk source: Not a supported disk format (sparse VMDK version too old)
Disk Transfer Failed                      
Error: Failed to open source disk: 3f66f54d-a9fa-4aa8-806d-d757d6f34a59.disk0.vmdk
[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Backtrace:
[00] rip 00007f09767453e4 
[01] rip 00007f09765e99d4 
[02] rip 00007f097658e038 
[03] rip 00000000004fef51 
[04] rip 000000000054aaa5 
[05] rip 000000000054ae78 
[06] rip 000000000049c41a 
[07] rip 00007f0974e62c4d 
[08] rip 000000000047ec7a 

[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Deleting file: ./test_ova-disk1.vmdk

 

Same fragment when I unpack OVA and then run ovftool on the .ovf file:

 

Writing VMX file: test_ovf.vmx
[2011-10-03 16:35:53.934 7F7E899C4720 verbose 'ovftool'] Using file size as progress measure
Disk progress: 0%[2011-10-03 16:35:53.935 7F7E899C4720 verbose 'ovftool'] Ovf::GetFileSource as StreamVmdk failed. Exception: Cannot open disk source: Not a supported disk format (sparse VMDK version too old)
Disk progress: 99%[2011-10-03 16:35:54.106 7F7E899C4720 verbose 'ovftool'] Ovf::GetFileSource: Opened 3f66f54d-a9fa-4aa8-806d-d757d6f34a59.disk0.vmdk as diskLib source
[2011-10-03 16:35:54.106 7F7E899C4720 verbose 'ovftool'] Opening disk target /xcinstall-1.corp.google.com/VirtualLsiLogicController0:0
Disk Transfer Completed                   
Completed successfully
Can someone please explain to me, what is happening?
I am using python's tarfile to create OVA, if this may be of importance (although I doubt that, since it works with diskless OVA),
my qemu-img version used in this example was 0.12,
I used ovftool in version 2.0.0.

Thank you.

Convert ovf template to vsx

$
0
0

Hello ,

I used the vcenter 4.1 console to Export OVF Template.  We need to be able to load this template in vmware player.  I downloaded ovftool and tried to convert the OVF template so that it could be run in Vmware player.

 

 

This is the command I am issuing to convert the template based off of the OVFTOOL PDF.  This, to my understanding should convert the OVF to a VMX and drop it in the D:\vms folder.  There are 4 disks in this VM server

 

Input

C:\Program Files\VMware\VMware OVF Tool>ovftool -tt=vmx D:\server_name\server_name.ovf D:\vms\

 

Output:

 

Opening OVF source: D:\server\server.ovf
The manifest validates
Opening VMX target: D:\vms\
Warning:
- Target does not support CPU validation.
Error:
-
Completed with errors

 

Needless to say the VMS folder is getting created but nothing else is being converted. 

 

Any help would be greatly appreciated.

 

Thanks,

 

DS

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

Could not look up host [username]. Proper password, but will not convert

$
0
0

Hey all. I know I am using proper syntax, but it seems like there's a missing service running on my esx cluster. I am able to log in with vSphere, but cannot use ovftool to export a stopped server in my ESX 4.0 cluster environment.

 

command I am using:

 

ovftool vi://[username]:[password]@vi://192.168.77.111/[serverid] d:\[serveridoutput].ovf

 

the error I am receiving is as follows:

 

Error: Could not lookup host: [username]

Completed with errors

 

 

Now it's interesting because the server does seem to know that I am using a proper user/pass because if I make a mistake on the password, I am given another chance to log in, until I miss three tries. If I enter the correct password, it seems to almost connect, then fails out with the above error. I would *REALLY* appreciate some help with this guys.

 

Thanks in advance!

Converting OVF file using ovftool from VirtualBox produces error "Line 39: Unsupported element 'Caption'" and many more errors

$
0
0

Hi,

 

I would like to convert VirtualBox 3.2.4 virtual machine to VMWare ESX 4.0.

 

In VirtualBox I have exported appliance to 0.9 format and then follow the following tutorial: http://www.ctrip.ufl.edu/howto-convert-virtualbox-to-vmware

 

 

 

 

 

 

When executing command "ovftool my.ovf my.vmx" I got the following error:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Opening OVF source: e:\VMW\my.ovf

Warning: No manifest file

Opening VMX target: e:\VMW\my.vmx

Error:

 

 

 

 

 

  • Line 39: Unsupported element 'Caption'

  • Line 40: Unsupported element 'Description'

  • Line 41: Unsupported element 'InstanceId'

  • Line 42: Unsupported element 'ResourceType'

  • Line 43: Unsupported element 'VirtualQuantity'

  • Line 37: Missing child element 'InstanceID'.

  • Line 37: Missing child element 'ResourceType'.

  • Line 48: Unsupported element 'Caption'

  • Line 49: Unsupported element 'Description'

  • Line 50: Unsupported element 'InstanceId'

  • Line 51: Unsupported element 'ResourceSubType'

  • Line 52: Unsupported element 'ResourceType'

  • Line 45: Missing child element 'InstanceID'.

  • Line 45: Missing child element 'ResourceType'.

  • Line 57: Unsupported element 'Caption'

  • Line 58: Unsupported element 'Description'

  • Line 59: Unsupported element 'InstanceId'

  • Line 60: Unsupported element 'ResourceSubType'

  • Line 61: Unsupported element 'ResourceType'

  • Line 54: Missing child element 'InstanceID'.

  • Line 54: Missing child element 'ResourceType'.

  • Line 65: Unsupported element 'Caption'

  • Line 66: Unsupported element 'Connection'

  • Line 67: Unsupported element 'InstanceId'

  • Line 68: Unsupported element 'ResourceSubType'

  • Line 69: Unsupported element 'ResourceType'

  • Line 63: Missing child element 'InstanceID'.

  • Line 63: Missing child element 'ResourceType'.

  • Line 74: Unsupported element 'Caption'

  • Line 75: Unsupported element 'Description'

  • Line 76: Unsupported element 'InstanceId'

  • Line 77: Unsupported element 'ResourceType'

  • Line 71: Missing child element 'InstanceID'.

  • Line 71: Missing child element 'ResourceType'.

  • Line 81: Unsupported element 'AutomaticAllocation'

  • Line 82: Unsupported element 'Caption'

  • Line 83: Unsupported element 'Description'

  • Line 84: Unsupported element 'InstanceId'

  • Line 85: Unsupported element 'ResourceSubType'

  • Line 86: Unsupported element 'ResourceType'

  • Line 79: Missing child element 'InstanceID'.

  • Line 79: Missing child element 'ResourceType'.

  • Line 90: Unsupported element 'Caption'

  • Line 91: Unsupported element 'Description'

  • Line 92: Unsupported element 'HostResource'

  • Line 93: Unsupported element 'InstanceId'

  • Line 94: Unsupported element 'Parent'

  • Line 95: Unsupported element 'ResourceType'

  • Line 88: Missing child element 'InstanceID'.

  • Line 88: Missing child element 'ResourceType'.

  • Line 99: Unsupported element 'AutomaticAllocation'

  • Line 100: Unsupported element 'Caption'

  • Line 101: Unsupported element 'Description'

  • Line 102: Unsupported element 'InstanceId'

  • Line 103: Unsupported element 'Parent'

  • Line 104: Unsupported element 'ResourceType'

  • Line 97: Missing child element 'InstanceID'.

  • Line 97: Missing child element 'ResourceType'.

 

 

Please see attached ovf file.

 

 

 

What should I do? 

 

 

 

 

 

 

Thanks

What is the EULA character limit?

$
0
0

 

I'm using the OVF 1.0 tool to create a package for deployment to customers.  Included in my command is the --eula@=eulatext.txt  parameter.  When I use this parameter, the tool spends the requisite hour or two to extract and compress the virtual disk drive, but it doesn't create an OVF or MF file.  Without the --eula@= parameter, the OVF and MF files are created as expected.

 

 

Through trial and error, I've determined that the OVF 1.0 tool imposes a character limit in the contents of the text file I'm using.  When I cut about half of the EULA text, use of the --eula@= parameter works as expected.  (An error message from the tool would have saved me quite a bit of time determining this.  Checking this before the virtual disks are processed would also have saved hours.)

 

 

This is a legal concern.  I need to provide documentation of the character limit to my organization as justification for truncating our EULA.  Does anyone know where VMware or DMTF document this character limit?  I've been unable to locate it.

 

 


How to create VM without OVFtool in ESX 3.5?

$
0
0

 

Hi,

 

 

  Now I have a problem with OVFtool. I want to create a virtual machine on an ESX 3.5 server, but i don't want to use the OVF tool and the VI client. I know that there is a managed object called "OvfManager" in the VMWare API, but this object is supported only by vSphere 4.0 and higher. Is there any method that I can use the API to create the VM from the OVF file, without using the OVFtool? Thanks.

 

 

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

 

 

ovftool "locator does not refer to an object"

$
0
0

I am trying to create an OVF from a vm in vsphere - I'm running ovftool on a linux machine, and using the following syntax (I got this from the ovftool users guide):

ovftool username@myvcenter.aaa.com/"datacenter name"/vm/vmname /local/path/tostoreit/vnname.ovf

It prompts for a password, I enter the password, and it comes back with:

Opening VI source: vi://username@myvcenter.aaa.com/datacenter name/vmname
Error: Locator does not refer to an object:vi://username@myvcenter.aaa.com/datacenter name/vmname

 

Incidentally, I get the exact same error when I try using the mac version of ovftool, and the windows version.

Please help - I know this should work. I have no idea what I'm doing wrong, but I have to get this working pretty fast.

Thank you!!

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.

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

Viewing all 34499 articles
Browse latest View live


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