VMWare Tools requires Mac OS X version 10.5 or higher.') If, instead of copying ist to ist, you created an empty ist file as suggested elsewhere, VMWare Tools (among other apps) will not install (' VMWare Tools can't be installed on this disk.Before booting the virtual machine, comment out or delete the line firmware = 'efi' in /Users/ username/Documents/Virtual Machines.localized/ imagename.vmwarevm/ imagename.vmx, otherwise it won't boot.To import the VMDK file, create a custom virtual machine, choose your OS X version, select 'Use an existing virtual disk', and navigate to your file.If the image was created under a different user account, you may need to change ownership and permissions of the VMDK file before importing BatChmod makes it easy.All is not lost however, as another free Paragon tool, Paragon Virtual Disk Mounter Beta, can mount VMDK (as well as VDI, VHD, pVHD, and VHDX) images for editing. This virtual machine will power off.' when attempting to boot. If the previous step is skipped, Fusion will return ' The guest operating system is not Mac OS X Server.Before converting, copy /System/Library/CoreServices/ist to /System/Library/CoreServices/ist now you've got a server version according to About This Mac and the login screen (reminiscent of NT 3.51's ProductType registry setting discovered by Mark Russinovich).Paragon's disclaimer reflects the confusion around OS X 10.5 and 10.6's EULA: 'Please make sure that you do not violate the licensing agreement of your operating system and other installed software by virtualizing your system.' Injunctions like these were not a problem for Steve apparently.

Images can be created for Fusion 3+, Parallels 5+, and VirtualBox 4+. Mac OS X P2V # Paragon Virtualization Manager for Mac OS X is a free P2V (physical to virtual) converter for Leopard and Snow Leopard (do not install under Mavericks - it will render the system unbootable (though booting into Safe Mode and running the uninstaller will fix the problem)).

P2v mac os x vmware