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

Error: Invalid access to memory location - Fix an OVA?

$
0
0

I have a VM that I exported as an OVA as a "Just in Case" backup a while ago.  Today I had to use it and I cannot import it.

There was an ISO mounted when I did the export and it exported the ISO as well.  The error I get is when it tries to access the ISO, it fails.

 

I downloaded OVFtool in the hopes I could strip the ISO from the OVA, but I am getting an error trying to use the --noImageFiles option.  it tells me:

 

E:\ESX\OVA's>ovftool --noImageFiles Win7-Tax64.ova test.ova
Opening OVA source: Win7-Tax64.ova
Opening OVA target: test.ova
Writing OVA package: test.ova
Disk Transfer Failed
Error: Invalid access to memory location.
Completed with errors

 

 

Is it possible to remove this ISO?

After searching through the forum I uninstalled OVFtool from my E: drive and put it on C: with the same result.  Here is the logToConsole:

 

 

E:\ESX\OVA's>ovftool --X:logToConsole Win7-Tax64.ova test.ova

2012-03-09T17:08:08.405-05:00 [08672 verbose 'Default'] Subscribing to signal: 2

(SIGINT)

2012-03-09T17:08:08.405-05:00 [08672 verbose 'Default'] Subscribing to signal: 4

(SIGILL)

2012-03-09T17:08:08.405-05:00 [08672 verbose 'Default'] Subscribing to signal: 2

2 (SIGABRT)

2012-03-09T17:08:08.405-05:00 [08672 verbose 'Default'] Subscribing to signal: 8

(SIGFPE)

2012-03-09T17:08:08.405-05:00 [08672 verbose 'Default'] Subscribing to signal: 1

5 (SIGTERM)

2012-03-09T17:08:08.406-05:00 [08672 verbose 'Default'] [ovfTool.cpp] Using home

directory C:\Users\ItsTooHot\AppData\Roaming\VMware\ovftool.cfg

2012-03-09T17:08:08.406-05:00 [08672 verbose 'Default'] [ovfTool.cpp] OvfTool En

vironment:

--> /X:httpTimeout = "600"

--> /X:imageReadSize = "262144"

--> /X:logToConsole = "true"

--> /X:maxNumberOfTermSignals = "5"

--> /X:maxRedirects = "256"

--> /X:maximalDeltaConfSize = "8"

--> /X:maximalDeltaTreeSize = "6"

--> /X:progressSmoothing = "60"

--> /X:useMacNaming = "false"

--> /X:vCloudKeepTemplate = "true"

--> /X:vCloudTimeout = "3600"

--> /X:vimSessionTimeout = "600"

--> /authdPortSource = "902"

--> /authdPortTarget = "902"

--> /fencedMode = "bridged"

--> /prgPath = "C:\Program Files\VMware\VMware OVF Tool"

--> /source = "Win7-Tax64.ova"

--> /target = "test.ova"

-->

2012-03-09T17:08:08.412-05:00 [08672 verbose 'Default'] [ovfTool.cpp] Done initi

alizing libs

2012-03-09T17:08:08.412-05:00 [08672 verbose 'Default'] [ovfTool.cpp] Determinin

g source

2012-03-09T17:08:08.412-05:00 [08672 verbose 'Default'] [ovfTool.cpp] Determinin

g target

Opening OVA source: Win7-Tax64.ova

2012-03-09T17:08:08.479-05:00 [08672 verbose 'Default'] OVF Descriptor: <?xml ve

rsion="1.0" encoding="UTF-8"?>

--> <!--Generated by VMware VirtualCenter Server, User: ItsTooHot, UTC time: 201

2-03-02T23:49:58.21025Z-->

--> <Envelope vmw:buildId="build-345043" xmlns="http://schemas.dmtf.org/ovf/enve

lope/1" xmlns:cim="http://schemas.dmtf.org/wbem/wscim/1/common" xmlns:ovf="http:

//schemas.dmtf.org/ovf/envelope/1" xmlns:rasd="http://schemas.dmtf.org/wbem/wsci

m/1/cim-schema/2/CIM_ResourceAllocationSettingData" xmlns:vmw="http://www.vmware

.com/schema/ovf" xmlns:vssd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/C

IM_VirtualSystemSettingData" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instanc

e">

-->   <References>

-->     <File ovf:href="Win7-Tax64-disk1.vmdk" ovf:id="file1" ovf:size="80291440

64" />

-->     <File ovf:href="Win7-Tax64-file1.iso" ovf:id="file2" ovf:size="331949670

4" />

-->   </References>

-->   <DiskSection>

-->     <Info>Virtual disk information</Info>

-->     <Disk ovf:capacity="70" ovf:capacityAllocationUnits="byte * 2^30" ovf:di

skId="vmdisk1" ovf:fileRef="file1" ovf:format="http://www.vmware.com/interfaces/

specifications/vmdk.html#streamOptimized" ovf:populatedSize="18292015104" />

-->   </DiskSection>

-->   <NetworkSection>

-->     <Info>The list of logical networks</Info>

-->     <Network ovf:name="VM Network">

-->       <Description>The VM Network network</Description>

-->     </Network>

-->   </NetworkSection>

-->   <VirtualSystem ovf:id="Win7-Tax64">

-->     <Info>A virtual machine</Info>

-->     <Name>Win7-Tax64</Name>

-->     <OperatingSystemSection ovf:id="1" vmw:osType="windows7_64Guest">

-->       <Info>The kind of installed guest operating system</Info>

-->       <Description>Microsoft Windows 7 (64-bit)</Description>

-->     </OperatingSystemSection>

-->     <VirtualHardwareSection>

-->       <Info>Virtual hardware requirements</Info>

-->       <System>

-->         <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>

-->         <vssd:InstanceID>0</vssd:InstanceID>

-->         <vssd:VirtualSystemIdentifier>Win7-Tax64</vssd:VirtualSystemIdentifi

er>

-->         <vssd:VirtualSystemType>vmx-07</vssd:VirtualSystemType>

-->       </System>

-->       <Item>

-->         <rasd:AllocationUnits>hertz * 10^6</rasd:AllocationUnits>

-->         <rasd:Description>Number of Virtual CPUs</rasd:Description>

-->         <rasd:ElementName>2 virtual CPU(s)</rasd:ElementName>

-->         <rasd:InstanceID>1</rasd:InstanceID>

-->         <rasd:ResourceType>3</rasd:ResourceType>

-->         <rasd:VirtualQuantity>2</rasd:VirtualQuantity>

-->       </Item>

-->       <Item>

-->         <rasd:AllocationUnits>byte * 2^20</rasd:AllocationUnits>

-->         <rasd:Description>Memory Size</rasd:Description>

-->         <rasd:ElementName>2048MB of memory</rasd:ElementName>

-->         <rasd:InstanceID>2</rasd:InstanceID>

-->         <rasd:ResourceType>4</rasd:ResourceType>

-->         <rasd:VirtualQuantity>2048</rasd:VirtualQuantity>

-->       </Item>

-->       <Item>

-->         <rasd:Address>0</rasd:Address>

-->         <rasd:Description>SCSI Controller</rasd:Description>

-->         <rasd:ElementName>SCSI controller 0</rasd:ElementName>

-->         <rasd:InstanceID>3</rasd:InstanceID>

-->         <rasd:ResourceSubType>lsilogicsas</rasd:ResourceSubType>

-->         <rasd:ResourceType>6</rasd:ResourceType>

-->       </Item>

-->       <Item>

-->         <rasd:Address>1</rasd:Address>

-->         <rasd:Description>IDE Controller</rasd:Description>

-->         <rasd:ElementName>IDE 1</rasd:ElementName>

-->         <rasd:InstanceID>4</rasd:InstanceID>

-->         <rasd:ResourceType>5</rasd:ResourceType>

-->       </Item>

-->       <Item>

-->         <rasd:Address>0</rasd:Address>

-->         <rasd:Description>IDE Controller</rasd:Description>

-->         <rasd:ElementName>IDE 0</rasd:ElementName>

-->         <rasd:InstanceID>5</rasd:InstanceID>

-->         <rasd:ResourceType>5</rasd:ResourceType>

-->       </Item>

-->       <Item>

-->         <rasd:AddressOnParent>0</rasd:AddressOnParent>

-->         <rasd:ElementName>Hard disk 1</rasd:ElementName>

-->         <rasd:HostResource>ovf:/disk/vmdisk1</rasd:HostResource>

-->         <rasd:InstanceID>6</rasd:InstanceID>

-->         <rasd:Parent>3</rasd:Parent>

-->         <rasd:ResourceType>17</rasd:ResourceType>

-->       </Item>

-->       <Item>

-->         <rasd:AddressOnParent>0</rasd:AddressOnParent>

-->         <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>

-->         <rasd:ElementName>CD/DVD Drive 1</rasd:ElementName>

-->         <rasd:HostResource>ovf:/file/file2</rasd:HostResource>

-->         <rasd:InstanceID>7</rasd:InstanceID>

-->         <rasd:Parent>4</rasd:Parent>

-->         <rasd:ResourceType>15</rasd:ResourceType>

-->       </Item>

-->       <Item>

-->         <rasd:AddressOnParent>7</rasd:AddressOnParent>

-->         <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>

-->         <rasd:Connection>VM Network</rasd:Connection>

-->         <rasd:Description>E1000 ethernet adapter on "VM Network"</rasd:Descr

iption>

-->         <rasd:ElementName>Network adapter 1</rasd:ElementName>

-->         <rasd:InstanceID>8</rasd:InstanceID>

-->         <rasd:ResourceSubType>E1000</rasd:ResourceSubType>

-->         <rasd:ResourceType>10</rasd:ResourceType>

-->       </Item>

-->     </VirtualHardwareSection>

-->   </VirtualSystem>

--> </Envelope>

Opening OVA target: test.ova

2012-03-09T17:08:08.490-05:00 [08672 verbose 'Default'] Closing writer. Locator:

test.ovf (SHA1: 352f265785c162cd8bf180f257a7876dbacf34c4, Written bytes: 4962)

2012-03-09T17:08:08.491-05:00 [08672 verbose 'Default'] Closing writer. Locator:

test.mf (SHA1: 05aeacecbe7778a0bfa4bc10ab9f6e6fc713aaa9, Written bytes: 184)

Writing OVA package: test.ova

2012-03-09T17:08:08.492-05:00 [08672 verbose 'Default'] Using file size as progr

ess measure

Disk Transfer Failed

Error: Invalid access to memory location.

2012-03-09T17:08:08.495-05:00 [08672 verbose 'Default'] Backtrace:

--> backtrace[00] rip 000000000047693a (no symbol)

--> backtrace[01] rip 000000000034d008 (no symbol)

--> backtrace[02] rip 000000000034dc1e (no symbol)

--> backtrace[03] rip 00000000003011cb (no symbol)

--> backtrace[04] rip 0000000000475df3 (no symbol)

--> backtrace[05] rip 000000000048a2fc (no symbol)

--> backtrace[06] rip 000000014001d7ab (no symbol)

--> backtrace[07] rip 000000014009b945 (no symbol)

--> backtrace[08] rip 000000014009ce71 (no symbol)

--> backtrace[09] rip 0000000140022137 (no symbol)

--> backtrace[10] rip 0000000140049b91 (no symbol)

--> backtrace[11] rip 000000014007e8b2 (no symbol)

--> backtrace[12] rip 000000014007ed6d (no symbol)

--> backtrace[13] rip 000000014001af6f (no symbol)

--> backtrace[14] rip 000000014001b76a (no symbol)

--> backtrace[15] rip 000000014025f62e (no symbol)

--> backtrace[16] rip 0000000076d9652d (no symbol)

--> backtrace[17] rip 00000000770dc521 (no symbol)

-->

2012-03-09T17:08:08.496-05:00 [08672 verbose 'Default'] Deleting file: test.ova

Completed with errors

 

E:\ESX\OVA's>


Not able to ipaddress/gateway/netmask field configuration for deployed ovf in VM using ovftool

$
0
0

Hi,

 

I want to config IP-address/gateway/netmask to the deployed ovf virtual machine and i getting the following info when i run ovftool.exe

Can anyone help me out in configure ipaddress fields.

Or is there any other way to do it.

 

 

C:\Program Files\VMware\VMware OVF Tool>ovftool.exe --powerOn --diskMode=thin --
ipProtocol=IPv4 --acceptAllEulas --name=pravin --network="VM Network" --prop:IpA
ddress="10.110.208.16" --prop:SubnetMask="255.255.252.0" --prop:Dns="10.110.188.
5" --prop:DefaultGateway="10.110.208.1" --datastore="datastore1" "C:\Sharing\v35
9\ovf_filename.ovf" " vi://root:password@10.110.209.214"
Opening OVF source: //:@WIN-1VPBHEDRE5M:80\Sharing\v359\ovf_filename.ovf
Opening VI target: vi://root@10.110.209.214:443/
Deploying to VI: vi://root@10.110.209.214:443/
Transfer Completed
Powering on VM: pravin
Warning:
- No manifest file found.
- OVF property with key: 'DefaultGateway' does not exists.
- OVF property with key: 'Dns' does not exists.
- OVF property with key: 'IpAddress' does not exists.
- OVF property with key: 'SubnetMask' does not exists.
- No manifest entry found for: 'system.vmdk'.
Completed successfully

VMware Workstation Natively

$
0
0

okay, I know this isn't developed yet, but I thought I would ask about.

first I love VMware workstation, amazing tool. and most VMware products are quick and easy for the average user.

 

okay to meat of the topic. What would it take to install VMware natively withOUT a host operating system"

 

hear me out. I really love virtualization, and the option it gives to run ANY OS, but the drawback would be the HOST OS, I WISH there was a way to install a very simple OS that VMware creates or uses, to launch it's workstation. maybe call it "LiteStation". then with the same use of the workstation, load your OS, or OS's in many cases, being able to with such a low foot print might be able to open some doors for new technology.

 

now, the simple OS, it need limited capabilities, like driver install (preferably win drivers as they are the most common and most ready, but Linux drivers would be the most understandable), limited programs or possibly no program installs. but it need enough to use the full potential of the machine, so x64 would be required along with VT-x/EPT or AMD-V/RVI + acceleration etc.... with no browsers there won't be a need to install much security, just force it to connect, but not use the network connection except to switch it over to bridge the OS's in VM-LS.

 

I'm sure this software is not out there yet. but think of the possibilities, it would become a 'virtual' boot-loader... running all OS's in a virtual environment, utilizing the max potential of multi-platform. I could see the diminish of speed as we allocate a % of the native hardware for use by the VM's, but still. No longer would dual booting be a norm, having to restart just to use a different OS, but booting both would increase. sure we have native, but sometimes I don't want to mess with Win/Lin/OS just to get to the one I want. and I feel the native OS limits the use of the virtual machine.

 

or maybe something like this is already running.... I just haven't found out.

 

Anyways thanks for the listening... who knows maybe VMware might want to implement something like LiteStation in their software arsenal....

Accipitor

ovftool: unable to upload ovf

$
0
0

Hi,

 

I am trying to upload ovf file to vcloud. But I am getting following error:

 

D:\apps\ovftool>ovftool --acceptAllEulas --diskMode=thin --noSSLVerify

--overwrite --X:connectionReconnectCount=3 --X:forceDnsName --X:disableHostname

Resolve --X:logFile=upload.log --X:logLevel=trivia "D:\VM\VM.ovf" "vcloud://admin:admin123@XYZ.com?org=ORG&vappTemplate

=Test&catalog=CAT"

Opening VMX source: D:\VM\VM.ovf

Opening vCloud target: vcloud://admin@XYZ.com:443/

Deploying to vCloud vApp template: vcloud://admin@XYZ.com:443/

Transfer Failed

Error: Failed to send http data

Completed with errors

 

In log file I can see following log:

 

-->

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: SSL: certificate subject name 'XYZ.com' does not match target host name 'XYZ1.com'

-->

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: header data hidden

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: header data hidden

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: => Sending data of size 5

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: header data hidden

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: header data hidden

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: header data hidden

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: header data hidden

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: header data hidden

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: Connection #34 to host XYZ1.com left intact

-->

2016-01-22T15:40:23.269+05:30 verbose -[04044] [Originator@6876 sub=Default] vCloud response code: 204

2016-01-22T15:40:23.269+05:30 verbose -[04044] [Originator@6876 sub=Default] vCloud response body:

-->

2016-01-22T15:40:23.269+05:30 verbose -[04044] [Originator@6876 sub=Default] Curl session torn down

 

 

Any help is appreciated.

Deploy OVA to ESXi 5 host directly

$
0
0

Hello all,

 

I have a linux VM on a remote ESXi 5 host that I have installed OVFtool.  That same linux vm has a local "win2k8.ova" ova file.  Here is the command i'm trying to use:

 

ovftool -ds=DS1 -n=MSRVR01 win2k8.ova vi://root:password@172.16.100.20

 

and get the following message:

 

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

 

But this is a single ESXi host without any ResourcePools.  How do i get around this?

 

Thanks,

Nick

Convertion of .OVF to .VMX

$
0
0

From virtualmachine i have exported .ovf file from the following website http://www.techrepublic.com/blog/windows-and-office/how-do-i-convert-virtualbox-files-to-work-with-vmware-workstation/#.

and i recieved the following error in cmd prompt.

can anyone please help me to understand error line 84 and prove me solution .

........................................................................................

Error:

- Line 84: Could not parse the document: 'mismatched tag'

Warning:

- No manifest file found.

Completed with errors.

---------------------------------------------------------------------------------------

 

Steps followed:

Step 1: Export your virtual machine

The first step is to export your virtual machine from VirtualBox.

Step 2: Editing your .ovf file

The file you need to edit will be the .ovf file that serves as the descriptor for your virtual machine. You MUST open this in a text editor. Do NOT open it in a word processor as this will add extra characters to the file, which will render it unreadable by either VirtualBox or VMWare. The first section you need to edit is the format section. Look for a line of code (near the top) that contains this phrase:

ovf:format=

What follows that section needs to be changed to:

"http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized"

The next edit (in the same file) is the Virtual SystemType, and it must be one of the following:

<vssd:VirtualSystemType>vmx-07</vssd:VirtualSystemType> (for a esx 4.0)

<vssd:VirtualSystemType>vmx-04</vssd:VirtualSystemType> (for esx 3.5.x and 4.0 hosts)

Believe it or not, the next item to edit is the rsad for the sound card. The section will look similar to:

<Item>

<rasd:Caption>sound</rasd:Caption>

<rasd:Description>Sound Card</rasd:Description>

<rasd:InstanceId>6</rasd:InstanceId>

<rasd:ResourceType>35</rasd:ResourceType>

<rasd:ResourceSubType>ensoniq1371</rasd:ResourceSubType>

<rasd:AutomaticAllocation>false</rasd:AutomaticAllocation>

<rasd:AddressOnParent>3</rasd:AddressOnParent>

</Item>

To the above section, add the following after the first <Item> tag:

<Item ovf:required="false">

Step 3: Using the OVF tool

This step requires you to download and install the VMWare OVF Tool (you will have to log in first). The OVF tool is command-line only, and it will convert your newly prepped .ovf file into a .vmx that VMWare can use. To do this, follow these steps:

  • Click Start | Run.
  • Type cmd.
  • In the command window, change to the directory you installed the OVF Tool into and then issue the command:ovftool appliance.ovf new_appliance.vmx(Where appliance.ovf is the name of the appliance you exported from VirtualBox and new_appliance.vmx is the name you want to give the new virtual appliance. Depending on the size of your virtual appliance, this could take a while.)

Problems trying to convert a .iso to .ova file

$
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

New blog entry about deploying a OVF (OVA) using ovftool


Packaging from VMX to OVF removes information

$
0
0

 

Hello,

 

 

After conversion from VMX to OVF (vmplayer use) , the OVF file does not include the information for "Network Config/Setup Type" and "Shared Folders".

 

 

Because of that, Shared Folders need to be added and network interface set to NAT on VMplayer run-time. I am unable to find any such parameters in VMware and OVF-Specs documentations.

 

 

Here are the relevant details from VMX file:

 

 

Network Connections:

 

 

ethernet0.present = "TRUE"

ethernet0.connectionType = "nat"

 

 

Shared Folders:

 

 

sharedFolder0.present = "TRUE"

sharedFolder0.enabled = "TRUE"

sharedFolder0.readAccess = "TRUE"

sharedFolder0.writeAccess = "TRUE"

sharedFolder0.hostPath = "Z:\"

sharedFolder0.guestName = "Z-Drive"

 

 

Any help appreciated.

 

 

Thanks.

 

 

ovf tool fails on device paths

$
0
0

"A line such as ide1:0.fileName = "/dev/cdrom" or a line such as ide1:0.fileName = "/dev/scd0" wil cause the ovftool to abort with the following message:

 

- Device 'cdrom1' has a backing type that is not supported. This is a general limitation of the virtual machine's virtual hardware version of the selected host.

 

By contrast if the vmx file cdrom setting is set to ide0:1.autodetect = "TRUE"  this error is not received.

 

We are not sure if this can be overcome with other tool options, although we have not seen anything that looks promising.

 

Additionally, many of our settings are not carried over to the ovf format, they are simply dropped, such as the isolation.* settings.

 

Also, the original VM consisted of several disk files (vmdk).  The ovftool created one vmdk file from this VM.  We will require creating vmware persistent and vmware non-persistent disks for some of our VMs.

We are concerned that the ovftool may lose such disk information. This would be a show stopper for us, and would require us find an alternative solution for transporting VMs.

 

We would like for VMware to advise us of possible workarounds and any recommendations for these issues."

ovftool coredumped

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

 

 

 

Export ESXi VM using ovftool in Linux

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

OVA vs OVF in ovftool

$
0
0

Hi all,

I am trying to implement an OVF support for some virtualization software, which is using raw images for disks. I use qemu-img to convert raw images to vmdk format. Then I use ovftool to convert ovf file into vmware instance.

When the file I have is a simple ovf descriptor + manifest + disk - all is fine, it works even if I'm using qemu-img without "compat6" option

When the disk is compressed or the OVF package is packed into OVA - there are errors being thrown. Moreover when I create OVA package with no disk, the conversion works.

 

Here is the fragment of results for the OVA file:

 

Writing VMX file: test_ova.vmx
[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Using file size as progress measure
Disk progress: 0%[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Ovf::GetFileSource as StreamVmdk failed. Exception: Cannot open disk source: Not a supported disk format (sparse VMDK version too old)
Disk Transfer Failed                      
Error: Failed to open source disk: 3f66f54d-a9fa-4aa8-806d-d757d6f34a59.disk0.vmdk
[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Backtrace:
[00] rip 00007f09767453e4 
[01] rip 00007f09765e99d4 
[02] rip 00007f097658e038 
[03] rip 00000000004fef51 
[04] rip 000000000054aaa5 
[05] rip 000000000054ae78 
[06] rip 000000000049c41a 
[07] rip 00007f0974e62c4d 
[08] rip 000000000047ec7a 

[2011-10-03 16:34:35.685 7F097D2C1720 verbose 'ovftool'] Deleting file: ./test_ova-disk1.vmdk

 

Same fragment when I unpack OVA and then run ovftool on the .ovf file:

 

Writing VMX file: test_ovf.vmx
[2011-10-03 16:35:53.934 7F7E899C4720 verbose 'ovftool'] Using file size as progress measure
Disk progress: 0%[2011-10-03 16:35:53.935 7F7E899C4720 verbose 'ovftool'] Ovf::GetFileSource as StreamVmdk failed. Exception: Cannot open disk source: Not a supported disk format (sparse VMDK version too old)
Disk progress: 99%[2011-10-03 16:35:54.106 7F7E899C4720 verbose 'ovftool'] Ovf::GetFileSource: Opened 3f66f54d-a9fa-4aa8-806d-d757d6f34a59.disk0.vmdk as diskLib source
[2011-10-03 16:35:54.106 7F7E899C4720 verbose 'ovftool'] Opening disk target /xcinstall-1.corp.google.com/VirtualLsiLogicController0:0
Disk Transfer Completed                   
Completed successfully
Can someone please explain to me, what is happening?
I am using python's tarfile to create OVA, if this may be of importance (although I doubt that, since it works with diskless OVA),
my qemu-img version used in this example was 0.12,
I used ovftool in version 2.0.0.

Thank you.

how to I import an ovf into esxi 3.5

$
0
0

I've got a number of VM''s running that I've created or converted from physical machines but a software supplier gave me a zip file that contains;

 

a .ovf, .mf and and .vmdk file

 

I'm running the free version of esxi3.5 - how do I do about imprting/migrating, etc... these files into my esxi 3.5 server?

 

thanks in advance.

Cannot convert an other26xlinux-64 guest from VMX to OVF

$
0
0

I'm not sure if this is a bug or I'm missing something, but if I create a VMX using the "Other 2.6.x Linux (64-bit)" guest type (so that guestOS is "other26xlinux-64"), and then convert it to OVF via ovftool (I tried 1.0 and 2.1.0, both on Linux), the resulting XML seems wrong:

 

    <OperatingSystemSection ovf:id="1" vmw:osType="*other26xLinux64Guest">

 

Note the id of 1, and the asterisk before the osType string.  When importing the resuting OVF (ESXi & vSphere 4.1.0), the guest ends up as "Other (32-bit)", which is incorrect, but more significantly can't even boot until I change it manually to a 64-bit type.

 

I was expecting the OVF to contain:

 

   <OperatingSystemSection ovf:id="100" vmw:osType="other26xLinux64Guest">

 

Hand-editing the OVF to fix up the XML works fine, and I could do some sed magic to automate all this, but I'm wondering if there is a reason for this, or a more proper fix?

 

Thanks a lot for any help


Error converting OVF to VMX -- virtualbox-3?

$
0
0

I am trying to convert a .ovf to a .vmx using the ovftool utility in terminal on OSX 10.6.8.

 

USING the --lax command, the result I get is as follows:

 

 

Opening OVF source: /Users/Andrew/Desktop/CS50/appliance50-17/appliance50.ovf
Opening VMX target: /Users/Andrew/Desktop/CS50/appliance50-17/appliance50.vmx
Warning:
- Line 39: Unsupported hardware family 'virtualbox-3'.
- Line 107: OVF hardware element 'ResourceType' with instance ID '10': No support for the virtual hardware device type '35'.
- Line 63: OVF hardware element 'ResourceType' with instance ID '5': No support for the virtual hardware device type '20'.
- Missing hardware element 'CPU' with RASD type '3'.
- Line 127: Duplicate element 'AddressOnParent'.
Writing VMX file: /Users/Andrew/Desktop/CS50/appliance50-17.vmwarevm/appliance50.vmx
Transfer Failed                      
Error: Capacity mismatch for disk /Users/Andrew/Desktop/CS50/appliance50-17.vmwarevm//appliance50-disk1.vmdk
Deleting directory tree below: /Users/Andrew/Desktop/CS50/appliance50-17.vmwarevm
Warning:
- No manifest file found.
Completed with errors

 

 

Any suggestions on how to fix this?  It seems to be a problem with ovftool itself?

ovftool fails to deploy vApp (containing 12VMs) with its ova file while vsphere client GUI works

$
0
0

We found ovftool fails to deploy a vApp instance, within which 12VMs are to be created, from an ova file, while it succeeds if the ova file contains a slimmer version ovf file (VMs' no is decreased to 8). The host where ovftool runs is in the same LAN with VCenter server so network is probably not a problem. Besides, it also succeeds to deploy the package.ova file using VSphere Client GUI.


ovftool --X:logToConsole --noSSLVerify --name=DBaaS-fail --vmFolder=BuildValidation --powerOffTarget --overwrite '--net:VMNetwork=VLAN138' --datastore=store1800-1 --diskMode=thin

--prop:BaseIP=ww.xx.yy.zz --prop:Netmask=255.255.255.128 --prop:Gateway=ww.xx.yy.253 '--prop:DNS_Servers=10.132.71.1 10.132.71.2' --acceptAllEulas --powerOn /mnt/DATA/release/XXXXX/ova-demo/package.ova vi://user:password@10.ab.cc.dd/vCHS-DBaaS/host/ALMA/Resources/BuildValidation

 

The progress bar indicating complete percentage never shows up for the 12VM-version's deployment. The verbose log shows that the upload never starts. Has anybody encountered this issue? And you'll be appreciated if you can give us a hand. And we are willing to provide our ova file to troubleshooting this issue.


Background

We generate an OVA file which contains multiple VMs. Every VM specified in the ovf file refers to either a Linux vmdk or a Win vmdk within the OVA file. With two vmdk files contained in the ova file, the file size is almost 3G. We used the above command to deploy an vApp instance, but it always fail.

 

The following are what we have tried.

- The machine to run ovftool always keeps in the same LAN as VCenter server. This ensures network low latency.

- We tried ovftool both with its linux's version and windows's version. Deploying the ova containing 12VMs, always fail; deploying the slimmer version with 8VMs, it works;

- The difference between 12VM and 8VM ovafiles are very simple: both has two vmdk files, file-size are almost the same(~3G). It's just the latter ovf file choose to generate small number of homogenous VMs.

 

The verbose logs are attached below.

 

ovftool --X:logToConsole --noSSLVerify --name=DBaaS-fail --vmFolder=BuildValidation --powerOffTarget --overwrite '--net:VMNetwork=VLAN138' --datastore=store1800-1 --diskMode=thin

--prop:BaseIP=ww.xx.yy.zz --prop:Netmask=255.255.255.128 --prop:Gateway=ww.xx.yy.253 '--prop:DNS_Servers=10.132.71.1 10.132.71.2' --acceptAllEulas --powerOn /mnt/DATA/release/XXXXX/ova-demo/package.ova vi://user:password@10.ab.cc.dd/vCHS-DBaaS/host/ALMA/Resources/BuildValidation

ŠŠŠŠŠŠŠŠ.

-->

Opening VI target:

vi://root@10.146.25.129:443/vCHS-DBaaS/host/ALMA/Resources/BuildValidation

2014-01-17T08:15:55.791Z [7FCDED7D2740 verbose 'Default'] Hostsystem used

as deploy target: vim.HostSystem:host-16

Deploying to VI:

vi://root@10.146.25.129:443/vCHS-DBaaS/host/ALMA/Resources/BuildValidation

2014-01-17T08:16:24.172Z [7FCDED7D2740 verbose 'Default'] Using file size

as progress measure

2014-01-17T08:16:24.189Z [7FCDE4FB0700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.190Z [7FCDE416F700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.190Z [7FCDE412E700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.190Z [7FCDE40ED700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.191Z [7FCDE40AC700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.192Z [7FCDE406B700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.192Z [7FCDBFFFF700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.195Z [7FCDE4FB0700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.197Z [7FCDE416F700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.197Z [7FCDE412E700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.197Z [7FCDE40ED700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.198Z [7FCDE40AC700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.199Z [7FCDE406B700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.199Z [7FCDBFFFF700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:42.512Z [7FCDBFF7D700 verbose

'HttpConnectionPool-000001'] [RemoveConnection] Connection removed; cnx:

<SSL(<io_obj p:0x00007fcde0014b00, h:-1, <TCP '0.0.0.0:0'>, <TCP

'10.146.25.129:443'>>)>; pooled: 0

work@boxbuilder:~$ lsof -i TCP

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

ovftool.b 31731 work 7u IPv4 574157 0t0 TCP

10.146.25.131:33750->10.146.25.129:https (ESTABLISHED)

ovftool.b 31731 work 9u IPv4 575678 0t0 TCP

10.146.25.131:33752->10.146.25.129:https (ESTABLISHED)

ovftool.b 31731 work 10u IPv4 574954 0t0 TCP

10.146.25.131:57555->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 11u IPv4 574159 0t0 TCP

10.146.25.131:57556->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 12u IPv4 576636 0t0 TCP

10.146.25.131:57557->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 13u IPv4 574955 0t0 TCP

10.146.25.131:57558->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 14u IPv4 574160 0t0 TCP

10.146.25.131:57559->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 15u IPv4 576637 0t0 TCP

10.146.25.131:57560->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 16u IPv4 574956 0t0 TCP

10.146.25.131:57561->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

I want to clone a VMware VM (RHEL6.5), export it as an OVF and when someone deploys it again, I want them to enter custom information like IP, DNS, VM name in the vSphere Deploy wizard. How do i make this happen?

$
0
0

I want to clone a VMware VM (RHEL6.5), export it as an OVF and when someone deploys it again, I want them to enter custom information like IP, DNS, VM name in the vSphere Deploy wizard. How do i make this happen? (I've commented all the lines in the persistent net rules file and made the file read-only.)

ovftool errors for cluster names which contain url encoded characters

$
0
0

Cluster display name: cluster1/
Cluster edit properties: cluster%2f

 /usr/bin/ovftool--noSSLVerify vi://user:pass\@vcenterserver/"datacenter"/"host"/"cluster1%2f"/

 

Error: Locator does not refer to an object: vi://user@vcenterserver:443/datacenter/host/cluster1//

Error: Locator does not refer to an object: vi://jcrocker@ng-v28.sc.steeleye.com:443/VC_50_NG_DEV/host/ng-vc-50-dev-ha//

Can an OVF Package be Opened with VMware Workstation or Player?

$
0
0

Hi Everyone,

 

I created an OVF package out of a linked-clone using the OVFTool (ver. 2.0.0). The linked-clone was created using the vmrun utility. I am able to successfully create the OVF Package (the output is a .ovf file, a .mf file, and a .vmdk file). I am now trying to open this OVF package with either Workstation or the WMware Player, but I am getting the following error:

 

vmware error.png

 

What I want to understand is if there is something that could have gone wrong in the process of creating the OVF package, or the fact that it was created from a linked-clone, that is causing this error, or if this error is simply due to the fact that OVF pacakges cannot be opened "as is" with Workstation or the Player. If the latter is the reason, why do I have an option to select OVF packages as a file type from the Open Virtual Machine Dialog?

 

ovf dialog.png

 

Thanks to anyone with a few words of advice!

Viewing all 34499 articles
Browse latest View live


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