Quantcast
Viewing all 34499 articles
Browse latest View live

how to deploy ova/ovf into VMware Player?

hello.

 

         I create a ova file from my ESXi 5.0.0 with ovftool 2.1.0-467744, then I deploy this ova file into ESXi 5.0.0 is success and work well.

 

But I can't deploy the same ova file into VMWare Player with ovftool 2.1.0-467744 installed. Why?

 

         Anybody has any idea? Thanks.

 

Best Regards,


ovftool.exe crashes when deploying OVA from Windows 7

I'm experiencing a coredump when attempting to deploy an OVA into vCenter 5.0.0.  I have downloaded the OVA to the Windows 7 PC locally and have run the ovftool from that path as follows:

 

ovftool --X:logToConsole=true --X:logLevel="verbose" --name=ovf-test --datastore=datastore-local-113 --network=VLAN-603 MVF-ver-2_OVF10.ova "vi://Administrator:**********@10.45.99.10/MitelDesignCenter/host/VLabCluster-03 (Intel G6, stand-alone)/10.45.12.113"

 

 

The verbose output looks like this:

 

2012-01-13T11:45:23.595-05:00 [04492 verbose 'Default'] Subscribing to signal: 2 (SIGINT)

2012-01-13T11:45:23.596-05:00 [04492 verbose 'Default'] Subscribing to signal: 4 (SIGILL)
2012-01-13T11:45:23.596-05:00 [04492 verbose 'Default'] Subscribing to signal: 22 (SIGABRT)
2012-01-13T11:45:23.598-05:00 [04492 verbose 'Default'] Subscribing to signal: 8 (SIGFPE)
2012-01-13T11:45:23.599-05:00 [04492 verbose 'Default'] Subscribing to signal: 15 (SIGTERM)
2012-01-13T11:45:23.600-05:00 [04492 verbose 'Default'] [ovfTool.cpp] Using home directory C:\Users\hinchleg\AppData\Roa
ming\VMware\ovftool.cfg
2012-01-13T11:45:23.601-05:00 [04492 verbose 'Default'] [ovfTool.cpp] OvfTool Environment:
--> /X:httpTimeout = "600"
--> /X:imageReadSize = "262144"
--> /X:logLevel = "verbose"
--> /X:logToConsole = "true"
--> /X:maxNumberOfTermSignals = "5"
--> /X:maxRedirects = "256"
--> /X:maximalDeltaConfSize = "8"
--> /X:maximalDeltaTreeSize = "6"
--> /X:progressSmoothing = "60"
--> /X:useMacNaming = "false"
--> /X:vCloudKeepTemplate = "true"
--> /X:vCloudTimeout = "3600"
--> /X:vimSessionTimeout = "600"
--> /authdPortSource = "902"
--> /authdPortTarget = "902"
--> /datastore = "datastore-local-113"
--> /fencedMode = "bridged"
--> /name = "ovf-test"
--> /network = "VLAN-603"
--> /prgPath = "C:\Program Files\VMware\VMware OVF Tool"
--> /source = "MVF-ver-2_OVF10.ova"
--> /target = "vi://Administrator:**********@10.45.99.10/MitelDesignCenter/host/VLabCluster-03 (Intel G6, stand-alone)
/10.45.12.113"
-->
2012-01-13T11:45:23.609-05:00 [04492 verbose 'Default'] [ovfTool.cpp] Done initializing libs
2012-01-13T11:45:23.609-05:00 [04492 verbose 'Default'] [ovfTool.cpp] Determining source
2012-01-13T11:45:23.630-05:00 [04492 verbose 'Default'] [ovfTool.cpp] Determining target
Opening OVA source: MVF-ver-2_OVF10.ova
2012-01-13T11:45:23.634-05:00 [04492 verbose 'Default'] Manifest file present. Parsing file.
2012-01-13T11:45:23.635-05:00 [04492 verbose 'Default'] Manifest file entry: SHA(MVF-ver-2_OVF10.ovf) = 2926495bbde18cdb
3e738e390258bd2009996156
2012-01-13T11:45:23.637-05:00 [04492 verbose 'Default'] Manifest file entry: SHA(system.vmdk) = e1fe00f518356b3741789fa6
7567e9c8bf3fffe7
The manifest validates
2012-01-13T11:45:23.642-05:00 [04492 verbose 'Default'] Verifying that the files references in manifest are valid
2012-01-13T11:45:23.644-05:00 [04492 verbose 'Default'] OVF Descriptor: <?xml version="1.0" encoding="UTF-8"?>
dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" x
-->   <References>
-->     <File ovf:href="system.vmdk" ovf:size="488976384" ovf:id="system.vmdk_id"/>
-->   </References>
-->   <NetworkSection>
-->     <Info>List of logical networks used in the package</Info>
-->     <Network ovf:name="Network 1">
-->       <Description>Network 1</Description>
-->     </Network>
-->   </NetworkSection>
-->   <vmw:IpAssignmentSection ovf:required="false" vmw:protocols="IPv4" vmw:schemes="ovfenv">
-->     <Info>Supported IP assignment schemes</Info>
-->   </vmw:IpAssignmentSection>
-->   <DiskSection>
-->     <Info>List of the virtual disks and partitions needed</Info>
-->     <Disk ovf:diskId="system" ovf:capacity="5120" ovf:capacityAllocationUnits="byte * 2^20" ovf:format="http://www.v
mware.com/interfaces/specifications/vmdk.html#streamOptimized" ovf:fileRef="system.vmdk_id" ovf:populatedSize="135456358
4"/>
-->   </DiskSection>
-->   <VirtualSystem ovf:id="MVF-ver-2">
-->     <Info>A virtual machine</Info>
-->     <ProductSection ovf:required="false">
-->       <Info>VM ISV branding information</Info>
-->       <Product>MVF-ver-2</Product>
-->       <Vendor>Mitel Networks Corporation</Vendor>
-->       <!--
-->             Version is the actual product version in the
-->             form X.X.X.X where X is an unsigned 16-bit integer.
-->
-->             FullVersion is a descriptive version string
-->             including, for example, alpha or beta designations
-->             and other release criteria.
-->         -->
-->       <Version>1.0.13.0</Version>
-->       <FullVersion>MVF 1.0.13.0 (design) on MSL 9.4.12.0</FullVersion>
-->       <ProductUrl/>
-->       <VendorUrl/>
-->       <AppUrl>http://${vami.ip0.MVF-ver-2}/</AppUrl>
-->       <Category>Application</Category>
-->       <Property ovf:key="admin_pass" ovf:type="string" ovf:userConfigurable="true" ovf:value="" ovf:qualifiers="MinL
en(0),MaxLen(32)" ovf:password="true">
-->         <Label>Initial Administrator Password</Label>
-->         <Description>The initial password to use to when accessing this deployed virtual appliance.</Description>
-->       </Property>
-->       <Property ovf:key="domain_name" ovf:type="string" ovf:userConfigurable="true" ovf:value="xyzcorp.com" ovf:qual
ifiers="MinLen(0),MaxLen(256)">
-->         <Label>Domain Name</Label>
-->         <Description>The domain name this virtual appliance should belong to.</Description>
-->       </Property>
-->       <Property ovf:key="ssh_access" ovf:type="string" ovf:userConfigurable="true" ovf:value="none" ovf:qualifiers="
ValueMap{&quot;none&quot;,&quot;local networks&quot;,&quot;public&quot;}">
-->         <Label>Remote SSH Access</Label>
-->         <Description>The level of accessibility for remote shell access to this system.</Description>
-->       </Property>
-->       <Property ovf:key="local_net_ip" ovf:type="string" ovf:userConfigurable="true" ovf:value="0.0.0.0" vmw:qualifi
ers="Ip">
-->         <Label>Local Network Network Address</Label>
-->         <Description>The network address where remote access, including web admin access, is available.</Description
>
-->       </Property>
-->       <Property ovf:key="local_net_netmask" ovf:type="string" ovf:userConfigurable="true" ovf:value="0.0.0.0" vmw:qu
alifiers="Ip">
-->         <Label>Local Network Netmask</Label>
-->         <Description>The netmask to define the subnet range within the local network address.</Description>
-->       </Property>
-->       <Property ovf:key="mitel_arid" ovf:type="string" ovf:userConfigurable="true" ovf:value="" ovf:qualifiers="MinL
en(0),MaxLen(20)">
-->         <Label>Mitel Application Record ID</Label>
-->         <Description>The license key to apply to this virtual appliance.</Description>
-->       </Property>
-->     </ProductSection>
-->     <ProductSection ovf:class="vami" ovf:instance="MVF-ver-2" ovf:required="false">
-->       <Info>VAMI Properties</Info>
-->       <Category>Networking Properties</Category>
-->       <Property ovf:key="ip0" ovf:userConfigurable="true" ovf:type="string" vmw:qualifiers="Ip('Network 1')">
-->         <Label>Network 1 IP Address</Label>
-->         <Description>The IP address for this interface.</Description>
-->       </Property>
-->       <Property ovf:key="netmask0" ovf:userConfigurable="true" ovf:type="string" vmw:qualifiers="Netmask('Network 1'
)">
-->         <Label>Network 1 Netmask</Label>
-->         <Description>The netmask or prefix for this interface.</Description>
-->       </Property>
-->       <Property ovf:key="gateway0" ovf:userConfigurable="true" ovf:type="string" vmw:qualifiers="Gateway('Network 1'
)">
-->         <Label>Network 1 Default Gateway</Label>
-->         <Description>The default gateway address for this VM.</Description>
-->       </Property>
-->       <Property ovf:key="DNS0" ovf:userConfigurable="true" ovf:type="string" vmw:qualifiers="Dns('Network 1')">
-->         <Label>Network 1 DNS</Label>
-->         <Description>The domain name servers for this VM (comma separated).</Description>
-->       </Property>
-->     </ProductSection>
-->     <ProductSection ovf:class="vm" ovf:required="false">
-->       <Info>VM specific properties</Info>
-->       <Property ovf:key="vmname" ovf:type="string" ovf:value="MVF-ver-2"/>
-->     </ProductSection>
-->     <AnnotationSection>
-->       <Info/>
-->       <Annotation/>
-->     </AnnotationSection>
-->     <OperatingSystemSection ovf:id="79" ovf:version="5" vmw:osType="mslGuest">
-->       <Info>Guest Operating System</Info>
-->       <Description>MSL 9.3</Description>
-->     </OperatingSystemSection>
-->     <VirtualHardwareSection ovf:transport="com.vmware.guestInfo" ovf:required="false">
-->       <Info>Virtual Hardware Requirements</Info>
-->       <System>
-->         <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>
-->         <vssd:InstanceID>0</vssd:InstanceID>
-->         <vssd:VirtualSystemType>vmx-07</vssd:VirtualSystemType>
-->       </System>
-->       <Item>
-->         <rasd:AllocationUnits>hertz * 10^6</rasd:AllocationUnits>
-->         <rasd:Description>Number of virtual CPUs</rasd:Description>
gData">1 virtual CPU</rasd:ElementName>
Data">1</rasd:InstanceID>
-->         <rasd:ResourceType>3</rasd:ResourceType>
-->         <rasd:VirtualQuantity>1</rasd:VirtualQuantity>
-->       </Item>
-->       <Item>
-->         <rasd:AllocationUnits>byte * 2^20</rasd:AllocationUnits>
-->         <rasd:Description>Memory Size</rasd:Description>
gData">1024 MB of memory</rasd:ElementName>
Data">2</rasd:InstanceID>
-->         <rasd:ResourceType>4</rasd:ResourceType>
-->         <rasd:VirtualQuantity>1024</rasd:VirtualQuantity>
-->       </Item>
-->       <Item>
-->         <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
-->         <rasd:Connection>Network 1</rasd:Connection>
gData">Ethernet adapter on vmnet</rasd:ElementName>
Data">3</rasd:InstanceID>
-->         <rasd:ResourceSubType>VMXNET3</rasd:ResourceSubType>
-->         <rasd:ResourceType>10</rasd:ResourceType>
-->       </Item>
-->       <Item>
a">0</rasd:Address>
gData">SCSI Controller 0  - lsilogic</rasd:ElementName>
Data">4</rasd:InstanceID>
-->         <rasd:ResourceSubType>lsilogic</rasd:ResourceSubType>
-->         <rasd:ResourceType>6</rasd:ResourceType>
-->       </Item>
-->       <Item>
-->         <rasd:AddressOnParent>0</rasd:AddressOnParent>
gData">Harddisk 1</rasd:ElementName>
-->         <rasd:HostResource>ovf:/disk/system</rasd:HostResource>
Data">5</rasd:InstanceID>
-->         <rasd:Parent>4</rasd:Parent>
-->         <rasd:ResourceType>17</rasd:ResourceType>
-->       </Item>
-->     </VirtualHardwareSection>
-->   </VirtualSystem>
--> </ovf:Envelope>
-->
2012-01-13T11:45:23.802-05:00 [04492 verbose 'HttpConnectionPool'] HttpConnectionPoolImpl created. maxPoolConnections =
20; idleTimeout = 900000000; maxOpenConnections = 20; maxConnectionAge = 0
2012-01-13T11:45:24.876-05:00 [05124 verbose 'Default'] CURL: => Send header GET /sdk/vimServiceVersions.xml HTTP/1.1
--> Authorization: Basic QWRtaW5pc3RyYXRvcjpQQVNTd29yZDEyMzQ=
--> User-Agent: VMware-client/4.0.0 (ovfTool; libcurl)
--> Host: 10.45.99.10
--> Accept: */*
-->
-->
2012-01-13T11:45:24.879-05:00 [05124 verbose 'Default'] CURL: <= Recv header HTTP/1.1 200 OK
-->
2012-01-13T11:45:24.879-05:00 [05124 verbose 'Default'] CURL: <= Recv header Date: Fri, 13 Jan 2012 16:45:25 GMT
-->
2012-01-13T11:45:24.884-05:00 [05124 verbose 'Default'] CURL: <= Recv header Cache-Control: no-cache
-->
2012-01-13T11:45:24.887-05:00 [05124 verbose 'Default'] CURL: <= Recv header Connection: Keep-Alive
-->
2012-01-13T11:45:24.889-05:00 [05124 verbose 'Default'] CURL: <= Recv header Content-Type: text/xml; charset=utf-8
-->
2012-01-13T11:45:24.891-05:00 [05124 verbose 'Default'] CURL: <= Recv header Content-Length: 492
-->
2012-01-13T11:45:24.893-05:00 [05124 verbose 'Default'] CURL: <= Recv header
--> <?xml version="1.0" encoding="UTF-8" ?>
--> <!--
-->    Copyright 2008-2011 VMware, Inc.  All rights reserved.
--> -->
--> <namespaces version="1.0">
-->   <namespace>
-->     <name>urn:vim25</name>
-->     <version>5.0</version>
-->     <priorVersions>
-->       <version>4.1</version>
-->       <version>4.0</version>
-->       <version>2.5u2</version>
-->       <version>2.5</version>
-->     </priorVersions>
-->   </namespace>
-->   <namespace>
-->     <name>urn:vim2</name>
-->     <version>2.0</version>
-->   </namespace>
--> </namespaces>
-->
2012-01-13T11:45:24.896-05:00 [04492 verbose 'Default'] [ViConnection] Using vim API version: 5.0
2012-01-13T11:45:24.947-05:00 [04492 verbose 'HttpConnectionPool'] HttpConnectionPoolImpl created. maxPoolConnections =
1; idleTimeout = 900000000; maxOpenConnections = 1; maxConnectionAge = 0
2012-01-13T11:45:24.967-05:00 [04492 verbose 'Default'] Keeping VI session alive
Opening VI target: 2012-01-13T11:45:24.994-05:00 [04492 info 'Default'] CoreDump: Writing minidump
2012-01-13T11:45:25.044-05:00 [04492 panic 'Default']
-->
--> Panic: Win32 exception: Access Violation (0xc0000005)
-->    Read (0) at address 0000000000000018
-->    rip: 00000001401e4dcb rsp: 000000000012f470 rbp: 0000000000000018
-->    rax: 0000000000000000 rbx: 000000000012f5c0 rcx: ffffffffffffffff
-->    rdx: 0000000140000000 rdi: 0000000000000018 rsi: 0000000000000001
-->    r8:  0000000000000003 r9:  0000000000000000 r10: 000000000012f828
-->    r11: 000000000012f640 r12: 00000000036451cb r13: 0000000000000002
-->    r14: 0000000000000075 r15: 0000000000000000
-->
--> Backtrace:
--> backtrace[00] rip 000000000055693a (no symbol)
--> backtrace[01] rip 000000000042d008 (no symbol)
--> backtrace[02] rip 000000000042dc1e (no symbol)
--> backtrace[03] rip 000000000056db28 (no symbol)
--> backtrace[04] rip 000000000056dc97 (no symbol)
--> backtrace[05] rip 0000000000570b56 (no symbol)
--> backtrace[06] rip 0000000068975129 (no symbol)
--> backtrace[07] rip 00000000689742d6 (no symbol)
--> backtrace[08] rip 00000000689749de (no symbol)
--> backtrace[09] rip 0000000068974c1d (no symbol)
--> backtrace[10] rip 000000006897502b (no symbol)
--> backtrace[11] rip 000000014025f1ae (no symbol)
--> backtrace[12] rip 0000000077289d0d (no symbol)
--> backtrace[13] rip 00000000772791af (no symbol)
--> backtrace[14] rip 00000000772b1278 (no symbol)
--> backtrace[15] rip 00000001401e4dcb (no symbol)
--> backtrace[16] rip 00000001401e6c73 (no symbol)
--> backtrace[17] rip 00000001401e1b04 (no symbol)
--> backtrace[18] rip 00000001401cbfd9 (no symbol)
--> backtrace[19] rip 00000001400dbae5 (no symbol)
--> backtrace[20] rip 00000000003d7b65 (no symbol)
--> backtrace[21] rip 00000000003d7c8e (no symbol)
--> backtrace[22] rip 00000001400986f9 (no symbol)
--> backtrace[23] rip 000000014001af4b (no symbol)
--> backtrace[24] rip 000000014001b76a (no symbol)
--> backtrace[25] rip 000000014025f62e (no symbol)
--> backtrace[26] rip 000000007715652d (no symbol)
--> backtrace[27] rip 000000007728c521 (no symbol)
-->

OVFTool 2.1.0 with Active Directory Question (vSphere crashes)

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

Large OVF imports into vCloud Director 1.0.1 fail, smaller imports succeed

I'm getting wildly different results while importing large OVF file into vCloud Director 1.0.1 via the ovftool than when performing the upload of the same OVF via the native JAva tool within vCloud Director itself. AS long as the file transfer compeltes through the vCD Java tool, the file is importing into vCenter correctly, and then being correctly registered within vCD.

 

The OVF I'm working with is 68.2 GB in size.

 

Below is a sanatized version of my command line and the output from the tool:

 

 

ovftool --net:"dvportgroup-48=company-Services_Internal" E:\OlioWebtest\oliowebtest.ovf "vcloud://user:password@testvcd1.company.com:443/?org=company_Services&vapp=OlioWebTest&vdc=company_Services_ALLO_vDC01&catalog=test"
Opening OVF source: E:\OlioWebtest\oliowebtest.ovf
The manifest validates
Warning: File is not referred in the manifest: oliowebtest.ovf
Opening vCloud target: vcloud://user@testvcd1.company.com:443/
Waiting for task on server .done
Deploying to vCloud: vcloud://user@testvcd1.company.com:443/
Disk Transfer Completed

Error: Invalid response from server
Completed with errors

 

Looking in the vCD GUI logs for the organization, I see the descriptor being processed, and the process for finalizing the upload completing, but the vApp is never added to the catalog. If I look in vCenter, I can find the VM on a valdi datastore for the org vDC and the correct resource pool in the proper state for a catalog vApp. The error "Error: Invalid response from server" is displayed immediately upon completion of the data transfer.

 

 

 

If I move the VM to the root of the datacenter, I can import the VM as a vApp and copy it to the caalog with no issue.

 

I tested with a much smaller OVF (1.3 GB), and received exactly the behavior I expected.

 

ovftool --net:"none=company-Services_Internal" E:\suse\descriptor.ovf "vcloud://user:password@testvcd1.company.com:443/?org=company_Services&vapp=SUSE32&vdc=company_Services_ALLO_vDC01&catalog=test"
Opening OVF source: E:\suse\descriptor.ovf
Warning: No manifest file
Opening vCloud target: vcloud://user@testvcd1.company.com:443/
Waiting for task on server .done
Deploying to vCloud: vcloud://user@testvcd1.company.com:443/
Disk Transfer Completed

Waiting for task on server ...................done
Waiting for task on server .......................................done
Waiting for task on server ..done
Completed successfully

 

Looking at the succesful transfer, I see an additonal action logged in the GUI logs for the organization. After the finalization record, there is a "Create virtual application" event logged on the smaller transfer that is never logged on the larger transfer.

 

The only item I can think of from a vCloud Director standpoint is that that vCD logon sesion timeout has expired on the large transfer long before the additional tasks are issued to vCD resulting in the invalid response. Is this the case, or is something else going on?

 

When looking at the vcloud-container-info.log file on the cells doing the processing for the succesful imports, I see a whole string of commands being executed in the current logged on user context.

Custom OVF Property in my Virtual appliance

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

ovftool : Specify Hardware version during a conversion ?



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

Can't import OVA in to a folder

 

I an trying to inport an OVA file in to a precreated folder named test under a datacenter.  I have created a fold under vCenterServer/datacenter/host/test and running the below command.

 

ovftool --powerOn C:\Images\cur\NAMEHERE.ova vi://Administrator:PASSWORD@192.168.1.100/vCenterServer/datacenter/host/test

 

 

 

 

When i run this command i get the below output

Opening OVA source: C:\Images\cur\NAMEHERE.ova

Error: Found wrong kind of object (Folder)

 

I have also tried the same but importing in to a VM folder vCenterServer/datacenter/VM/tes, this gives the same error as above.

 

What am i doing wrong?

 

 

 

iso to ovf/ova? Can it be done?

 

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!

 

 

 

 

 


OVFtool bug when specifying datastore

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

ovftool fails with curl error: couldn't connect to server

HI,

 

I'm trying to create an OVF using ovftool 3.0.1. When I issue the ovftool command from the command line I get:

Error: cURL error: Couldn't connect to server
Completed with errors

 

I used the following command:

 

/usr/bin/ovftool vi://username:password@XX.XX.XX.XX/datacenter/vm/folder/vmname /destination

 

I can issue the command as above without the vmname to see if I can access Vsphere and to make sure I have a valid source locator.  The command is successful and returns a list of VMs I can use. When I add the VM name to the source locator path, I get the above error. The VM is pysically about 14GB in size (that is the space alloacted).

 

I can use the same command to another Vpshere server and I'm successful in creating the OVF. Which leads me to think that it might be a configuration issue with this Vsphere server?

 

What sorts of issues can lead to the above error?

 

Thanks,

 

Fernando

Failed to deploy OVA

Hi,

 

i have some OVA files that when i try to deploy them, shows the following error :

Unable to access file :

C:\user\Administrator\Desktop\Backup\new-ova\ubuntu.18-file1.iso

End Of OVA file reached while looking for : ubuntu.18-file1.iso

Image may be NSFW.
Clik here to view.
OVA-error.jpg

 

I use VMWare ESXi 5.5

how can i resolved this issue ?

Unsupported virtual hardware device 'VirtualSCSI'.

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.

ovftool - CURL error buffer: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number

I'm trying to export a VM using ovftool on linux.

 ovftool --X:logFile=upload1.log --X:logLevel=verbose --noSSLVerify vi://[user]:[pass]@[ESXi IP]:[port]/my_datacenter/vm/my_vm_folder/my_vm_name /tmp/test.OVF 

and i get the following error in the log:

2016-11-11T11:40:30.287+02:00 verbose -[7F5C76E3F7C0] [Originator@6876 sub=Default] Getting version of the VI host : [ESXi IP]

2016-11-11T11:40:30.287+02:00 verbose -[7F5C76E3F7C0] [Originator@6876 sub=Default] Initializing new curl session

2016-11-11T11:40:30.288+02:00 verbose -[7F5C76E3F7C0] [Originator@6876 sub=Default] WebRequest set basic http authorization, username : [user]

2016-11-11T11:40:30.288+02:00 verbose -[7F5C76E3F7C0] [Originator@6876 sub=Default] Getting http page: https://[ESXi IP]/sdk/vimServiceVersions.xml

2016-11-11T11:40:30.299+02:00 verbose -[7F5C6F1CF700] [Originator@6876 sub=Default] Curl_perform error code 35 (SSL connect error)

2016-11-11T11:40:30.299+02:00 verbose -[7F5C76E3F7C0] [Originator@6876 sub=Default] CURL error buffer: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number

2016-11-11T11:40:30.299+02:00 verbose -[7F5C76E3F7C0] [Originator@6876 sub=Default] Curl session torn down

2016-11-11T11:40:30.300+02:00 verbose -[7F5C76E3F7C0] [Originator@6876 sub=Default] Backtrace:

-->

--> [backtrace begin] product: VMware Workstation, version: e.x.p, build: build-2459827, tag: -

--> backtrace[00] libvmacore.so[0x003D9C74]: Vmacore::System::Stacktrace::CaptureWork(unsigned int)

--> backtrace[01] libvmacore.so[0x001DBF37]: Vmacore::System::SystemFactoryImpl::CreateQuickBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&)

--> backtrace[02] libvmacore.so[0x0018481D]: Vmacore::Throwable::Throwable(std::string const&)

--> backtrace[03] ovftool.bin[0x0020DFB3]

--> backtrace[04] ovftool.bin[0x00248E5D]

--> backtrace[05] ovftool.bin[0x0024C5C9]

--> backtrace[06] ovftool.bin[0x00295BC4]

--> backtrace[07] ovftool.bin[0x0029714C]

--> backtrace[08] ovftool.bin[0x00299744]

--> backtrace[09] ovftool.bin[0x001EC2B4]

--> backtrace[10] ovftool.bin[0x001EEB04]

--> backtrace[11] libc.so.6[0x00021F45]

--> backtrace[12] ovftool.bin[0x001626B9]

--> [backtrace end]

-->

You'll note that the command is run with --noSSLVerify.

So I checked the SSL versions on both the client and the ESX server using:

openssl ciphers -v | awk '{print $2}' | sort | uniq 

and both returned:

SSLv3

TLSv1.2

no difference between the two...
looked around for this curl error and while it is fairly well known I haven't seen a solution applicable to my situation.

Any ideas?

ovftool 4.2.0 has a broken --allowAllExtraConfig

4.2.0 is bundled into the current build of Fusion10:

ovftool --version

VMware ovftool 4.2.0 (build-6230482)

 

This version has a busted --allowAllExtraConfig flag, so some VMs will not export to OVA, instead you get a slew of errors like this one:

- Line -1: Unsupported value 'disk.EnableUUID' for attribute 'key' on element 'ExtraConfig'.

OVF and BIOS Settings

Hi,

 

is it possible to include the nvram-file in the OVF-File oder how to tranport BIOS-Settings with OVF.

 

regards.

Hans-Peter

TAM, EMEA-Central

VMware


Error: Failed to open disk: Test.vmdk

Hello all,

 

I am having a problem with the ovftool.

 

Here's what i did.

 

1)I created a VM running CentOS.

 

2)These are the 3 files that i got.

 

Test.vmx

 

Test.vmdk (Descriptor File)

 

# Disk DescriptorFile

version=1

CID=5046e880

parentCID=ffffffff

createType="vmfsPreallocated"


# Extent description

RW 83886080 VMFS "Test-flat.vmdk" 0


# The Disk Data Base

#DDB


ddb.virtualHWVersion = "4"

ddb.geometry.cylinders = "83220"

ddb.geometry.heads = "16"

ddb.geometry.sectors = "63"

ddb.adapterType = "lsilogic"

 

Test-flat.vmdk

 

3) This is the command that i ran

 

ovftool "Test.vmx" "Test_New.ova"

 

4)This is the error that i got.
2012-09-05T12:24:57.817+05:30 [7F22134FE740 verbose 'Default'] [ovfTool.cpp] Done initializing libs
2012-09-05T12:24:57.817+05:30 [7F22134FE740 verbose 'Default'] [ovfTool.cpp] Determining source
2012-09-05T12:24:57.818+05:30 [7F22134FE740 verbose 'Default'] [ovfTool.cpp] Determining target
Opening VMX source: Test.vmx
2012-09-05T12:24:57.821+05:30 [7F22134FE740 verbose 'Default'] Failed to open disk: ./Test-1-0.vmdk
2012-09-05T12:24:57.821+05:30 [7F22134FE740 verbose 'Default'] Exception: Failed to open disk: ./Test-1-0.vmdk. Reason: The file specified is not a virtual disk
Error: Failed to open disk: Test-1-0.vmdk

Please help!

 

Thank you

Failed to open OVF descriptor

Hi All,

 

I am trying to convert vmdk file to ovf format using command line. I am using the below command:

 

# ovftool my_vm.vmdk new.ovf

   Opening OVF source: my_vmdk.vmdk

   Error: Failed to open OVF descriptor

   Completed with errors

 

Not sure whats wrong in this command. Please help!

 

Thanks!

Unsupported element 'Property'

 

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'

 

 

 

 

 

 

 

 

OVF import trouble

I am attempting to perform and document a roundtrip Export and Import using ovftool.

 

I performed the export as follows:


bowser:/tmp/ovfTool # mount 10.68.x.xx:/export/images /mnt/ovfExport

bowser:/tmp/ovfTool # mkdir /mnt/ovfExport/ovfs

bowser:/tmp/ovfTool # mkdir /mnt/ovfExport/ovfs/wario-sles11-sp1-x8664

bowser:/tmp/ovfTool # ovftool vi://bluoma:******@helios.blue.roguewave.com/Corvallis/vm/Build\ Server/sles11-sp1-x8664/wario /mnt/ovfExport/ovfs/wario-sles11-sp1-x8664/wario.ovf

Opening VI source: vi://bluoma@helios.blue.roguewave.com:443/Corvallis/vm/Build%20Server/sles11-sp1-x8664/wario
Opening OVF target: /mnt/ovfExport/ovfs/wario-sles11-sp1-x8664/wario.ovf
Writing OVF package: /mnt/ovfExport/ovfs/wario-sles11-sp1-x8664/wario.ovf
Disk Transfer Completed

Completed successfully

 

 

Now I am attempting to import/deploy the ovf:

 

bowser:/tmp/ovfTool # ovftool --datastore=skillet-ds2 /mnt/ovfExport/ovfs/wario-sles11-sp1-x8664/wario.ovf vi://bluoma:******@helios.blue.roguewave.com/Corvallis/host/R\&D/despina.cvo.roguewave.com
Opening OVF source: /mnt/ovfExport/ovfs/wario-sles11-sp1-x8664/wario.ovf
The manifest validates
Opening VI target: vi://bluoma@helios.blue.roguewave.com:443/Corvallis/host/R&D/despina.cvo.roguewave.com
Deploying to VI: vi://bluoma@helios.blue.roguewave.com:443/Corvallis/host/R&D/despina.cvo.roguewave.com
Disk Transfer Failed
Error: SHA1 digest of file wario-disk1.vmdk does not match manifest
Completed with errors

 

Any ideas why the SHA1 digest did not verify?

 

vCenter:   4.1.0

ESXi host:  4.1.0

 

Thanks,

Bryan

Locator does not refer to an object:

 

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

 

 

Viewing all 34499 articles
Browse latest View live


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