Jump to content

Search the Community: Showing results for tags 'fusion'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace


  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 7 results

  1. Here is a new utility to patch the EFI firmware in VMware Workstation and Fusion to allow the non-server versions of Mac OS X 10.5 (Leopard) and 10.6 (Snow Leopard) to run. Yoiu will need macOS unlocker 3 if you are using Workstation on non-Apple hardware. I still have to find a way to do this on ESXi as the UEFIPatch utility will not run in the ESXi console. This currently supports: Workstation 11/12/14/15 on Windows and Linux Workstation Player 7/12/14/15 on Windows and Linux Fusion 10/11 on macOS https://github.com/DrDonk/efi-unlocker/releases/download/1.0.0/efi-unlocker100.zip https://github.com/DrDonk/efi-unlocker Please read the readme.txt file for details. readme.txt
  2. It’s that time of year again! With #WWDC2016 in full swing, Apple has graced us with an insider look at the next big OS release for the newly renamed macOS, dubbed Sierra. By default, it doesn’t work in Fusion as a virtual machine the same way users would expect by simply dragging the installer .app onto Fusion. Make sure to update to the latest version of Fusion, otherwise it might not work. Luckily, we can use some tools built into OS X El Capitan (and earlier) to get this working in a VM. At a high level, we need a blank OS X 10.11 (custom) VM, and we need to leverage command line tools (with links to their respective docs): Apple’s ‘createinstallmedia‘ CLI tool which is bundled with the “Install 10.12 Developer Preview.app” VMware’s ‘vmware-rawdiskCreator‘ tool to create the actual disk where we will be installing to. First, you’ll need to have a blank, custom VM. This is straightforward, but I’ll walk through just so you have it. From Fusion go File > New From the ‘New VM’ wizard we would choose ‘Create Custom VM’ Choose the OS version OS X 10.11 Choose ‘Create New Disk‘ Save the VM wherever you please I customized it to add more RAM, bumping it to 4GB (4096MB) just to be on the safe side. When you have your new blank VM, we now need to do 3 things: Create the installation media “sparse image” Copy contents of the installer into the new installation media sparse image Create a .vmdk which ‘points’ to the installation media sparse image (now filled with the contents of the installer) that we just created. So to do that we start with Mac’s Disk Utility app. You’ll find it in your /Applications/Utilities folder (or do like I do and hit cmd-space and search Spotlight for ALL THE THINGS… ? In Disk Utility go File > New Image > Blank Image… and use the settings I have in the image below (call the file whatever you like, but make sure it has the following: Size = 6GB (absolutely not smaller) Format = OS X Extended (Journaled) Encryption = none Partition = Single Partition – GUID Partition Mac Image Format = sparse disk image This creates the blank slate that we will then copy the contents of the “Install 10.12 Developer Preview.app” into using ‘createinstallimage’ utility. It should ‘mount’ the new image we just created, but if it’s not there you can mount it with Disk Utility or from the command line. Mine mounted automatically. Once it’s mounted we can copy the contents of our installation app into the new sparse image. For this, we jump down to the command line and run some commands. First, let’s create our install media. sudo /Applications/Install\ 10.12\ Developer\ Preview.app/Contents/Resources/createinstallmedia --volume /Volumes/macOS-10.12_DP --applicationpath /Applications/Install\ 10.12\ Developer\ Preview.app I named the thing I created with Disk Utility ‘macOS-10.12_DP’ as you can see in the ‘Name’ field in the image above. Easy peasy… contents copied, new installation media is created with the sparse image we just created, filled with the contents of the installer .app we got from Apple. Now, let’s make sure the host Mac’s disk layout is okay with “diskutil list“: (for clarity, $ is the prompt at the terminal, you do not need to type it) $ diskutil list It outputs something like the image below: We can see that I have the ‘Install 10.12 Developer Preview’ mounted as /dev/disk2s2. We need this device id because this is the prepared installation media that we’ll be installing from in the blank virtual machine we created earlier, and the disk number may change depending on what you have mounted on your system. Now we use VMware’s ‘vmware-rawdiskCreator’ tool to create a .vmdk based on the sparse image we created. The syntax is as follows: <path to vmware-rawdiskCreator> create <device id> <partition id> <path to where we want the .vmdk to be saved> <bus type> So a few things about that so we understand what’s happening: vmware-rawdiskCreator is located within the Fusion app bundle itself, so we’ll point to that create is the vmware-rawdiskCreator function that will create a new “raw” disk <device id> is the /dev/disk2 that we saw earlier, yours may be different if you have other disks mounted. <partition id> is 2 because it’s the 3rd partition on the ‘device’, and numbering starts at 0 (so 0 = first, 1 = second…) We tell it where we want it to be saved, and in our case it will be within the VM bundle that we created at the beginning <bus type> we choose lsilogic so that it behaves like a CD-ROM. So, for me the command is as follows (all one line): $ /Applications/VMware\ Fusion.app/Contents/Library/vmware-rawdiskCreator create /dev/disk2 2 ~/Documents/Virtual\ Machines.localized/macOS_10.12.vmwarevm/macOS_installationmedia lsilogic It should take a few seconds to make the new .vmdk. Okay, breathe… we are about to get the actual install started. Because Fusion doesn’t support mounting raw disks using the UI, we just have to add it to the configuration file manually. In the Virtual Machine Library window, right-click your newly created OS X 10.11 VM. If you hold down the ‘Option’ key you’ll notice some options change… including ‘Edit config file in a text editor’ (I couldn’t take a screenshot due to the need for multiple key presses). With the config file open in TextEdit, paste the following either at the bottom or with the other SATA device to keep them together (if you’re a little ocd about it like I am ? sata0:2.present = "TRUE" sata0:2.fileName = "macOS_installationmedia.vmdk" sata0:2.deviceType = "rawDisk" suspend.disabled = "TRUE" Notice the file we’re pointing at is ‘macOS_installationmedia.vmdk’… that’s the one we just created with our vmware-rawdiskCreator tool, and it’s a relative path meaning it’s in the same folder as the config file (.vmx) itself. Close the document (if you’re using TextEdit it will save automatically). Now all that’s left is to press ‘Play’ on the VM and go through the installation! It’s a bit of hack, but we’re working on making it just as seamless as installing current and earlier versions of OS X on Fusion. To recap, we did the following: Downloaded the macOS 10.12 Developer Preview Created a blank VM with OS X 10.11 as the type Created a sparse disk for the install media Copied the install media to the sparse disk Used vmware-rawdiskCreator to create a .vmdk based on the sparse disk with the installation media Boot and install Once the installation is done you can delete the extra hard disk because it’s no longer needed, and you can’t suspend the VM while a raw disk is attached. Hope that helps folks looking to try the latest that Apple has to offer! Let me know in the comments how that’s working out for you, if you have any suggestions, or need clarity on anything I’ve written here! One minor nitpick After installation, one should shut down the VM (via macOS Shutdown option), then re-edit the VM configuration file and remove 4-line entries: If you don’t delete these lines you end up with weird ‘bootcamp’ related errors… (we use rawdiskcreator for bootcamp installs, naturally)… And because it’s a raw-disk it can’t be deleted from the UI (because that would break a bootcamp VM so we disallow that). sata0:2.present = “TRUE” sata0:2.fileName = “macOS_installationmedia.vmdk” sata0:2.deviceType = “rawDisk” suspend.disabled = “TRUE” Thanks for the feedback, friends! The install should work afterwards Here are some screenshot of the install process and the following fun hahahha
  3. Hi all, Love the idea of having to pass a quiz to post. Hopefully I don't noob my question too much. I followed and tried the guides I have found online, and then I fell on here to install OSx on VMWare Fusion. My main purpose is that I have an older app I want to run (Homeworld 2), but because it requires a PowerPC, only 10.5/10.6 will support it. (my legit installs) I have the retails disc for 10.6, but the original install disc for my MBP for 10.5...and now that I am writing this, that might be my issue...but who knows. Basically, I have the following: OSx 10.7 Lion Fusion 4.1.1 Model Name: MacBook Pro Model Identifier: MacBookPro5,2 Processor Name: Intel Core 2 Duo Processor Speed: 2.66 GHz Number of Processors: 1 Total Number of Cores: 2 L2 Cache: 6 MB Memory: 8 GB Bus Speed: 1.07 GHz Boot ROM Version: MBP52.008E.B05 SMC Version (system): 1.42f4 My install disc is the disc that came with my laptop, version 10.5. I followed a guide here: http://blog.michael....are-fusion-4-0/ I didn't end up making it work, but it did give me a better idea as to why I can't load it natively. From the comments, I came here and I have since tried and retried to make it work, but after having registered, I did realized that I was attempting to run the install from a 10.5 disc that is for my MBP. Could this be the reason why I can't install it under VMWare Fusion 4.1.1 ? My only solution other than VMWare Fusion is to dual-boot into 10.5 (haven't looked at guides for this yet), but I imagine that can work. Obviously running 10.5 virtual would be better, if only to provide me with my game over the virtual session. Anyway, when I attempted my install, I see the Apple logo boot screen, the little spinning icon, then the Apple logo turns into a Circle+X and just hangs there are the install. The guide here seems to focus so much more on VMWare Workstation, etc. Can someone link me to a guide specifically for Fusion 4.1.1, or at least confirm if it works? One thing I did notice, is that VMWare Fusion had 10.7 as an option, after running your patch. It still didn't seem to go. Thanks to any and all help!
  4. I just purchased a refurbished 27" iMac (September 2013. Unfortunately, I didn't have enough money to buy one with a SSD or Fusion drive, and I am stuck with a 1TB internal drive at 7200rpm. Originally, I was just going to purchase an external SSD and boot from it, but I have decided that I would rather use a hybrid/fusion drive. Will a hybrid drive even work properly in an enclosure? If not, any recommendations on a cheaper external SSD? I was hoping to get the following hybrid drive with a decent USB 3.0 or TB enclosure. http://www.amazon.com/gp/product/B00EIQTOFY/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1
  5. Install Fusion Drive With Clover Easy step 1) boot to usb installer with clover. http://cloverboot.weebly.com 2) Open Disk Utility ease hdd ssd for Fusion Drive 3) Open Terminal diskutil list seek for HDD SSD Device /dev/diskX diskutil cs create “Fusion Drive” disk[Y SSD] disk[X HDD] # or disk[Y SSD]s[YA SSD partition] disk[X HDD]s[XA HDD Partition] when this operation success you will got UUID copy it diskutil coreStorage createVolume [Fusion Drive UUID] jhfs+ "[Name The Drive]" 100% 4) open disk Utility format Fusion drive as HFS+ 5) install OS X to Fusion Drive 6) Open Terminal mkdir /Volumes/{EFI,ESP1,ESP2} diskutil list remember Fusion drive,Usb installer Device /dev/diskX /dev/disk0 /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_CoreStorage 499.8 GB disk0s2 3: Apple_Boot Boot OS X 134.2 MB disk0s3 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *250.1 GB disk1 1: EFI EFI 209.7 MB disk1s1 2: Apple_CoreStorage 249.7 GB disk1s2 3: Apple_Boot Boot OS X 134.2 MB disk1s3 /dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: Apple_HFS Macintosh HD *748.9 GB disk2 /dev/disk3 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *8.0 GB disk3 1: EFI EFI 209.7 MB disk3s1 2: Apple_HFS Install OS X Mavericks 7.7 GB disk3s2 mount EFI partition on USB installer mount -t msdos /dev/disk3s1 /Volumes/EFI Mount Fusion Drive EFI Partition mount -t msdos /dev/disk0s1 /Volumes/ESP1 mount -t msdos /dev/disk1s1 /Volumes/ESP2 Copy data in EFI partition to Fusion drive cp -r /Volumes/EFI/EFI/ /Volumes/ESP1/EFI/ cp -r /Volumes/EFI/EFI/ /Volumes/ESP1/EFI/ 7) Install Ethernet kext to Fusion Drive for first Login cp -r /Volumes/EFI/EFI/CLOVER/kexts/10.9/RTL81111.kext/ /Volumes/Macintosh\ HD/System /System/Library/Extensions/RTL81111.kext/ #replace RTL81111.kext with your ethernet or wifi kext 8) Restart boot form UEFI Bios menu choose UEFI: SSD Model 9) After post installations you must install clover component for load and save NVRAM 10) Open Disk Utility get info about fusion drive partition and copy UUID 11) mount EFI partition open Clover's config.plist at EFI/EFI/CLOVER/config.plist set Default Volume by put UUID=[uUID you copy from Disk Utility] to boot section as ( easy edit config.plist with Clover Configure ) <key>Boot</key> <dict> <key>DefaultVolume</key> <string>UUID=58376EA1-C080-3883-9B1D-3A8DE1BA1177</string> <key>Timeout</key> <integer>5</integer> </dict> 12) Complete #P.S. Load Nvram Script if nvram not load to system you can use this script to fix it. You must enable iCloud, iMessage Before use this. save this code as FusionLoadNvram.command or Download and Run one. Script Base on http://www.idelta.info/archives/nvram_on_hackintosh/ osascript -e 'do shell script "sudo echo \"nvram -xp > /nvram.plist;chflags hidden /nvram.plist;\" >> /etc/rc.shutdown.local;sudo nvram -xp > /tmp/nvram;sudo cp -r /tmp/nvram /nvram.plist;sudo rm -rf /tmp/nvram;sudo chflags hidden /nvram.plist;sudo rm -rf /tmp/alpha.delta.fusion.LoadNvram.plist;sudo cat >> /tmp/alpha.delta.fusion.LoadNvram.plist << EOF <?xml version=\"1.0\" encoding=\"UTF-8\"?> <!DOCTYPE plist PUBLIC \"-/Apple/DTD PLIST 1.0/EN\" \"http:/www.apple.com/DTDs/PropertyList-1.0.dtd\"> <plist version=\"1.0\"> <dict> <key>Label</key> <string>alpha.delta.fusion.LoadNvram</string> <key>KeepAlive</key> <true/> <key>RunAtLoad</key> <true/> <key>ProgramArguments</key> <array> <string>/usr/sbin/nvram</string> <string>-xf</string> <string>/nvram.plist</string> </array> <key>UserName</key> <string>root</string> <key>StandardErrorPath</key> <string>/dev/null</string> <key>StandardOutPath</key> <string>/dev/null</string> </dict> </plist> EOF sudo cp -R /tmp/alpha.delta.fusion.LoadNvram.plist /Library/LaunchDaemons/alpha.delta.fusion.LoadNvram.plist;sudo chmod 755 /Library/LaunchDaemons/alpha.delta.fusion.LoadNvram.plist;sudo chown root:wheel /Library/LaunchDaemons/alpha.delta.fusion.LoadNvram.plist;sudo launchctl load /Library/LaunchDaemons/alpha.delta.fusion.LoadNvram.plist" with administrator privileges'
  6. Ciao a tutti, posseggo un mac mini (late 2012) i7 con un fusion drive di 1Tb. Recentemente, tentando di partizionare il drive, è successo un casino. La capacità dell'HD è scesa da 1.12 Tb a 739Gb. Non essendomi addentrato bene nella logica del Fusion drive mi sono rivolto all'Apple Store per farmi ripristinare il mac alle condizioni di fabbrica. Con non poche difficoltà (la conoscenza di comandi da terminale era indispensabile) sono riusciti a sistemarlo. Ora la disponibilità del mio hd è stata ripristinata. Ho solo un dubbio stupido....sono certo che prima dell'invio in assistenza il mio HD segnalasse 1.12Tb di disponibilità (intendo quella che viene visualizzata sulla scrivania abilitando le informazioni del drive). Ora è passata a 1.11Tb. Naturalmente questa piccola differenza non fà la differenza, ma vorrei capire il perchè si sia lievemente rimpicciolita. Ho pensato che, quando è stato acquistato, non ci fosse la partizione di recupero, perchè ho letto che alcuni mac non l'avevano...ma non ne sono convinto. Ora ovviamente c'è. Vorrei solo addentrarmi un pochino nel problema perchè ho la sensazione che, rigenerando il fusion, abbiano fatto qualcosa che non andava. Grazie a tutti per il supporto e le informazioni che mi fornirete. Francesco
  7. Hi all, I have 5 disks including four SSDS and a 4TB HDD configured in a CoreStorage (Fusion drive) volume. I have Filevault enabled also. When I turn on my hackintosh, I am presented with the Filevault screen to select my user, enter my password and continue to decrypt and boot macOS. This works around 80% of the time with no issues at all. Sometimes with seemingly no identifiable pattern, after I enter my password it just hangs on the Filevault screen with the loading bar and does not progress. There is no disk activity either. After a while of the hanging, it will just display the prohibitory sign against a black background. I have to force shut the hackintosh off with the power button and try to boot again. Usually after I do this, it will boot the second time. I'm currently running Sierra 10.12.6 but this has also happened when I tried 10.13 too. Clover is fully up to date as of today (r4380). Does anyone know why this might occur? The only thing I have picked up on is the drives change disk identifiers and move themselves around (eg. /dev/disk1) during different boot ups so maybe it's getting confused when trying to decrypt and boot as a corestorage volume. I have no idea how to prevent this from happening either. Any help or suggestion would really be appreciated. My specs are: Motherboard: GA-Z97X-UD7 TH RAM: 16GB Corsair 1866MHZ Memory GFX: 2x Nvidia GTX 760 CPU: Intel Core i7-4790K 4GHZ