That's the point of my question - I cannot find the 'services' section in the HTML client. Services is there in the older / flash (flex) vsphere client, but I can't find it in the new HTML 'fully featured' client.
If the image did not come from the qemu-img utility, thevmware_disktype and vmware_adaptertype might be different. Todetermine the image adapter type from an image file, use the following commandand look for the ddb.adapterType= line:
Currently, OS boot VMDK disks with an IDE adapter type cannot be attached to avirtual SCSI controller and likewise disks with one of the SCSI adapter types(such as, busLogic, lsiLogic, lsiLogicsas, paraVirtual) cannot be attached tothe IDE controller. Therefore, as the previous examples show, it is importantto set the vmware_adaptertype property correctly. The default adapter typeis lsiLogic, which is SCSI, so you can omit the vmware_adaptertype propertyif you are certain that the image adapter type is lsiLogic.
In a mixed hypervisor environment, OpenStack Compute uses thehypervisor_type tag to match images to the correct hypervisor type. ForVMware images, set the hypervisor type to vmware. Other valid hypervisortypes include: hyperv, ironic, lxc, and qemu.Note that qemu is used for both QEMU and KVM hypervisor types.
Even with a cached VMDK, there is still a copy operation from the cachelocation to the hypervisor file directory in the shared data store. To avoidthis copy, boot the image in linked_clone mode. To learn how to enable thismode, see vmware.use_linked_clone.
Before provisioning VMs, create a port group with the same name as thevmware.integration_bridge value in nova.conf (default isbr-int). All VM NICs are attached to this port group for management bythe OpenStack Networking plug-in.
In this case the opID isoslo.vmware-debb6064-690e-45ac-b0ae-1b94a9638d1f and we can grep thevCenter log (usually /var/log/vmware/vpxd/vpxd.log) for it tofind if anything went wrong with the CreateVM operation.