One goal of Cobbler is to abstract out all your installation types. Basically the idea is create a profile one, use it for PXE, reinstallations (--replace-self) and virtualized machines all at once.
To get this working, you will need to be using Cobbler to host your PXE infrastructure.
You can then, using special koan syntax (one single command line invocation), install a Cobbler profile /inside/ VMware, pulling the RAM and Disk storage parameters from Cobbler.
This allows you to treat VMware just as another installation type ... the same kickstart and parameters you use to install inside your bare metal machines and other virtualization types can be used for vmware in very similar ways.
First, grab yourself some caffeine.
Second, set up VMware as normal. (As of the time of writing this, we support VMware server and workstation, and there is a patch being worked on to support nearly all VMware variants)
Then do some minimal cobbler setup:
Note that MAC addresses outside that range will not work, and you cannot skip the step of creating them in that range. Unlike Xen/KVM they are also not auto-generated by koan... the reason for this is, without the mapping in Cobbler, PXE control over what profile is installed is meaningless.
Then, on the guest OS, run the following:
koan --server=cobbler.example.org --system=foosball --virt --virt-type=vmware
Koan will ask cobbler for the RAM and Disk needs associated with "foosball", or rather, the profile associated with "foosball". It will then automatically create your VMware configuration file (vmx) and disk image, and set that image up so that the rest of the installation happens over PXE.
Thus the installation is in tandem between PXE and the VMware libraries, though all of the profile data is still managed by cobbler.