A quick check seems to find this may be unsupportable. For example http://stackoverflow.com/questions/39159/is-it-possible-to-run-mac-os-x-in-a-virtual-machine covers that restrictive EULA so for this one, call Apple and ask them directly.
Nothing better for this one than mother.
I have several Mac OS X VMs and Mac Minis running 10.8.4. A typical VM says it has a 2.28 GHz 'Unknown' processor with 4GB DRAM. They all have a particular user which has admin rights. They're all told to restart daily (some other machine - the master - ssh's in as the same admin user and does a sudo shutdown -r now)
All machines are configured to have this particular admin user autologin and run an AppleScript 'Application' which basically runs a bash shell script which calls java with a jar and a URL for something on the master using HTTPS ... this uses a JNLP file.
One problem is that this admin user doesn't always reliably autologin. When I find a machine where this is the case, I'm usually able to ssh into it as the same user, issue a sudo shutdown -r now, wait for the machine to restart and then this user does autologin (that is, it usually works the second time around without any changes or tweaks).
How can I figure out what's going on and make it so this user reliably does the autologin after every restart?
(Other issues with these machines include  occasionally a socket is closed, interrupting work being orchestrated by a remote machine which ssh's in with this same admin user ...  occasionally the machine will get into a state where no one can ssh in... perhaps there is a memory hog process which takes up too much RAM?)
I've tried having this admin user's login item (the bash script) sleep for 6 minutes before doing the jnlp task which involves HTTPS and the master. But I think it doesn't even get as far as autologging in this admin user.