Quantcast
Viewing all 34499 articles
Browse latest View live
↧

OVFTool 2.1.0 with Active Directory Question (vSphere crashes)

January 23, 2012, 10:03 am
$
0
0

When I try to export one of my VMs using File/Export/Export OVF Template....it crashes vSphere with a nice assertion window.

 

To see what the cause of this is, I decided to try using ovftool 2.1.0 on Linux to export the VM instead, to see what happens (like does it crash ovftool?).

 

I got stuck though because when I log into the vCenter I have to specify a domain\username format and I can't figure out how to pass this to ovftool in a way that doesn't cause errors.

 

For example, I tried things like this:

 

# ovftool  vi://myvcenter.domain.com/DataCenterName/vm/

Username:  MYDOMAIN\Administrator

Password: whatever

 

Didn't work, I don't think it likes the backslash.

 

So I tried stuffing it in a variable:

 

# DF="MYDOMAIN\Administrator"

# ovftool  vi://"$DF"@myvcenter.domain.com/DataCenterName/vm/

 

Error: Curl error: Couldn't connect to server

 

Anyone have any ideas?

 

Thanks,

CJ

↧
Search

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

 

 

↧
↧

getting error (core dumped) "$OVFTOOL_BIN" "$@" while using ovftool from jenkins instance

January 14, 2015, 1:33 pm
$
0
0

Hi,

 

When i try to configure deployment job from Jenkins, i am getting

/usr/bin/ovftool: line 23: 19723 Segmentation fault  (core dumped) "$OVFTOOL_BIN" "$@"

error in command line, Not sure how to find solution, i was able to use the same command from my local system directly from my user account.

This error i am getting after message

Opening OVF source: myfile.ovf

 

thanks in advance,

vduggirala

↧

ovftool Failed to send http data

April 5, 2016, 3:00 am
$
0
0

Hi,

 

Can someone provide an indication on what is generating the following error when running ovftool to deploy a vm on a host in a vCenter?

 

Opening OVA source: /usr/local/path/to/ova/file.ova

The manifest validates

Opening VI target: vi://user@vCenter_ip:443/

Deploying to VI: vi://user@vCenter_ip:443/

^MTransfer Failed

^MTransfer Failed

Error: Failed to send http data

Completed with errors

 

The error reproduced on client setup to which I don't have access so I have no other additional logs.

 

Thanks.

↧

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

↧
↧

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

April 5, 2012, 9:03 am
$
0
0

Hi All,

 

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

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

It has a total size of around 4.5GB.

 

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

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

 

output:

{{{

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

 

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

 

Completed successfully

}}}

 

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

 

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

{{{

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

}}}

and then it stops and everything rolledback.

 

 

Any pointers ?

 

Thanks

Nikunj

↧

Problems trying to convert a .iso to .ova file

September 12, 2013, 9:19 pm
$
0
0

I have a .iso image from which I want to create a .ova , But everytime I run into a problem

 

Error: Curl error: Couldn't connect to server

Completed with errors

 

Here is the command I used,

 

ovftool vi://user:master/@14.23.12.34:443/rt4/www/html/imgs/qweTER7.3/.tyRani/NEWCFT/CFT-NEW-5.23.23.iso /rt4/www/html/tmp_ova/CFT-NEW-5.23.23.ova

 

Not sure whats wrong with this command, I don't have special character in my password or username

 

please note that 14.23.12.34 is a linux machine and both source and target are in same machine and Im executing ovftool command in same linux machine.

 

Thank you

Mac

↧

OVA file generated using OVFTool not played by Player5.0

October 5, 2012, 3:05 am
$
0
0

I have VMware Player 5.0.0. It internally has ovftool 3.0.1

 

I used VMware Studio2.0 to build an appliance in  OVA format  - It opened successfully by Player 5.0

Converted OVA -> OVF again from OVF->OVA using ovftool 3.0.1. (This is just for testing. Later I need to change OVF according to my need).

 

Now this re-generated OVA file is not supported by Player5.0. When I tried to open OVA file, Player failed with error 'Failed to open virtual machine: Failed to open OVF descriptor.'

 

Is this an issue with OVFTool or Player ? Please suggest.

 

BTW, I have used the below commands for convertion

 

OVA -> OVF      ovftool.exe -st=OVA -tt=OVF "d:\NEW-OVA\xxxxxxx.ova" "d:\NEW-OVF\xxxxxxx.OVF"
OVF -> OVA      ovftool.exe -st=OVF -tt=OVA "d:\NEW-OVF\xxxxxxx.ovf" "d:\NEW-OVA\xxxxxxx.OVA"
Without -st, -tt options, ovftool is assuming the VMX format.

 

Thanks in advance

 

--hemanth

↧
Search

Converting OVA file to VMX

July 3, 2011, 8:06 pm
$
0
0

I downloaded the latest OVF converter tool but it looks like as per documentation, it cannot convert OVA to VMX?

If yes, how?  If no, how do I?  Thanks

↧
↧

Convert ovf template to vsx

November 21, 2011, 5:06 am
$
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

↧

no love for Fusion users?

June 30, 2009, 2:22 pm
$
0
0

 

I just found out that I cannot import any of my ovf images into Fusion. Very disappointing. It looks like there may have once been an ovftool binary for Mac users but I'm unable to find it anywhere. Does anyone know where I can get a copy of the tool for OS X? I could always do the conversion on my linux workstation but I'd rather do most of my work on the Mac.

 

 

Will ovf import/export be built into Fusion in a future version? That sure would make things easier.

 

 

Thanks.

 

 

↧

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

↧

OVFtool bug when specifying datastore

December 7, 2012, 6:16 pm
$
0
0

It appears that ovftool 3.0.1 has an issue while specifying the target datastore when importing an OVF when the VI is a vCenter 5.0 server with ESX 5.0 Update 1 hosts that have a large number of Datastores.  The cluster where this problem occurs has 148 Datastores.

 

Some datastores work, most don't.  This is a new problem since ovftool 2.0.1 worked fine when this cluster was at ESX 4.0 Update 3.

 

An example statement that will cause the problem (with all names replaced with "test" names):

 

"C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" --acceptAllEulas --name="TestVM" --datastore="TestDatastore" --network=TestNetwork --vmFolder="TestFolder" http://192.168.0.1/public/ovfs/testvm.ovf vi://"username:password"@vcenter.test.com/"Data Center"/host/"HA and DRS"/Resources/"Test Resource Pool"

 

Which results in this error (with the datastore names replaced with TestDatastoreX), even though the Datastore clearly exists.  It worked fine prior to vSphere 5.0 and vCenter 5.0.  Any ideas?

 

Note that all "possible completions" specified below work fine!  Those that I have tried that are "not" in the possible completions do "not" work.

 

Error: Invalid target datastore specified (TestDatastore): Possible completions:
  TestDatastore1
  TestDatastore2
  TestDatastore3
  TestDatastore4
  TestDatastore5
  TestDatastore6
  TestDatastore7
  TestDatastore8
  TestDatastore9
  TestDatastore10
  TestDatastore11
  TestDatastore12
  TestDatastore13
  TestDatastore14
  TestDatastore15
  TestDatastore16
  TestDatastore17
  TestDatastore18
  TestDatastore19
  TestDatastore20
  TestDatastore21
  TestDatastore22
  TestDatastore23
  TestDatastore24
  TestDatastore25
  TestDatastore26
  TestDatastore27
  TestDatastore28
  TestDatastore29
  TestDatastore30
  TestDatastore31
  TestDatastore32
  TestDatastore33
  TestDatastore34
  TestDatastore35
Completed with errors
↧
↧

iso to ovf/ova? Can it be done?

July 27, 2010, 10:10 am
$
0
0

 

Hi I'm wondering if there is an automation tool/command(s) that will allow us (team of developers) to import/use a .iso file that contains 64bit OS and pass it through VMware ESXi or Server and then export it to OVF/OVA?

 

 

Is it possible? Can it be done?

 

 

Your answers will be very apreciated, many thanks!

 

 

 

 

 

↧

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

December 16, 2012, 12:01 pm
$
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!

↧
Search

Unsupported virtual hardware device 'VirtualSCSI'.

January 20, 2016, 3:07 am
$
0
0

I try to deploy a OVA into a vCenter 5.5, using OVFTool with the following command:

/usr/bin/ovftool --powerOn --acceptAllEulas --noSSLVerify --skipManifestCheck --allowAllExtraConfig --X:enableHiddenProperties --deploymentOption=${VMNAME_DEPLOYMENT_SIZE} "--net:Network 1=${VMNAME_PORTGROUP}" --datastore=${VMNAME_DATASTORE} --diskMode=${VMNAME_DISK_TYPE} --name=${VMNAME_DISPLAY_NAME} --prop:vami.DNS.APPLIANCE=${VMNAME_DNS} --prop:vami.gateway.APPLIANCE=${VMNAME_GATEWAY} --prop:vami.ip0.APPLIANCE=${VMNAME_IPADDRESS} --prop:vami.netmask0.APPLIANCE=${VMNAME_NETMASK} --prop:guestinfo.cis.appliance.ssh.enabled=${ENABLE_SSH} ${VMNAME_OVA} vi:/${VCENTER_USERNAME}:${VCENTER_PASSWORD}@${VCENTER_HOSTNAME}/?dns=${ESXI_HOSTNAME}

and I got this error:

Opening VMX target: vi:/administrator*************
Error: OVF Package is not supported by target:
 - Line 768: Unsupported virtual hardware device 'VirtualSCSI'.
Warning:
 - ExtraConfig options exists in source.
Completed with errors

The OVF file has the following settings:

            <Item>
     LINE768-->   <rasd:Address xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData">0</rasd:Address>
                <rasd:ElementName xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData">SCSI Controller 0 - pvscsi</rasd:ElementName>
                <rasd:InstanceID xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData">4</rasd:InstanceID>
                <rasd:ResourceSubType>virtualSCSI</rasd:ResourceSubType>
            <rasd:ResourceType>6</rasd:ResourceType>
              </Item>

and also :


<System>
        <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>
        <vssd:InstanceID>0</vssd:InstanceID>
<vssd:VirtualSystemType>vmx-07 vmx-08 vmx-09</vssd:VirtualSystemType>
      </System>

 

Any advice on how to fix this issue and deploy the OVA?

Thanks.

↧

Cannot Import OVF into ESXi 3.5

June 28, 2009, 11:58 pm
$
0
0

 

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

 

 

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

 

 

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

 

 

 

 

 

An error occurred while parsing the OVF descriptor

Unable to parse XML element 'Envelope'

 

 

 

 

 

What am I doing wrong? 

 

 

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

 

 

Please help!

 

 

 

 

 

Thank you.

 

 

↧
↧

Create OVF/OVA via ovftool

April 9, 2012, 6:06 am
$
0
0

Hi,

 

I have a ESXi 5.0 server running which has a Guest VM running CentOS 5.6.

 

The ESXi server is a standalone server, not included in a datacenter, not managed by vCenter.

 

The server has a HDD of 80G which has both the ESXi host & the Guest OS running on top of it.

 

I installed ovftools on my Windows laptop & tried to create a ovf from the VM but am unsuccessful. I constantly get the following error -

c:\>ovftool vi://root:<rootpassword>@<ESXi Host IP>/datastore1/CentOS c:\testVM.ovf

Error: Cannot parse locater: vi://root:<rootpassword>@<ESXi Host IP>/datastore1/CentOS

Completed with errors

 

The local datastore name is "datastore1"

 

Can someone help me out here with forming the correct the ovftool command to create an ovf & possibly an OVA out of the running VM?

 

 

Thanks

 

Bhushan Pathak

↧

Error Installing OVFTool on Ubuntu 14 WorkStation Guest

May 13, 2015, 9:02 pm
$
0
0


I am trying to install ovftool 4.1.0 on a Ubuntu guest I have on my Windows host.  I downloadedd the ovftool bundle changed permission to +x, started the bundle, and accepted the license.  It says it is ready to install and I press enter.  Then I get the below and ovftool is never installed.


 


Rolling back VMware installer component 2.1.0


Removing files..


Uninstalling VMware installer component 2.1.0


Deconfiguring...


 


Any ideas? The bundle I have is the 'VMware-ovftool-4.1.0-2459827-lin.x86_64.bundle' on Ubuntu 14


 

↧

Is there a way to specify static IP for a deploying OVA in the ovftool command?

August 3, 2011, 3:38 pm
$
0
0

Hi,

 

I am trying to deploy OVA using ovftool. I see the option --network and --net available for selecting the network by name, though I was not able to find a way to assign a static IP in the ovftool command itself. Something like --ip0=10.10.10.10. Is there a way we can do this? From UI when we deploy an OVA, we have provision to provide IP, Gateway, Netmask and DNS.

 

Thanks

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