Hello,

I need the suppot of an OVF expert.

I have the following problem - For an OFV deployment I need some restrictions.

Know someone how I can determine the disk format to "thin" during the deployment wizard?

Can someone help or have an idea how I can realize it?

Thanks in advanced and best

Romano

I'm using ESXi 6.0 U2....free version and cannot use Veeam (i believe).

I want to backup a VM, it's okay it is stopped, but for a shortest possible time.

My own suggestion:

I think the best way would be to make an OVF of the VM.

But to keep the down-time as short as possible I would like to export to a OVF located on the same host (but in another datastore located on another disk) perhaps with the fastest compression.
1st question: Using the ovftool, is it possible to specify a local datastore on the same host as target? If so how?
I tried something like:

2nd question: If I use ovftool from my local windows client pc.....will data be transferred to my PC and then back to the host or will the host understand to do it directly to it's own datastore?

3nd question: Can I do an OVF export directly on the ESXi host. e.g. connecting to the host using SSH and type a command?
For now I only know of two ways: Using the web-client and using the UI (but data will for sure be transfered directly to my PC). Or using ovftool from my PC.

One could ask, why not make a OVF directly to my backup-archive? Because I believe transferring the OVF files directly over the network will make the backup time longer, and therefore having the VM being stopped for a longer time. I get transfer-speed between 15-30MB/sec....I was hoping to get a lot more doing and disk-to-disk transfer on the host.

Any other way of doing this?
I know I could just copy all the VMs files from the datastore, but I don't like it too much as it can get complicated with snap-shorts, memory files etc.

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?

I am using ESXI 4 and I have a VM what I want to export to OVF every week or two. I am trying to use ovf tools and write a script to make this easier. No matter what I do, I always get the error "locator does not refer to an object".

My setup is ESXI 4.
VM Name is: SUGARCRM
Datastore path is: [datastore1]/debian/debian.vmx

According the to the instructions, the following should work, but they do not work for me. What is the correct command syntax?

ovftool.exe vi://root:mypassword@192.168.1.60/ha-datacenter/?ds=[datastore1]/debian/debian.vmx c:\vm\sugarcrm.ovf
Error: Locator does not refer to an object

ovftool.exe vi://root:mypassword@192.168.1.60/ha-datacenter/vm/debian/debian c:\vm\sugarcrm.ovf
Error: Locator does not refer to an object

ovftool.exe vi://root:mypassword@192.168.1.60/ha-datacenter/vm/debian/SUGARCRM c:\vm\sugarcrm.ovf
Error: Locator does not refer to an object

ovftool.exe vi://root:mypassword@192.168.1.60/ha-datacenter/SUGARCRM c:\vm\sugarcrm.ovf
Error: Locator does not refer to an object

I am trying to deploy VMWARE integrated OpenStack 3.0 OVF on vSphere 6.5 environment in my LAB. After many attempt and trials, problem persists. I am getting following error:

Failed to deploy OVF package.

Cause:

A general system error occurred:

Transfer failed: Error transferring file to https://192.168.0.36/nfc/5212d4b7-984e-5b9b-7259-d522dff8b619/disk-0.vmdk: 192.168.0.36 failed to respond.

This OVF contained two VMs. After deployment fail, If I check datastore, one of the Vms has been already copied but not the other one.

The same OVF I was able to deploy on vSphere 6.0 environment without any issues. Any body has any idea what this error is and can be fixed?

hi all,

I'm currently exporting a VM, in OVA format, using the "Exporing OVF File" command inside the client (or web client).

When exporting the unique vmdk disk is automatically divided in parts

disk1.vmdk.000000000, disk1.vmdk.000000001, disk1.vmdk.000000002  ......

I thought that this option was only available from the command line:

> ovftool --chunkSize=2gb  <source> package.ovf

The enviroment is based on vSphere 5.1

Using the same version to another infrastructure the problem does not occur.

So I imagine that the problem is due to some global setting...

I would like to avoid manually merge discs with "cat" command or "vdiskmanager" utility

any ideas?

thanks.

Hi,

    I have an ova file created for a virtual machines that has 6 virtual disks.  All disks were on different datastores.  When I import that ova I'd like a way for the vdisks to not all end up in one datastore, but on specific datastores.  I'm currently running vSphere 5.1.  My reason for this is that certain datastores are on high performance disks, and I would like the imported VM to also utilize those high performance disks.  There doesn't appear to be a way to edit while doing the import.  There also doesn't appear to be a way to edit the virtual machine and change it's datastores after I have created it.  The last thing I can find to try is to use the datastore browser to move these virtual disks to the appropriate datastores, but looks like an ugly way to do it.  Does anyone have any other ideas on how to do this with ova file?

    I switched to ova files because I wanted a nice compressed package to deliver the my virtual machine examples (they're thick provisioned because I want to encourage our customers to utilize thick provisioned drives).  Any ideas on a better way to distribute these example VM's so that the underlying storge defaults are saved?

                               Thanks for any suggestions,

                                                   Mark

Hello

I'm trying to export a VM to OVF format but it's failing with SSL error.

C:\Program Files\VMware\VMware OVF Tool>ovftool.exe --noSSLVerify=true --compres

s vi://username:password@localhost:80/Test/143.219.176.247/HOCMPTWS01-Template y:\

margg\VM

Error: cURL error: SSL connect error

Completed with errors

I'm not using any special characters.

Has anyone seen this error? Any suggestions?

Using OVFTool 4.1

ESX 3.5

VCenter 2.5

Hi All,

I have been using ovftool to export VMs to ovf and then upload the vmdk into AWS and spin up the VM there. I have encounter my first VM that doesn't follow this pattern. The only thing I think is different is that it has two disks, as per attached disks pic. The disk1.vmdk imports fine to AWS, but try various ways (ec2-import-volume and aws ec2 import-snapshot) to import disk2.vmdk but it doesnt doesn't work. The same tasks do work for disk1.vmdk. ec2-import-volume fails wirh "ERROR: This does not appear to be a Stream Optimized VMDK. It contains invalid magic number 0" and "aws ec2 import-snapshop" failed with message "deleted ClientError: Disk validation failed [Corrupted VMDK: VMDK Descriptor does not exist.]"

It looks like disk2.vmdk is corrupt? How do I verify it or the ovf?

C:\Program Files (x86)\VMware\VMware Player>1023856-vdiskmanager-windows-7.0.1.exe -R "disk1.vmdk"

No errors were found on the virtual disk, 'disk1.vmdk'.

C:\Program Files (x86)\VMware\VMware Player>1023856-vdiskmanager-windows-7.0.1.exe -R "disk2.vmdk"

Does nothing... blank...?

C:\Program Files (x86)\VMware\VMware Player>1023856-vdiskmanager-windows-7.0.1.exe -r "disk2.vmdk" -t 5 "d2.vmdk"

Creating disk 'd2.vmdk'

Failed to convert disk: The file specified is not a virtual disk (0xf00003ebf).

disk1.vmdk:

# Disk DescriptorFile

version=1

CID=99f9dc81

parentCID=ffffffff

createType="streamOptimized"

# Extent description

RDONLY 125829120 SPARSE "generated-stream.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.deletable = "true"

ddb.geometry.cylinders = "7832"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "8cc93b5679040b8bf5a35c4c8e30829a"

ddb.toolsVersion = "0"

ddb.virtualHWVersion = "10"

disk2.vmdk:

# Disk DescriptorFile

version=1

CID=c6757781

parentCID=ffffffff

createType="streamOptimized"

# Extent description

RDONLY 104857600 SPARSE "generated-stream.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.deletable = "true"

ddb.geometry.cylinders = "6527"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "3c1250f5cf0a29cd8e29d0bf42bbfc30"

ddb.toolsVersion = "0"

ddb.virtualHWVersion = "10"

Folks,

We are very happy to create a home page for one of our favorite tools. Please download it, try it out and participate in our forums.

Project Onyx is very much in Tech Preview and we appreciate any and all feedback. Forum support only.

Thanks

In case anyone plans on attending PEX in Las Vegas this year - here is the Session ID

VMware Partner Exchange Feb 8-11- Las Vegas More info

Thursday 11:30 – 12:30   TEX IBP 1007 - Getting Stoned with Onyx

First of all Project Onyx is completely awesome. It has helped me with my scripting and better understaning of the entire VM environment.

In short, we are trying to automate a process to flex clone our db server rdm luns and attach the clones luns to our reporting server.  I have created a script that completes all the process including the adding the physical rdm to the vm.  the process on the script appears to work correctly, however when the reconfigVM_Task function runs on the VM, i get an error File rpt-test/rpt-test.vmdk is larger than he maximum size supported by datastore

If i add the rdm's through the gui, it all works correctly. There is 370gb of space free in the datastore.  The lun's I am attempting to add to the vm add up to 20 gb total in size.

Here is the add-rdm function code that was created from Project Onyx, that I have modified enough to pass the new Lun id to the VM.

function AddHDD{

param($vm, $string1, $string2, $string3)

$string1 = "/vmfs/devices/disk/" + $string1

$string2 = "/vmfs/devices/disk/" + $string2

$string3 = "/vmfs/devices/disk/" + $string3

$vmMo = Get-View (Get-VM $vm).ID

$spec = New-Object VMware.Vim.VirtualMachineConfigSpec

$spec.deviceChange = New-Object VMware.Vim.VirtualDeviceConfigSpec[] (3)

$spec.deviceChange[0] = New-Object VMware.Vim.VirtualDeviceConfigSpec

$spec.deviceChange[0].operation = "add"

$spec.deviceChange[0].fileOperation = "create"

$spec.deviceChange[0].device = New-Object VMware.Vim.VirtualDisk

$spec.deviceChange[0].device.key = -100

$spec.deviceChange[0].device.backing = New-Object VMware.Vim.VirtualDiskRawDiskMappingVer1BackingInfo

$spec.deviceChange[0].device.backing.fileName = "[WINVM_FC1]"

$spec.deviceChange[0].device.backing.deviceName = $string1 #"/vmfs/devices/disks/naa.60a98000572d43724e34556771303735"

$spec.deviceChange[0].device.backing.compatibilityMode = "physicalMode"

$spec.deviceChange[0].device.backing.diskMode = ""

$spec.deviceChange[0].device.connectable = New-Object VMware.Vim.VirtualDeviceConnectInfo

$spec.deviceChange[0].device.connectable.startConnected = $true

$spec.deviceChange[0].device.connectable.allowGuestControl = $false

$spec.deviceChange[0].device.connectable.connected = $true

$spec.deviceChange[0].device.controllerKey = 1000

$spec.deviceChange[0].device.unitNumber = 1

$spec.deviceChange[0].device.capacityInKB = 11542703

$spec.deviceChange[1] = New-Object VMware.Vim.VirtualDeviceConfigSpec

$spec.deviceChange[1].operation = "add"

$spec.deviceChange[1].fileOperation = "create"

$spec.deviceChange[1].device = New-Object VMware.Vim.VirtualDisk

$spec.deviceChange[1].device.key = -101

$spec.deviceChange[1].device.backing = New-Object VMware.Vim.VirtualDiskRawDiskMappingVer1BackingInfo

$spec.deviceChange[1].device.backing.fileName = "[WINVM_FC1]"

$spec.deviceChange[1].device.backing.deviceName = $string2 #"/vmfs/devices/disks/naa.60a98000572d43724e34556771303736"

$spec.deviceChange[1].device.backing.compatibilityMode = "physicalMode"

$spec.deviceChange[1].device.backing.diskMode = ""

$spec.deviceChange[1].device.connectable = New-Object VMware.Vim.VirtualDeviceConnectInfo

$spec.deviceChange[1].device.connectable.startConnected = $true

$spec.deviceChange[1].device.connectable.allowGuestControl = $false

$spec.deviceChange[1].device.connectable.connected = $true

$spec.deviceChange[1].device.controllerKey = 1000

$spec.deviceChange[1].device.unitNumber = 2

$spec.deviceChange[1].device.capacityInKB =5245223

$spec.deviceChange[2] = New-Object VMware.Vim.VirtualDeviceConfigSpec

$spec.deviceChange[2].operation = "add"

$spec.deviceChange[2].fileOperation = "create"

$spec.deviceChange[2].device = New-Object VMware.Vim.VirtualDisk

$spec.deviceChange[2].device.key = -102

$spec.deviceChange[2].device.backing = New-Object VMware.Vim.VirtualDiskRawDiskMappingVer1BackingInfo

$spec.deviceChange[2].device.backing.fileName = "[WINVM_FC1]"

$spec.deviceChange[2].device.backing.deviceName = $string3  #"/vmfs/devices/disks/naa.60a98000572d43724e34556771303737"

$spec.deviceChange[2].device.backing.compatibilityMode = "physicalMode"

$spec.deviceChange[2].device.backing.diskMode = ""

$spec.deviceChange[2].device.connectable = New-Object VMware.Vim.VirtualDeviceConnectInfo

$spec.deviceChange[2].device.connectable.startConnected = $true

$spec.deviceChange[2].device.connectable.allowGuestControl = $false

$spec.deviceChange[2].device.connectable.connected = $true

$spec.deviceChange[2].device.controllerKey = 1000

$spec.deviceChange[2].device.unitNumber = 3

$spec.deviceChange[2].device.capacityInKB = 5245223

$VmMo.ReconfigVM_Task($spec)

}

Any help/advice would be greatly appreciated.  Thanks in advance.

Carter's session from Partner Exchange in Las Vegas 2010.

-Pablo

1 Hour Session from VMware Partner Exchange Feb 2010. Carter Shanklin presents "Getting Stoned with Project Onyx"

[Getting Stoned with Project Onyx by Carter Shanklin | http://vimeo.com/10468960] from pablo roesch on Vimeo .</p>

VM Console remains Blank When VI client is connected via Onyx.

Is this normal ?

Regards

Jith

Config : XP SP3

.Net 3.5 SP1

vSphere CLient 4.1

and PowerCLI 4.1

I tried to use vSphere Client (against a vCenter in 2.5 U5) : KO with Onyx2, OK with Onyx1.5

Same thing with PowerCLI 4.1 : KO with Onyx2, OK with Onyx1.5

it still sounds very promising !

Ben

The 'check for newer version' feature doesn't work when behind a proxy.

And there is no option to specify a proxy nor to take the IE or FF settings.

A minor annoyance

____________

Blog: LucD notes

Twitter: lucd22

Hi,

Onyx is great in that you get all the config changes i the order executed with complete content!

Is there any way to get this in vCenter without having to deploy this proxy? I suppose this is the reason you did it. I am just wondering how best to integrate vCenter configuration change tracking into my application without telling customers they have to connect to a proxy.

Thanks in advance.

Firstly, Onyx -- great project!

(Window title): Client load error

 

Error occured while loading "\\unc\path\to\Onyx_2.0.3910.32223\Clients\Onyx.KnownClients.Generic.dll":

Request for the permission of type 'System.Security.Permissions.RegistryPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=...' failed.

Is it possible to utilize onyx to see what third party applications are doing with vcenter or specific hosts?   We are investigating an issue we have that occurs with a third party product, and their response has consistantly been "we just make standard snapshot calls to vcenter" - however we do NOT have the same issue when we utilize snapshots without the third party app.   Would like to be able to capture what is going from the app to vcenter and compare to a normal vcenter client snapshot request.

Any ideas or suggestions would be greatly appreciated.