Anyone using OVF extensively?

Environment...

ESXi 4 box, with a single very simple VM, just a VM, no disks, nothing more than a VM shell really.

ESXi 3.5 U 4 running a single VM, which has vCenter 4 running in it.  Windows 2008, 32, 1.5GB RAM for VM

Windows XP SP3 fully patched desktop to run OVF CLI tool for Windows and VIClient 4

Attempted...

1) From VI client, try to use GUI to Export OVF Template, VirtualCenter Service stops.

2) From Windows XP SP3 full patched desktop, where Windows OVF1.0 Tool installed, Attempt to do OVF export as attempted above, generates an unexpected exception trap.  vCenter 4 VMware Virtual Center server stops.

C:\Program Files\VMware\VMware OVF Tool>ovftool "vi://administrator@192.168.15.3/Home Office/vm/Test01" ./Test01.OVF

Please enter login information for source vi://192.168.15.3/

Username: administrator

Password: *********

Opening VI source: vi://administrator@192.168.15.3/Home Office/vm/Test01

Error: The specified network name is no longer available.

This application has requested the Runtime to terminate it in an unusual way.

Please contact the application's support team for more information.

Terminate process signal received - aborting operation

C:\Program Files\VMware\VMware OVF Tool>

I have an OVF from VirtualBox that I want to import into VMware Workstation 6.5.2 (linux). The first thing I noticed was that there is no 'Import' option in the File menu of VMware 6.5.2 for linux. So, I ran the ovf file through ovftool. ovftool reported an error when converting:

~/tmp] ovftool foo.ovf ~/tmp/convert/foo.vmx

Opening OVF source: foo.ovf

Warning: No manifest file

Opening VMX target: foo.vmx

Error:

- Line 2: Invalid value '1.0' for attribute 'version' on element 'Envelope'.

~/tmp]

This particular OVF was created with VirtualBox 2.2.4. Both support ovf 1.0, right? Output of line 2 ...

~/tmp] sed -n 2p foo.ovf

Ideas?

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

(Easy) Question… Regarding the use of global configuration file (ovftool.cfg) and local configuration file with OVFTOOL.

Syntax is given only for comments and parameters which are name-value pairs, e.g. datastore=DATASTORE-NAME. 

For a single parameter without a corresponding value, e.g. –acceptAllEulas, should these parameters be expressly set to TRUE?

Or can they simply be present (no equals sign)?  Both styles seem to work properly for --acceptAllEulas option.

Example:  which of the following CFG files shows the expected syntax?   Or are both acceptable?

acceptAllEulas=true

disableVerification=true

quiet=true

datastore=S123D0001

ipAllocationPolicy=fixed

or

acceptAllEulas

disableVerification

quiet

datastore=S123D0001

ipAllocationPolicy=fixed

(Yeah, I know - this question probably is a gimme.    Just curious if there's anything to trip over here. ) 

=cjs

Message was edited by: cjstaples-emc -- sorry, original formatting garbage

Hi to all in the community,

I have some problems configuring a Juniper virtual appliance with a "virtual serial port" in an OVF format. I intend to configure the basic network settings of this appliance through a "virtual serial port" and expect scripts. This is to run on an ESX 4.0.

1/ I tried to convert different configurations of virtual machine (Linux ones) with serial port and virtual serial port (in VMX format from Workstation 6.0) to OVF format in order to check the way the serial port and virtual serial ports are described. For this I used OVFTool 2.0.1 and VMWare vCenter Converter Standalone 4.0.1. I can not get any information regarding the serial ports or the virtual serial ports whatever the original configuration (VMX) and whichever tool is use. Could anybody provide some help or light regarding this?

2/ Is there a specific way to describe serial ports and virtual serial ports in the OVF descriptor? I didn't find anything relevant in the DMTF document DSP0243_1.1.0.pdf!

3/ In general, how can I get my appliance loading properly on my ESX server with a virtual serial port without touching vSphere and before powering it on automatically?

Thanks in advance to those who can help.

Chris

Is there a way to map network devices that are both associated with "VM Network" in the ova to different networks on the target?  The ova contains only "VM Network", but I would like to put one interface on "NET_A" and one on "NET_B".

Hi,

I am using the ovftool v2.0.1 64bit to automatically create the OVA files from the virtual machines created by the workstation 7.1 and have two big problems:

• The ovftool don't know the gestos = "windows7-64" in the vmx file.
  • It encode it to <OperatingSystemSection ovf:id="1" vmw:osType="*winVista64Guest">.
  • Using the ovftool to create the virtual machine from this ova package create vmx file with guestos = "other" (32bit OS). The virtual machine doesn't work before the OS type is not changed to the 64bit win7
  • Using the guestos = "winvista-64" in vmx file is the workaround but I want to see support for win7 x64bit OS, please.
• Using the ovftool with mapped network discs on Win7 is nightmare when encoding or decoding the OVA file with compress option. The speed is about 1MB/s when the target is on mapped network disk. Tested in more environment with same results.
  The virtual drive size before compression (vmdk file) is about 12GB and the size after compression is about 5-6GB (ova package).
  The OS installed in virtual drive is Win7 64b.
  I am using parameter "--compression=9" when creating the ova package.

Do you have any solution for these problems. especially for the second one, please?

Hello,

I am brand new to the OVF Tool and am currently reading the documentation and experimenting with the utility.

I would like to know if the OVF Tool is a good utility for performing VM backups (copies) in a vSphere environment.

It is not clear, if that is one of the intended uses of the OVF Tool.

How would one accomplish this (backup and restore later) with the OVF Tool command line utility?

1)  Convert vmx config file to ovf (what happens to the original vmx file and the vmdk, vmxf, nvram, etc... files?)

Once you have an ovf package, what is the best way to import it (restore the VM)?  If you use the "Deploy OVF Template" feature in vSphere client, does it launch a wizard that prompts you for all the required meta configuration?  Do you need to remember certain config settings from when you created the OVF package?

Thanks for any insight as I come up to speed with the OVF Tool.

Thanks,

Bryan

I recently had an issue where I exported a VM as an OVF using the vSphere client, a few weeks later I needed to import the VM back into our environment and after importing I received an "Error loading Operating System" error.  I have imported and exported countless VMs as OVF files, and this is very frustrating.  I also have VMs sent to me from Government entities and I always express how they should send them as an OVF file since it makes it very easy for me to import.  Recently I had 1 out of 3 errors after the import with the same "Error loading Operating System" message.

I have tried to change the HD controller on the VM, I also created a New VM with the "custom" option and I chose the exact OS and vHardware for the VM, and I tried to use the existing .vmdk files and that does not work.  I'm just wondering if there is some simple fix out there for what I thought was a simple import and export.

I'm using ESXi 4.1 Update 2 on HP BL hardware...oh, I also have VMware Workstation 8, and I can mount the vmdk files.

Was giving an SSL error, now giving a connecgt error. No firewall involved. I wonder Windows does not have ssh, so, why is vConverter using ssh.

Any help much appreciated.

Hi,

I have an OVF file that refeneces a disk image from a webserver, e.g.:

<File ovf:href="http://myserver/cdrom.iso" ovf:id="file1"/>

When i try to deploy this OVF to a vSphere server, it fails at the disk transfer stage... it looks to me like ovftool is treating it like a local file:

$ ovftool my.ovf vi://root:@172.26.0.172

Opening OVF source: my.ovf

Warning: No manifest file

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

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

Disk Transfer Failed

Error: Failed to open file: cdrom.iso

Here is the output with logging enabled:

When an OVF is deployed from a local file, does it mean the references also need to be local? I had a quick read of the OVF spec and it seems like file reference can be anywhere... local, relative, http or https... any ideas?

Hi- has anyone hit any problems with exporting large (e.g. > 1TB) VMs in OVA/OVF format?

I realise that you can split the files generated, but leaving aside any issues to do with the file-system on which the files reside, are there any inherent gotchas with the export mechanism or the file format that would mean it's not a good idea to rely on this for exporting large VMs...?

Thanks!

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

I give; I have spent too long attempting to find the magic decoder ring to get ovftool to do what I expect to be a very basic use case.

My vCenter server is win2k8 R2 node, my host node is RHEL6.3, and my guest in this case is CentOS6.3.

The vCenter server FQDN is vsphere2.foo.com.

The ESX host is las13.foo.com.

The guest is qavm1.foo.com

The Datacenter name is screwy, but appears to be passable with URI character replacements.  The name is "Foo / Bar Network" so I have been using "Foo %2f Bar Network" and quoting any URL string to deal with the spaces.

Examining the Datacenter layout in vCenter client, the path to the vm from which I want to create an OVA is

Foo / Bar Network/QA Guy/las13.foo.com/qavm1

attempting to use ovftool from either the Win2k8 server or my RHEL6.4 development machine results in the same errors.  I have perturbed the syntax of options and paths in so many ways I don't want to list them all here, but the end result is always an incorrect reference or missing object.

Might I grovel for the proper syntax to store a VM guest as an OVA?

Yes...I have devoured the manual mutiple times over...RTFM is my first tenet

Thank you all!

[root@qavm34 tmp]# ovftool --sourcetype=vmx "vi://administrator@vsphere2.foo.com/Foo %2f Bar Network/host/las13.foo.com"

Error: Unknown option: 'sourcetype'

Completed with errors

[root@qavm34 tmp]# ovftool --sourceType=vmx "vi://administrator@vsphere2.foo.com/Foo %2f Bar Network/host/las13.foo.com"

Error: Failed to open file: vi://administrator@vsphere2.foo.com/Foo %2f Bar Network/host/las13.foo.com

[root@qavm34 tmp]# ovftool --sourceType=vmx "vi://administrator@vsphere2.foo.com/Foo %2f Bar Network/host/las13.foo.com/qavm1"

Error: Failed to open file: vi://administrator@vsphere2.foo.com/Foo %2f Bar Network/host/las13.foo.com/qavm1

[root@qavm34 tmp]# ovftool --sourceType=VI "vi://administrator@vsphere2.foo.com/Foo %2f Bar Network/host/las13.foo.com/qavm1"

Please enter login information for source vi://vsphere2.foo.com/

Username: administrator

Password: **********

Error: Locator does not refer to an object: vi://administrator@vsphere2.foo.com:443/Foo / Bar Network/host/las13.foo.com/qavm1

[root@qavm34 tmp]# ovftool --sourceType=VI "vi://administrator@vsphere2.foo.com/Foo %2f Bar Network/host/las13.foo.com"

Please enter login information for source vi://vsphere2.foo.com/

Username: administrator

Password: *********

Error: Locator does not refer to an object: vi://administrator@vsphere2.foo.com:443/Foo / Bar Network/host/las13.foo.com

[root@qavm34 tmp]# ovftool --sourceType=VI "vi://Administrator@vsphere2.foo.com/Foo %2f Bar Network/host/"

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: **********

Error: Locator does not refer to an object: vi://Administrator@vsphere2.foo.com:443/Foo / Bar Network/host/

[root@qavm34 tmp]# ovftool --sourceType=VI "vi://Administrator@vsphere2.foo.com/Foo %2f Bar Network/host"

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: **********

Error: Locator does not refer to an object: vi://Administrator@vsphere2.foo.com:443/Foo / Bar Network/host

[root@qavm34 tmp]#

[root@qavm34 tmp]#

[root@qavm34 tmp]#

[root@qavm34 tmp]# ovftool --sourceType=VI "vi://Administrator@vsphere2.foo.com/Foo %2f Bar Network"

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: **********

Error: Found wrong kind of object (Datacenter). Possible completions are:

  vm/

  host/

[root@qavm34 tmp]# ovftool --sourceType=VI "vi://Administrator@vsphere2.foo.com/Foo %2f Bar Network/vm/qavm1"

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: **********

Error: Locator does not refer to an object: vi://Administrator@vsphere2.foo.com:443/Foo / Bar Network/vm/qavm1

[root@qavm34 tmp]# ovftool --sourceType=VI "vi://Administrator@vsphere2.foo.com/Foo %2f Bar Network/vm/QA Guy/qavm1"

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: **********

Error: Locator does not refer to an object: vi://Administrator@vsphere2.foo.com:443/Foo / Bar Network/vm/QA Guy/qavm1

[root@qavm34 tmp]# ovftool --sourceType=VI "vi://Administrator@vsphere2.foo.com?moref=vim.vm.VirtualMachine:qavm1"

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: **********

Error: Invalid object type specified (not a ManagedEntity subtype)

[root@qavm34 tmp]# ovftool "vi://Administrator@vsphere2.foo.com?moref=vim.vm.VirtualMachine:qavm1"

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: **********

Error: Invalid object type specified (not a ManagedEntity subtype)

[root@qavm34 tmp]# ovftool "vi://Administrator@vsphere2.foo.com/Foo %2f Bar Network/host/las13.foo.com"

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: **********

Error: Locator does not refer to an object: vi://Administrator@vsphere2.foo.com:443/Foo / Bar Network/host/las13.foo.com

[root@qavm34 tmp]# ovftool "vi://Administrator@vsphere2.foo.com/Foo %2f Bar Network?ds=[EqualLogic] qavm1/qavm1.vmx"

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: *********

Please enter login information for source vi://vsphere2.foo.com/

Username: Administrator

Password: **********

Error: Locator does not refer to an object: vi://Administrator@vsphere2.foo.com:443/Foo %2f Bar Network?ds=[EqualLogic]%20qavm1/qavm1.vmx

[root@qavm34 tmp]# ovftool --version

VMware ovftool 3.0.1 (build-801290)

[root@qavm34 tmp]#

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

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

Something like this I can't get to work:

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

Thanks for any hints,

CJ

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

                <Info>Supported IP assignment schemes</Info>

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

                        <Info>Supported IP assignment schemes</Info>

                </vmw:IpAssignmentSection>

        </Section>

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

                <Info/>

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

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

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

                </Property>

        </Section>

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

                <Info>

            Unknown OVF elements in this element will be passed directly

            to the OVF output descriptor without interpretation

        </Info>

        </Section>

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

                <Info/>

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

Hello There,

OvfTool: 3.0.1

vCloud Director(VCD): 5.1

I use ovftool 3.0.1 to upload an ovf file to VCD and the server return error after upload completely.

It works previously while use ovftool 2.1 with VCD 1.5

I use ovftool 3.0.1 command line to upload template like this:

ovftool --X:logFile=upload.log --machineOutput --powerOn --acceptAllEulas --ipAllocationPolicy=transientPolicy "--net:mynetwork01=mynetwork01" --name=test88t "/tmp/ova/vwin1/vwin1.ovf" "vcloud://xxx:xxx@mynetwork/?org=zhongnan&vappTemplate=test88t&vdc=zhongnan-ALLOC-02&catalog=ISO%20Library" | while read x ; do echo $x; done

The ovf uploaded to VCD is complete, however I got an error result:

<?xml version="1.0" encoding="UTF-8"?>

<InstantiateVAppTemplateParams name="test88t" deploy="false" powerOn="false" xmlns="http://www.vmware.com/vcloud/v1.5"

                               xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1">

  <InstantiationParams>

    <NetworkConfigSection>

      <ovf:Info>Configuration parameters for logical networks</ovf:Info>

      <NetworkConfig networkName="mynetwork">

        <Configuration>

          <ParentNetwork href="https://mynetwork/api/network/xxx-xxx-xxx-xxx"

                         type="application/vnd.vmware.vcloud.network+xml" name="mynetwork-01"/>

          <FenceMode>bridged</FenceMode>

          <AddressingMode>POOL</AddressingMode>

        </Configuration>

        <IsDeployed>true</IsDeployed>

      </NetworkConfig>

    </NetworkConfigSection>

  </InstantiationParams>

  <Source href="https://mynetwork/api/vAppTemplate/vappTemplate-aaa-bbb-ccc-ddd"/>

  <AllEULAsAccepted>true</AllEULAsAccepted>

</InstantiateVAppTemplateParams>

        2013-06-11T04:33:17.786-07:00 [7FA9BA208720 verbose 'Default'] VCloud response body:

        --> <?xml version="1.0" encoding="UTF-8"?>

        --> <Error xmlns="http://www.vmware.com/vcloud/v1.5" minorErrorCode="BAD_REQUEST" message="Bad request

-->  - Unexpected JAXB Exception

-->  - cvc-complex-type.2.4.a: Invalid content was found starting with element 'AddressingMode'. One of '{&quot;http://www.vmware.com/vcloud/v1.5":RetainNetInfoAcrossDeployments,

&quot;http://www.vmware.com/vcloud/v1.5":Features, &quot;http://www.vmware.com/vcloud/v1.5":d, &quot;http://www.vmware.com/vcloud/v1.5":RouterInfo}' is expected."

                   majorErrorCode="400" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

                   xsi:schemaLocation="http://www.vmware.com/vcloud/v1.5http://sd1.aiscloud.net/api/v1.5/schema/master.xsd"></Error>

        -->

        2013-06-11T04:33:17.788-07:00 [7FA9BA208720 verbose 'Default'] Backtrace:

        --> backtrace[00] rip 00007fa9b42a0f44 Vmacore::System::Stacktrace::CaptureWork(unsigned int)

        --> backtrace[01] rip 00007fa9b406bca4 Vmacore::System::SystemFactoryImpl::CreateQuickBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&)

        --> backtrace[02] rip 00007fa9b4001ef8 Vmacore::Throwable::Throwable(std::string const&)

        --> backtrace[03] rip 000000000061e7c1 /usr/lib/vmware-ovftool/ovftool.bin() [0x61e7c1]

        --> backtrace[04] rip 000000000060fca8 /usr/lib/vmware-ovftool/ovftool.bin() [0x60fca8]

        --> backtrace[05] rip 000000000064eb65 /usr/lib/vmware-ovftool/ovftool.bin() [0x64eb65]

        --> backtrace[06] rip 000000000064fd7a /usr/lib/vmware-ovftool/ovftool.bin() [0x64fd7a]

        --> backtrace[07] rip 0000000000569c84 /usr/lib/vmware-ovftool/ovftool.bin() [0x569c84]

        --> backtrace[08] rip 00000000004c4b6e /usr/lib/vmware-ovftool/ovftool.bin() [0x4c4b6e]

        --> backtrace[09] rip 00000000004c7be4 /usr/lib/vmware-ovftool/ovftool.bin() [0x4c7be4]

        --> backtrace[10] rip 00007fa9b1cb1c4d /lib/libc.so.6(__libc_start_main+0xfd) [0x7fa9b1cb1c4d]

        --> backtrace[11] rip 00000000004a2f79 std::basic_streambuf<char, std::char_traits<char>>::xsgetn(char*, long)

Please let me if this is a bug in ovftool to integrate VCD 5.1.

Thanks,

Jeff

OVF Command option:

ovftool.exe "--acceptAllEulas=true" "--name=Robo_Naren_vApp_Temp" "--datastore=fiddleback-esx2:storage1" "-dm=thin" "--network=VM-Network" "C:/appliance-main-image-8.0.0.3.0.ova" "--prop:hostname=naren.am.com" "--prop:ip=10.0.0.xx9" "--prop:netmask=255.255.252.0" "--prop:gateway=x1.3x.2xx.1" "--powerOn" "vi://root:xxxxx@1x.xx.2xx.5x/"

When i try to execute the above command i'm getting the below error.

Error:

Error: Unexpected option: --prop:ip=10.0.0.xx9

Completed with errors

OVF properties

Here's is my ovf content for the properties

      <Property ovf:key="ip" ovf:required="true" ovf:type="string" ovf:userConfigurable="true" vmw:qualifiers="Ip">

        <Label>2. IP Address</Label>

      </Property>

      <Property ovf:key="netmask" ovf:required="true" ovf:type="string" ovf:userConfigurable="true" vmw:qualifiers="Ip">

        <Label>3. Subnet Mask</Label>

      </Property>

      <Property ovf:key="gateway" ovf:required="true" ovf:type="string" ovf:userConfigurable="true" vmw:qualifiers="Ip">

        <Label>4. Default Gateway</Label>

      </Property>

Using  "vSphere Client version 5.1.0"

Can anyone help me in resolving this problem ?

We have a specific folder used for certain vm's that I need to deploy to.


As an example I can view the current list of vm's with:


ovftool vi://myadmin:mypass@ourvcenter/DATACENTER/vm/myvms

Error: Found wrong kind of object (Folder). Possible completions are:
vmname1
vmname2
vmname3
　


Now let’s say I want to import an ovf to myvms/vmname4 I get a "Locator does not refer to an object" error.


ovftool --datastore=mydatastore --network=mynetwork vi://myadmin:mypass@ourvcenter/DATACENTER/vm/myvms/vmname4 newvm.ovf

Opening VI source: vi://myadmin:mypass@ourvcenter/DATACENTER/vm/myvms/vmname4
Error: Locator does not refer to an object: vi://myadmin:mypass@ourvcenter/DATACENTER/vm/myvms/vmname4
Completed with errors


I have tried variations of using —name and —vmfolder and changing the vi: path without success.


I can import directly to esxi and to host through vcenter but we are then having to go back into vcenter to move these vms to the correct folder.


Is there a way to get this into the "right" place up front?

Hi all.  I'm trying to archive some no-longer-used VMs with ovftool, and I've managed to save half of them.  The ovftool output looks like:

wpeters$ ovftool vi://root@zeus/Riverbed/VSH_250m /Volumes/Archive/VSH_250m.ova

Enter login information for source vi://zeus/

Username: root

Password: *********

Opening VI source: vi://root@zeus:443/Riverbed/VSH_250m

Opening OVA target: /Volumes/Archive/VSH_250m.ova

Writing OVA package: /Volumes/Archive/VSH_250m.ova

Transfer Completed                    

Completed successfully


 


The other half of the machines fail with the mysterious vim.fault.FileNotFound without saying which file isn't found.  I've looked at the settings for both successful and unsuccessful VMs and cannot figure out what the difference is:


 

wpeters$ ovftool vi://root@zeus/Riverbed/VSH_markt /Volumes/Archive/VSH_markt.ova

Enter login information for source vi://zeus/

Username: root

Password: *********

Opening VI source: vi://root@zeus:443/Riverbed/VSH_markt

Error: vim.fault.FileNotFound

Completed with errors

HI

I am using a standalone ESXi 5.5

On this I am running 5 vms.

I do not have any resource pool neither I have a vsphere/vcenter server.

Now I want to export one of the vms in ovf format.

What should be my source locator?

I tried using the one below but it does not help.

ovftool vi://user:passwd@10.20.30.40/ha_datacenter/host/my_vm_name  /tmp/myvm.ovf

Error: Locator does not refer to an object: vi://root@10.20.30.40:443ha-datacenter/host/abc.xyz.com/Resources/ha_datacenter/host/my_vm_name

Completed with errors

Thanks in advance,

Sachin