A love for Apple’s OSX and computing devices brings some side effects. One of them is that you’re stuck with VMware Fusion which is way behind it’s Windows counterpart, VMware Workstation. Fusion cannot import .ovf VMs, just .vmx VMs. In my case, I needed to convert the vSphere Management Appliance to a VM that could run in VMware Fusion.

It took me a while to this neat tool: http://communities.vmware.com/community/vmtn/server/vsphere/automationtools/ovf – ovftool is a utility that can convert virtual machines between certain formats.

Once you have it downloaded and installed, you can use the commandline tool to convert the .ovf to … Read more

When you’re like me, you just go ahead and install stuff without taking the time to read if the software you’re installing can be upgraded later. Dive head first. 😉

Often with beta software, an upgrade path to a release build is lacking or problematic. Same goes for vCloud Director 1.5 beta to the release build of 1.5. When I upgraded to the release build, I did so without ‘Unpreparing’ the ESXi hosts that were being used by vCloud Director. That causes some problems when you want to link a new vCloud Director to these ESXi hosts, as the vCloud … Read more

vCloud Director uses a java keystore to read its SSL certificates from. This makes it a bit more complicated to use an existing certificate and private key set. Took me a while to figure out, so I’m sharing.

In this example I created /opt/vmware/keystore for the certificate files. The ssl-key.pem and ssl-cert.pem are the existing certificate files. Furthermore, I used ‘passed’ as the keystore and alias password. (needed for the vCD configuration)

Firstly, we need to convert the key and certificate to a DER format:

[root@vcd.lostdomain.org keystore]# export PATH=$PATH:/opt/vmware/vcloud-director/jre/bin
[root@vcd.lostdomain.org keystore]# openssl pkcs8 -topk8 -nocrypt -in ssl-key.pem -inform PEM -out 
Read more

I’ve had my share of battles with corrupt vmdk files, after the process of removing a snapshot crashed. Finally, I found a way to recover them through a VCB utility. Here’s the log that usually presents itself:

May 12 01:43:13.593: vmx| DISKLIB-DSCPTR: Failed to open extents for descriptor file in normal mode
May 12 01:43:13.593: vmx| DISKLIB-LINK : “/vmfs/volumes/49dc603e-af139aaa-7131-002219b6f201/VM1/VM1.vmdk” : failed to open (Device or resource busy).
May 12 01:43:13.593: vmx| DISKLIB-CHAIN : “/vmfs/volumes/49dc603e-af139aaa-7131-002219b6f201/VM1/VM1.vmdk” : failed to open (Device or resource busy).
May 12 01:43:13.594: vmx| DISKLIB-LIB : Failed to open ‘/vmfs/volumes/49dc603e-af139aaa-7131-002219b6f201/VM1/VM1.vmdk’ with flags 0xa (Device or resource busy).

Read more