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

Error in uploading to vCloud using ovftool

December 7, 2012, 7:38 pm
$
0
0

Hi,

 

     I try to upload a physical server image to vcloud but it keep returning this error "Invalid response from Server"

 

 

>ovftool -o --net:"bridged=myNetwork" --ipAllocationPolicy=transientPolicy winphysical.ovf "vcloud://username:password@s1.myvcloud.net/?org=MyOrg&vapp=myTest&vdc=MyVDC&catalog=MyCatalog"
Opening OVF source: winphysical.ovf
The manifest validates
Opening vCloud target: vcloud://username@s1.myvcloud.net:443/
Error: Invalid response from server
Completed with errors

 

The ovftool version is 3.01 and the vcloud is 1.5.

I have also attahed the ovf file.

 

 

Thank you.
Regards,

ET Goh

↧
Search

ovftool: Conversion to monolithic sparse image fails with a Vapp ovf file

February 21, 2013, 11:08 pm
$
0
0

Hi,

 

We have been trying to create the monolithicSparse Image for the Vapp Ovf using the following OVF Tool command-Line Options

/usr/bin/ovftool --acceptAllEulas -dm=monolithicSparse Test_Vapp.ovf NEW_Vapp.vmdk

 

But the Ovf tool fails to do the conversion with the following message

Error: OVF Package is not supported by target.

 

We have also tried validating the Vapp ovf file using the ovftool schemaValidate and did not find any issues with this.

 

Please let us know if the Ovf tool supports conversion for multiple virtual machines (i.e support for Vapp OVF)

Thanks in advance

↧
↧

ovftool deploy failing with "Network connection was lost"

February 23, 2013, 8:49 pm
$
0
0

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

↧

How do I set target VM hostname when deploying OVA?

October 2, 2013, 11:23 am
$
0
0

I'm deploying OVA files to a vCenter using ovftool; it's working perfectly, but I want to go the extra mile and automatically set the hostname of the VM after it is deployed.

 

I found a reference to a 'hostname' property (--prop:hostname=myvm.example.com), but it doesn't actually work

 

Here's my command  line

ovftool --lax --acceptAllEulas --datastore=MySAN --overwrite --powerOn --vmFolder=TestFolder --diskMode=thin --powerOffTarget --prop:hostname=myvm.example.comhttp://myurl.com/path/input.ova vi://vcenteruser:password@mycenter.example.com/MyDC/host/MyD/Resources/OVFTest

 

So what is the proper way to do this?

↧

Conversion chart?

July 25, 2014, 10:42 am
$
0
0



Hello, I have been using VMWare for some time now, but new to this conversion tool and vCloud.


My current dilemma is getting a VMWare player VMX converted so I can upload it to vCloud. Seemed straightforward, but every time I convert it and then try to upload it to vCloud, I get 


a virtual system in the ovf file being uploaded requires unrecognized virtual hardware version


I have other platforms to move from as well- I hope this forum will get me where I need to be with those instances, but this error doesn't show when I search the forum. I assume that either I need a switch in there when running ovftool, or you simply can't convert a Player file into an OVF. I am testing the stand-alone convertor, stepping the output file down to VMX-9 to see if this will help.


...I notice there are a lot of questions about getting from one platform and format to another.


Is there no chart somewhere with all of this info in it? That is, FROM platform on X axis, TO platform on Y axis, Yes/no/details/link to more info/etc in cells as appropriate? I was not able to find one.

     Seems like we could use that... I have a very light team running the vCloud and they just aren't there for me with the conversion work I need to do- and that work is essentially all I need to do on the maintenance side of the fence. Plowing through all of the manuals and becoming an expert in what I need to do is also not an option...

↧
↧

ovftool installation requirements

September 22, 2014, 7:07 am
$
0
0



Hello,


I fail to install ovftool on a privately created Linux distribution machine.


The Linux machine is not native Linux and it uses a 32 bit kernel.


The ovftool is used to deploy several OVA images on remote distributed vSphere platforms.


As the ovftool package is provided as a bundle (script+binary) with no source and no specific set of installation requirements


I'd like to know if the list of pre-requirements can be provided.


For instance, I noticed that bash and psutils are required.


There are more requirements which are currently unknown to me and are essential.


As an alternative, is there any other ovftool that can be used to deploy OVA images on vSphere, like SaltStack python API or others ?


Thanks in advance.

↧

OVF Tool memory range error

August 12, 2009, 7:05 am
$
0
0

 

I'm using the ovf tool to convert a virtual appliance to virtual machine format and getting a memory size limitation error based on the OVF source.  The source ovf file specifies 4GB of memory for guest OS:

 

 

Error:

- Virtual machine has 4,096 megabytes of memory, which is outside the range of 4 to 3,600 megabytes supported on the host.  This may be a general limitation of the host software, or specific to the guest OS selected for the virtual machine.

 

 

The work around is to edit the source ovf file and decrease the RAM size to  3 GB and conversion works fine.  But I'm curious why this limitation is occuring.  Is 3,600 MB the maximum virtual memory size supported byVMware workstation or server?

 

 

 

 

 

 

 

 

↧

VMware OVF Tool 2.1.0 is now alive.

August 29, 2011, 7:20 am
$
0
0

Hi All.

 

VMware OVF Tool 2.1.0 is now ready for download.

 

Go to the download link on the frontpage.

 

 

 

Eske

↧
Search

OVFTool cannot set property successfully

September 15, 2011, 2:49 am
$
0
0

I want to set some properties to ovf files.

 

I use ovftool as bellow:

 

ovftool --prop:ip=10.32.23.123 --prop:dns=255.255.254.0

 

when this command has been executed without error showing, I still cannot see the property of ovf files.

 

Then I used ovftool myovffile.ovf

 

I still can not see the property I want to set.

what should I do?

↧
↧

ovftool : Specify Hardware version during a conversion ?

June 20, 2014, 3:27 am
$
0
0



Hi everybody,


I'd like to change the hardware version during an export using ovftool. Is there a way to specify it ?
I've seen the "--maxVirtualHardwareVersion" but I'm unable to understand how to use it. I can't find any documentation on the supported syntax anywhere.


Any advice ?


Jean-Baptiste

↧

vCenter 5 virtual appliance configuration

January 17, 2012, 5:33 am
$
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-

↧

ovftool to VI: "No space left for device '#' on parent controller '#'" for IDE Disks

January 21, 2011, 10:22 am
$
0
0

I have an OVF I'm trying to import into VI (ESX 3.5) and I'm getting the following error:

 

Error: OVF Package is not supported by target:
- Line 57: No space left for device '7' on parent controller '6'.

 

Here's the snippet of OVF:

      <Item>
        <rasd:Address>0</rasd:Address>
        <rasd:ElementName>IDE 0</rasd:ElementName>
        <rasd:InstanceID>6</rasd:InstanceID>
        <rasd:ResourceSubType>piix4</rasd:ResourceSubType>
        <rasd:ResourceType>5</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:AddressOnParent>0</rasd:AddressOnParent>
        <rasd:ElementName>Harddisk disk1</rasd:ElementName>
        <rasd:HostResource>ovf:/disk/disk1</rasd:HostResource>
        <rasd:InstanceID>7</rasd:InstanceID>
        <rasd:Parent>6</rasd:Parent>
        <rasd:ResourceType>17</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:Address>1</rasd:Address>
        <rasd:ElementName>IDE 1</rasd:ElementName>
        <rasd:InstanceID>8</rasd:InstanceID>
        <rasd:ResourceSubType>piix4</rasd:ResourceSubType>
        <rasd:ResourceType>5</rasd:ResourceType>
      </Item>

 

 

Thanks!

Mike

↧

Unsupported element 'Property' from ovftool and ESXi server

July 3, 2012, 8:39 am
$
0
0

I'm trying to use the ovftool to import a OVA file into a ESXi server.  However I get the following error

 

Error: OVF Package is not supported by target:
- Line 118: Unsupported element 'Property'
Completed with errors

 

The related lines in the OVF file are:

    <ProductSection ovf:class="vami" ovf:instance="*******">
      <Info>Information about the installed software</Info>
      <Category>Networking Properties</Category>
118-->      <Property ovf:key="gateway" ovf:type="string" ovf:userConfigurable="true">
        <Label>Default Gateway</Label>
        <Description>The default gateway address for this VM. Leave blank if DHCP is desired.</Description>
      </Property>
      <Property ovf:key="DNS" ovf:type="string" ovf:userConfigurable="true">

 

Based on some initial investigation I have done I beleive this is because the ProductSection is defaulting to required="true" which forces ESXi to use these fields, however ESXi doesn't seem to support this and it errors out as shown above.

 

The OVA file was generated using ovftoolto export VM in a vcenter instance.  This OVA file imports fine into vcenter, but not ESXi

 

Is there anyway to configure ovftoolwhen run against vcenter to generate required="false" in the  ProductSection elements?

    <ProductSection ovf:class="vami" ovf:instance="*******" ovf:required="false">
   
Or some otherway to get ovftoolto export a VM from vcenter as an OVA that will import into ESXi?

 

ovftool 2.1, ESXi 4.1, vCenter 4.1

↧
↧

ovftool coredumped

August 10, 2009, 12:55 am
$
0
0

 

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 "$@"

 

 

 

↧

How do I keep vmxnet3 NIC type when exporting to OVF/OVA

January 18, 2010, 10:34 am
$
0
0

Hi,

I exported a VM from my ESXi 4.0.0 server using ovftool for Windows but the type of NIC seems to have been changed as part of the conversion. It was VMXNET3 on the host but ends up being VMXNET in the OVF.

 

The export was done as follows..

 ovftool --eula@=c:\MyEULA --powerOffSource vi://root:password@esxi4_host/MyVapp d:\dev\vapps\

 

Snippet from the original .vmx

ethernet0.virtualDev = "vmxnet3"

 

Snippet from the .ovf that was generated

   <VirtualHardwareSection>
...snip..      <Item>        <rasd:AddressOnParent>7</rasd:AddressOnParent>        <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>        <rasd:Connection>VM Network</rasd:Connection>        <rasd:Description>VmxNet ethernet adapter on "VM Network"</rasd:Description>        <rasd:ElementName>ethernet0</rasd:ElementName>        <rasd:InstanceID>6</rasd:InstanceID>        <rasd:ResourceSubType>VmxNet</rasd:ResourceSubType>        <rasd:ResourceType>10</rasd:ResourceType>
...snip..    </VirtualHardwareSection>

 

Is this a known issue ? Any workarounds ?

↧
Search

VMware's ovftool doesn't install/work on VMware vMA 4.0?

March 22, 2010, 2:24 pm
$
0
0

Tried to install 64bit ovftool on VMware vMA 4.0 today and it failed to install or yield any useful information:

 

[vi-admin@scofield]$ ./VMware-ovftool-installer-1.0.0-166674-lin.x86_64.sh

VMware OVF Tool installer script
Copyright VMware 2009
.........extracting archive........

Checksum validation failed for archive.
(If you use FTP, make sure to set it to binary mode)

 

As far as I can tell, the binary is actually included in the install script though I'm not sure why 'FTP' is being referenced here unless VMware is expecting to download the actual source? I would hope that since vMA is a VMware virtual appliance that it should support any "VMwae" utilities but from what I've seen in the past with VDDK and VIX, that is not always and generally is not the case.

 

Can anyone comment on or know how to get it to install?

 

Thanks for your time

 

 

 

 

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

Twitter: @lamw

vGhetto Script Repository

Getting Started with the vMA (tips/tricks)

Getting Started with the vSphere SDK for Perl

VMware Code Central - Scripts/Sample code for Developers and Administrators

VMware Developer Community

 

http://engineering.ucsb.edu/~duonglt/vmware/vexpert_silver_icon.jpg

 

If you find this information useful, please award points for "correct" or "helpful".

↧

Export ESXi VM using ovftool in Linux

April 13, 2010, 2:56 pm
$
0
0

Hello,

 

I am trying to use the ovftool in Linux to export a VM running on ESXi 4.0 to an OVF package with the following syntax:

 

$ovftool "vi://root@192.168.X.XXX?ds=[datastore1]test-vm/test-vm.vmx" /home/ovfs/test1.ovf

 

But I always get the error: Datacenter object not found

 

The path to the vmx file is:

test-vm/test-vm.vmx

 

If I have a standalone ESXi (no vCenter present) what Datacenter name should I use?, I have tried with "Datacenter", "Default" but nothing seems to work.

 

Any help is highly appreciated.

 

Thanks.

 

 

Juan Aristizabal.

↧
↧

Locator does not refer to an object:

August 24, 2010, 2:16 am
$
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

 

 

↧

Defining serial port Without the GUI

December 2, 2010, 5:14 pm
$
0
0

I need access to my deployed virtual machine's serial console, not through a GUI window, but through ssh or telnet.  I finally found how to define a serial console so that I can telnet in, which is perfect, but now I'd like to automate the defining of that serial device without using the vSphere Client GUI.

 

I can define my serial port from the vSphere Client GUI after deploying my VM by powering off the VM, Edit Settings -> Add a Serial Port, check "Connect via Network" -> Network Backing -> Server (VM listens for connections), Port URI = telnet://10.36.0.85:7001, where 10.36.0.85 is my ESXi 4.1 server's IP address and 7001 is a random port.  When I power on my VM, I can telnet 10.36.0.85 7001 from a remote system and viola, I have serial console/terminal access.

 

In the vmx file, I can see

  serial0.present = "TRUE"

  serial0.yieldOnMsrRead = "TRUE"

  serial0.fileType = "network"

  serial0.fileName = "telnet://10.36.0.85:7001"

 

The question is, how can I define the above either in the ovf file before I deploy, as I deploy (I'm using ovftool from a remote system), or via a remote command afterwards, e.g. a vSphere CLI command?  When I try exporting the ovf template from the vSphere client, I get "Device 'Serial port 1' cannot be exported."

↧

ovftool import VM slow

December 24, 2010, 11:17 am
$
0
0

Hi,

 

Am I the only one that gets about 10Mbps (Megabits/second), or about 1MB/sec (megabyte/sec) throughput when using the ovftool to import a VM on a 1Gbps LAN?  I would assume there is some type of throttle on the service console network interface, even though I haven't found any evidence from the forums that indicates this is true.  It's just a little strange that we're getting "exactly" 10Mbps.  This happens on multiple vCenter servers and ESX clusters so I'm assuming it's a throttle.  From the one machine I run the ovftool from, I can import to 2 different clusters and get 20Mbps (10Mbps on each).

 

This is on vCenter 4.0 Update 2 and ESX 4.0 Update 2 (not ESXi) as well as 4.1 versions of these.

 

Any ideas?

 

Thanks!

 

Eric

↧
Viewing all 34499 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>