Odd "feature" I've encountered in VMWare Fusion 6.
If you net boot an OS X VM and use Casper Imaging to deploy, it'll deploy the OS and it's own stuff ok but any other additional packages have their ownership completely screwed up. Usually the files are set to _unknown:_unknown.
Anyone else encountered this?
Ok found what was wrong. Get Fusion to use SCSI disks instead of SATA.
SATA drives show up in the vm environment as external drives instead of internal ones for some reason.
Thanks for posting this, franton. This was the solution to a problem I had where target VM's wouldn't get past the 50 % boot progress bar, after being Casper Imaged through either netboot or a second virtual hard drive. Once I switched my target VM's HDD to SCSI, it was able to boot.
I can only log in from safe-mode, but that's another challenge.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.