VMware Fusion uses their own custom script to create a temporary VMDK which the VM boots off.Theyve been using this since Mavericks and quite frankly, its time to drop their own custom nonsense as Apple has been providing createinstallmedia for a few years now.What youll néed: Latest greatest mac0S Sierra installer (obviousIy) VMware Fusion 8.1.1 (only tested on this version) Bit of CLI skills Freshly created VM (I just created a custom vm with stock standard settings choosing OS X 10.11 as the type) Part 1: Creating the installer disk image.
Fire up Disk Utility and create a blank sparse disk image or use hdiutil, whichever you like. Size: 6GB. hdiutil create -size 6GB -fs JHFS -volname macOSinstallmedia -type SPARSE DesktopmacOSinstallmedia Mount it (or double-click in Finder to mount): hdiutil mount DesktopmacOSinstallmedia.sparseimage Next use createinstallmedia from the macOS Installer: sudo ApplicationsInstall 10.12 Developer Preview.appContentsResourcescreateinstallmedia --volume VolumesmacOSinstallmedia --applicationpath ApplicationsInstall 10.12 Developer Preview.app Part 2: Make the vmdk The newly created install media should still be mounted, if not just mount the macOSinstallmedia.sparseimage again. Before we start, you need the device id of the mounted sparse disk, so run diskutil list. Specify the path so that the resulting vmdk is created inside your freshly created VMs folder (just simplifies the next step). ApplicationsVMware Fusion.appConténtsLibraryvmware-rawdiskCreator create dévdisk2 2 DocumentsVirtual Machines.localizedmacOS.vmwarevmmacOSinstallmedia lsilogic What we have now, is a vmdk pointer that refers to our mounted sparsedisk (thus, dont try and unmount the sparsedisk). Part 3: Attach vmdk to your VM Unfortunately you cant attach an existing vmdk that happens to be a rawDisk, so we need to edit the vmx file for our VM. Navigate to it, in my case that would be DocumentsVirtual Machines.localizedmacOS.vmwarevm Use your favourite editor, such as vi or nano, then add these lines (added mine right below the first set of sata0 lines to macOS.vmx (or whatever you happen to call your VM): sata0:2.present TRUE. Once the install has run through, you can power it off and remove the lines you added in the vmx file in Part 3. Rich confirmed to me earlier that this also works as he set up his Fusion VM using his script. The install went smoothly and the beta is running now Thanks for the post. Strangely I cant find an edit button for my post Anyhow, what I meant was you cant attach an existing rawDisk vmdk via Fusions interface, hence the need to edit the vmx. Apple disclaims ány and all Iiability for the ácts, omissions and cónduct of ány third partiés in connéction with or reIated to your usé of the sité. All postings ánd use of thé content ón this site aré subject to thé Apple Developer Fórums Participation Agreement.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |