I'm trying to settup a vApp with one VM via the Java SDK api, how can this be achieved?

I have thried :

Only the computer name is updated correctly but the Virtual Machine name is not...which setting is the right one?

I'm posting also a picture of the deployed VM to see what am I trying to change

Hey,

Is anybody aware of what network flows exist when deploying an ovf file using ovftool through a vCenter?  Right now ovftool is continually erroring out with the following message:

Transfer Failed                      
Error: Network connection was lost.
Completed with errors

When watching on the vCenter I can see that the virtual machine is created but then it looks like data is never actually transferred.  So I know that the initial connection to vCenter is successful.

I'm guessing the initial connection happens with vCenter and then the data transfer occurs directly with the ESX.  Would be very appreciative if somebody could confirm this and identify the port that the data transfer happens on.

Thanks,

-Chris

Hi Guys,

I'm trying to use the below command using ovftool and have not been successful

ovftool vi://user:pass@localhost?moref=vim.vm.VirtualMachine:<VM GuestName>.

every time I receive the message "vmodl.fault.ManagedObjectNotFound".  How to query using moref using VM Guest name.

like when I do  "ovftool vi://user:pass@localhost" -  I receive the details about the VM Guests.

-Mahesh

I have created my own OVF discriptor XML file for creating Logical Partations on systems and installing OS on the created Virtual machines.But I m facing problem in specifying the Disk Section attributes such as OVF:diskid, OVF:href and other details in my OVF xml file.I mean I m unable to find any clue regarding specifying the raw OS information in OVF file ,so that while deploying the OVF into managed systems ,it automatically picks up the os image from the NIM repository.

Thanks in advance .....

I'm trying to use ovftool to automate OVA deployments to vCloud Director 5.1. I have installed ovftool 3.0.1 on Ubuntu and tested out some operations. Everything seems to work except that I always get a segmentation fault when I invoke a vcloud target.

Here is the logging output:

2013-04-12T09:38:22.261-07:00 [7F987B01E740 verbose 'Default'] [SSL_DB] Using /home/evan/.ovftool.ssldb as SSL DB
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 2 (SIGINT)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 4 (SIGILL)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 6 (SIGABRT)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 8 (SIGFPE)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 15 (SIGTERM)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 1 (SIGHUP)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 3 (SIGQUIT)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 5 (SIGTRAP)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 9 (SIGKILL)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Subscribing to signal: 13 (SIGPIPE)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] OvfTool Version: VMware ovftool 3.0.1 (build-801290)
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] Using home directory: /home/evan/.ovftool
2013-04-12T09:38:22.263-07:00 [7F987B01E740 verbose 'Default'] OvfTool Environment:
--> /X:httpTimeout = "0"
--> /X:imageReadSize = "262144"
--> /X:logToConsole = "true"
--> /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"
--> /fencedMode = "bridged"
--> /prgPath = "/usr/lib/vmware-ovftool"
--> /source = "vcloud://vclouddirector.intapp.net/"
--> /vCloudTemplate = "false"
-->
2013-04-12T09:38:22.270-07:00 [7F987B01E740 verbose 'Default'] Done initializing libs
2013-04-12T09:38:22.270-07:00 [7F987B01E740 verbose 'Default'] Determining source
2013-04-12T09:38:22.270-07:00 [7F987B01E740 verbose 'Default'] Determining target
2013-04-12T09:38:22.302-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.617-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.617-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.617-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.617-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.617-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.617-07:00 [7F986BFFF700 verbose 'Default'] CURL: header data removed
2013-04-12T09:38:22.619-07:00 [7F987B01E740 verbose 'Default'] VCloud request body:
-->
2013-04-12T09:38:22.641-07:00 [7F987B01E740 verbose 'Default'] VCloud response body:
--> <?xml version="1.0" encoding="UTF-8"?>
--> <SupportedVersions xmlns="http://www.vmware.com/vcloud/versions" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.vmware.com/vcloud/versionshttp://vclouddirector/api/versions/schema/versions.xsd">
-->     <VersionInfo>
-->         <Version>1.5</Version>
-->         <LoginUrl>https://vclouddirector.intapp.net/api/sessions</LoginUrl>
   ... schema output snipped ...
-->
2013-04-12T09:38:22.648-07:00 [7F987B01E740 verbose 'Default'] VCloud version used: 5.1

The end of the strace output:

[pid 15407] munmap(0x7f8b32f7c000, 135168) = 0
[pid 15407] munmap(0x7f8b32f9d000, 135168) = 0
[pid 15407] munmap(0x7f8b3cadb000, 135168) = 0
[pid 15407] write(6, "\25\3\1\0\30B& 2\7\30\3259W0n~(4\216\375\"\35\310c\211{+\350", 29) = 29
[pid 15407] close(6)                    = 0
[pid 15407] brk(0x2c17000)              = 0x2c17000
[pid 15407] brk(0x2c38000)              = 0x2c38000
[pid 15407] write(1, "2013-04-12T09:40:54.198-07:00 [7"..., 882013-04-12T09:40:54.198-07:00 [7F8B3CB7F740 verbose 'Default'] VCloud version used: 5.1
) = 88
[pid 15407] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
Process 15404 resumed
Process 15407 detached
[pid 15410] +++ killed by SIGSEGV (core dumped) +++
[pid 15409] +++ killed by SIGSEGV (core dumped) +++
[pid 15408] +++ killed by SIGSEGV (core dumped) +++
[pid 15411] +++ killed by SIGSEGV (core dumped) +++
<... wait4 resumed> [{WIFSIGNALED(s) && WTERMSIG(s) == SIGSEGV && WCOREDUMP(s)}], 0, NULL) = 15407
write(2, "/usr/bin/ovftool: line 23: 15407"..., 91/usr/bin/ovftool: line 23: 15407 Segmentation fault      (core dumped) "$OVFTOOL_BIN" "$@"
) = 91
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
--- SIGCHLD (Child exited) @ 0 (0) ---
wait4(-1, 0x7fff27453e98, WNOHANG, NULL) = -1 ECHILD (No child processes)
rt_sigreturn(0xffffffffffffffff)        = 0
rt_sigaction(SIGINT, {SIG_DFL, [], SA_RESTORER, 0x7f70fceb44a0}, {0x43f140, [], SA_RESTORER, 0x7f70fceb44a0}, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
read(255, "", 409)                      = 0
exit_group(139)                         = ?

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.

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

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

I have a setup where I am accessing vCenter and an ESXi host through a NAT layer. If I try to deploy directly to vCenter, ovftool automatically tries to connect to the ip address of the ESXi host behind the NAT layer, which fails.

It looks something like this:

[root@ovfimporter mnt]# date; ovftool --datastore="PayGo Storage" --net:"VLan 4=DedicatedPortGroup_NNNN" CUST/CUST.ovf vi://matthew.wallace@10.10.10.1/Customer\ Datacenter/host/PayGo\ Cluster/Resources/Paygo/NNNN\ \(abc44060-35dc-438a-8c79-6bc7586082ab\)/ ;date

Tue Oct  8 10:18:43 MDT 2013

Opening OVF source: CUST/CUST.ovf

The manifest validates

Enter login information for target vi://10.10.10.1/

Username: matthew.wallace

Password: *********

Opening VI target: vi://matthew.wallace@10.10.10.1:443/Customer%20Datacenter/host/PayGo%20Cluster/Resources/Paygo/NNNN%20(abc44060-35dc-438a-8c79-6bc7586082ab)/

Deploying to VI: vi://matthew.wallace@10.10.10.1:443/Customer%20Datacenter/host/PayGo%20Cluster/Resources/Paygo/NNNN%20(abc44060-35dc-438a-8c79-6bc7586082ab)/

Transfer Failed

Transfer Failed

Error: Lost connection to target

Completed with errors

Tue Oct  8 10:20:19 MDT 2013

Looking at netstat, I saw a hung connection to 443 of one of the ESX hosts in that PayGo Cluster:

In this case, 172.17.0.10 is the "real" IP of one of the esx hosts in the PayGo cluster managed by that vCenter, which I can reach from the client running the ovftool only by using the NAT ip of 10.10.10.100.

So, I tried to specify the external ip of that host. Per the ovftool 3.5 user guide:

Given that, I tried using several syntaxes:

ovftool --datastore="PayGo Storage" --net:"VLan 4=DedicatedPortGroup_NNNN" CUST/CUST.ovf vi://matthew.wallace@10.10.10.1/Customer\ Datacenter/host/PayGo\ Cluster/Resources/Paygo/NNNN\ \(abc44060-35dc-438a-8c79-6bc7586082ab\)/?ip=10.10.10.100

or even just the simplest version to see if I can get a prompt for going further down in the locator tree:

ovftool --datastore="PayGo Storage" --net:"VLan 4=DedicatedPortGroup_NNNN" "vi://matthew.wallace@10.10.10.1/?ip=10.10.10.100"

I invariably get a result like this:

The manifest validates

Enter login information for target vi://10.10.10.1/

Username: matthew.wallace

Password: *********

Error: Locator does not refer to an object: vi://matthew.wallace@10.10.10.1:443/?ip=10.10.10.100

Completed with errors

Outside of the brief mention of the "ip=xxx" param mentioned in the ovftool userguide I've been unable to find any reference to someone successfully using this parameter so I'm uncertain if this is a bug, my not understanding the intention of the parameter as specified in the OVF tool guide, or me using bad syntax.

We are excited about this new community and welcome all to participate and discuss OVF Tool topics.

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 &lt;source locator&gt; &lt;destination locator&gt;" 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

I use ovftool to deploy an appliance to a host (esx 3.5i). after disk copy done, I got an error message and the tool core dumped.

What does the message means ?

Thanks in advance.

Opening OVF source: /home/luger_lee/tmpout/VMware-VIPerl-Toolkit-1.6.0-104313-Appliance/VMware-RCLI-3.5-U2-Appliance.ovf

Warning: No manifest file

Opening VI target: vi://root@alaska/

Target: vi://alaska/

Disk progress: 1%

...

Disk progress: 99%

Disk Transfer Failed           

Error: Unable to get NFC ticket for target disk

Error: Failed to clean up after failure. Reason: vim.fault.NotAuthenticated

terminate called after throwing an instance of 'Vim::Fault::NotAuthenticated::Exception'

  what():  vim.fault.NotAuthenticated

Terminate process signal received - aborting operation/usr/bin/ovftool: line 23: 32361 Aborted                 (core dumped) $OVFTOOL_BIN "$@"

I recieve the following error "- Unsupported hardware version: 3". Please assist. Converting a vmx to a ovf. Recieve error when vmx file is opened.

I am trying to import OVF with custom propery set and getting folling error with vmware ovf tool. Any idea on how to resolve this issue?

Error:

- Line 107: Unsupported element 'Property'

This is driving me crazy! How do you specify which datastore to use when there are multiple?

I ran exactly the same command on a box that had one datastore and it worked fine (as expected). It created the VM folder in the root of the DS and then pulled across the VM from the OVF. However with multiple it just says no target datstore specified. I've tried a million combinations of ?-ds= with square brackets, without. Sometimes it says not found in inventory. I guess it's looking for a folder. But surely this can't be that hard?

C:\Program Files\VMware\VMware OVF Tool&gt;ovftool P:\Downloads\PanoManagerVM-2.8.0

-ovf\panomanager.ovf "vi://root@192.168.1.5

Opening OVF source: P:\Downloads\PanoManagerVM-2.8.0-ovf\panomanager.ovf

Warning: No manifest file

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

Username: root

Password: *********

Opening VI target: vi://root@192.168.1.5/

Error: No target datastore specified

Datastores found on target:

  SAN Storage

  storage1

I have exported an VM to an ovf and put it in a folder on a 2003 windows server.  I then created a web folder in IIS 6, and turned on folder browsing.  When I put the url path in vSphere to import the ovf, I get a 404 error from IIS.  Is there a way to publish an ovf to IIS6? 

Thanks in advance,

geob

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.

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

Hello,

I'm attempting to do a vmware to ovf converstion.  However, I'm receiving some fairly generic errors from ovftool and was hoping I could get some help.

Here are the console messages when I attempt to convert:

[root@provisionvrpt ~]# /usr/bin/ovftool --machineOutput --X:logToConsole=true /var/lib/vmware/Virtual\ Machines/vm/test.vmx /var/lib/vmware/Virtual\ Machines/vmovf/test.ovf
[2011-08-16 00:42:55.990 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 2 (SIGINT)
[2011-08-16 00:42:55.990 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 4 (SIGILL)
[2011-08-16 00:42:55.990 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 6 (SIGABRT)
[2011-08-16 00:42:55.990 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 8 (SIGFPE)
[2011-08-16 00:42:55.990 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 15 (SIGTERM)
[2011-08-16 00:42:55.990 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 1 (SIGHUP)
[2011-08-16 00:42:55.990 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 3 (SIGQUIT)
[2011-08-16 00:42:55.990 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 5 (SIGTRAP)
[2011-08-16 00:42:55.990 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 9 (SIGKILL)
[2011-08-16 00:42:55.991 B7FAC6D0 verbose 'ovftool'] Subscribing to signal: 13 (SIGPIPE)
[2011-08-16 00:42:55.991 B7FAC6D0 verbose 'ovftool'] [ovfTool.cpp] Using home directory /root/.ovftool
[2011-08-16 00:42:55.991 B7FAC6D0 verbose 'ovftool'] [ovfTool.cpp] OvfTool Environment:
/X:fencedMode = "bridged"
/X:imageReadSize = "262144"
/X:logToConsole = "true"
/X:maxNumberOfTermSignals = "5"
/X:maxRedirects = "256"
/X:maximalDeltaConfSize = "8"
/X:maximalDeltaTreeSize = "6"
/X:progressSmoothing = "60"
/X:vimSessionTimeout = "600"
/authdPortSource = "902"
/authdPortTarget = "902"
/machineOutput = "true"
/prgPath = "/opt/vmware/ovftool"
/source = "/var/lib/vmware/Virtual Machines/vm/test.vmx"
/target = "/var/lib/vmware/Virtual Machines/vmovf/test.ovf"

[2011-08-16 00:42:56.000 B7FAC6D0 verbose 'ovftool'] [ovfTool.cpp] Done initializing libs
[2011-08-16 00:42:56.000 B7FAC6D0 verbose 'ovftool'] [ovfTool.cpp] Determining source
[2011-08-16 00:42:56.212 B7FAC6D0 verbose 'ovftool'] [ovfTool.cpp] Determining target
[2011-08-16 00:42:57.488 B7FAC6D0 verbose 'ovftool'] Failed to open disk: /var/lib/vmware/Virtual Machines/vm/test.vmdk
[2011-08-16 00:42:57.488 B7FAC6D0 verbose 'ovftool'] Exception: The specified virtual disk needs repair
Error: Failed to open disk: test.vmdk
[2011-08-16 00:42:57.493 B7FAC6D0 verbose 'ovftool'] Backtrace:
[00] rip 050210b3
[01] rip 04eb6e9e
[02] rip 04e55ec2
[03] rip 081c014b
[04] rip 08310271
[05] rip 08311b54
[06] rip 0831ad24
[07] rip 0831b1f7
[08] rip 0831b74c
[09] rip 081f871a
[10] rip 0816fa45
[11] rip 080cd318
[12] rip 0317be9c
[13] rip 080ae4f1

But when I attempt to repair the disk, I get the following:

vmware-vdiskmanager -R /var/lib/vmware/Virtual\ Machines/vm/test.vmdk
No errors were found on the virtual disk, '/var/lib/vmware/Virtual Machines/vm/test.vmdk'.

Any help would be apprecaited.  Is there a way to increase the verbosity of the logging?

Here is my ovftool version info: VMware ovftool 2.0.1 (build-260188)

Thanks!