This is my first time trying to install a brand new Mac OS X El Capitan v10.11.6 in a brand new VirtualBox v5.1.18 installation in a 2012 13.3' 9,2 / MD102ll/A model with Intel Core I7 CPU (2.9 ghz with 4 MB L3 cache (Turbo Boost up to 3.6 Ghz)), updated OS Sierra v10.12.4, 8 GB of 1600 MHZ DDR3 SDRAM, Intel HD graphics 4000, 500 GB of SSD, etc. I used 's instructions and script to make an ISO file of my downloaded App Store's Mac OS X El Capitan v10.11.6 installer. I tried a couple new VMs (guided and expert with their mostly defaults except the VM location to be shared by multiple Mac OS users in /Users/ant/VirtualBox VMs/Mac OS X El Capitan v10.11.6/) twice with the mounted ISO file, but both failed with their last 'com.apple.AppleFSCompressionTypeZlib load succeeded' line as shown in my screen capture/shot. How do I fix this so I can clean install?
Then name it El Capitan Type and Version = MAC OS X (64bit) and click on Next. Allocate more than 3GB of ram and click on next. Then click on Use an existing virtual hard disk file and browse for the virtual hard disk file extracted from El Capitan Disk ISO Image and click on Create. Instructions and script to help you create a VirtualBox VM running macOS. Make the script executable and run it: chmod +x prepare-iso.sh &&. By default, the output is saved as El Capitan|Sierra|High Sierra|Mojave.iso on the.
Thank you in advance. I will have to check. It did say it was done at the end.OK, I reran InstallerApp2iso with verbose 3 to make a new ISO from the same App Store's downloaded El Capitan v10.11.6 app file. I attached the log file. The only thing I noticed that might be a problem.
2017-04-17 08:43:41.025 diskimages-helper3511:191439 -processKernelRequest: flush received 33:66: execution error: Finder got an error: Can’t get window 'OS X Base System'. (-1728) Remove Package link and replace with actual files.
(go get some coffee). I also found it interesting that both md5's checksums were different from my yesterday's ISO and today's ISO files. Shouldn't they be the same? Attachments InstallerApp2iso (4/2/2017)'s verbose log 3's outputs with downloaded App Store's El Capitan v10.11.6 app. (19.67 KiB) Downloaded 10 times.
Socratis wrote. One thing I'm trying is to verify the checksum of the installer app.
See: and make sure that it's the correct one.My.dmg file looks OK: Code: $ shasum /Users/Shared/archives/Mac OSes/OSinstallers/Install OS X El Capitan 10.11.6 (ELN ).app/Contents/SharedSupport/InstallESD.dmg 7739e3f62080000da5d28efa62a262 /Users/Shared/archives/Mac OSes/OSinstallers/Install OS X El Capitan 10.11.6 (ELN).app/Contents/SharedSupport/InstallESD.dmg I noticed there was a DMG so I tried to see if I could boot from it in VM like the ISO file. And oops, I meant to say v10.11.6 and not v10.11.4 (confused with Sierra's.4) earlier. Posts: 211 Joined: 9. Jul 2007, 20:02 Location: An Ant Farm Primary OS: Debian other VBox Version: OSE Debian Guest OSses: Updated Windows (XP Pro.
SP3 & 64-bit W7 HPE SP1) & Mac OS X v10.11.x El Capitan. Socratis wrote:Right-click on the VM in VirtualBox Manager, 'Show in Finder', zip the.vbox file and attach it here please.Done.
I also upgraded my VirtualBox to v5.1.20 and rebooted the host machine, but they did not help. Attachments A zipped file of my brand new.vbox file from VirtualBox v5.1.20. (1.36 KiB) Downloaded 15 times Posts: 211 Joined: 9. Jul 2007, 20:02 Location: An Ant Farm Primary OS: Debian other VBox Version: OSE Debian Guest OSses: Updated Windows (XP Pro. SP3 & 64-bit W7 HPE SP1) & Mac OS X v10.11.x El Capitan.
Socratis wrote:. Try with 3072 MB of RAM instead of 2048 MB. Try with two vCPUs instead of one. Try with 128 MB of vRAM instead of 16 MB. Enabling the Host I/O cache, might improve your performance. If the VM ever boots (VM settings » Storage » SATA Controller » Use Host I/O Cache = checked) I changed each setting one by one to see which would work with a brand new VM.
The first three did not help, but the fourth (enable the host I/O cache) finally made the ISO booted up fully, but why? However, it won't let me install since it says 'There's not enough free space on OS X Base System to install' and no HDD seen. And then, I used its Disk Utility (top menu bar was hidden because of my limited screen space) to initialize the 32 GB virtual drive. So I decided to start over from scratch to see if I can use the default settings again, but it boots up ISO just fine. What the frak? I decided to reboot the host and retry from scratch with defaults with the new VM.
So, I enabled the Host I/O cache, and it booted up. I will resume the installation later and just in case you have something else to tell me.
Socratis wrote:Why? Are you using a VGA monitor? At 1024x768 (the default), I find it rather odd that you wouldn't see the top part of the VM. Uh, I even tried waiting 30 minutes yesterday during my breakfast break.
After enabling host I/O cache, then it boots up instantly today. No hang and pause! This internal 13.3' MBP's screen is only 1280x800 pixels big and non-retina with Intel 4000 video. I had to scroll up. The vertical scrollbar appeared during the basic text screen. It sounds I am safe to resume to install. Posts: 211 Joined: 9.
Jul 2007, 20:02 Location: An Ant Farm Primary OS: Debian other VBox Version: OSE Debian Guest OSses: Updated Windows (XP Pro. SP3 & 64-bit W7 HPE SP1) & Mac OS X v10.11.x El Capitan. Ant wrote:Uh, I even tried waiting 30 minutes yesterday during my breakfast break.
After enabling host I/O cache, then it boots up instantly today. No hang and pause!Weird. At some point earlier I believe that you said that you switched hard drives from a platter-based one to an SSD one, is that correct? It's the only thing I can think of that could make a difference, yet the connection is not that obvious. I know that it works fine with or without the I/O cache, since when I started installing OSX guests the cache wasn't even an option. I will repeat the tests (I believe I still have a 10.11.x installer around), but could you do the same please?
Create two identical VMs, except the I/O cache setting. Then we'll compare logs from the 4 runs; 2 yours and 2 mine. 2 with cache on, 2 with cache off. And yes, of course the MBP9,2 has indeed a small screen size, you're right. Proceed with the installation. It seems you're good to go.
I successfully installed El Capitan 10.11 on my MacBook Pro (running 10.10) inside of VirtualBox 5.0.8 r103449. Everything works pretty well and the performance is quite reasonable for a virtual machine.
One issue remaining is that my resolution is fixed at 1024x768. With my Windows and Linux guests, installing the VBox Guest Additions resolves this very easily.
The supplied VBOX Guest Additions ISO has guest installation utilites for Windows, Linux, Solaris, and OS2, but lacks guest additions for OSX. Does VirtualBox provide any guest additions for El Capitan guests (running on Mac hardware)? Or is this part of the roadmap at all?
Ultimately I'm trying to resolve my resolution issues, so if anyone has suggestions for that with El Capitan, please let me know. Posts: 1 Joined: 9. Nov 2015, 20:39. EFI provides two distinct video interfaces: GOP (Graphics Output Protocol) and UGA (Universal Graphics Adapter). Mac OS X uses GOP, while Linux tends to use UGA.
VirtualBox provides a configuration option to control the framebuffer size for both interfaces. To control GOP, use the following VBoxManage command: VBoxManage setextradata 'VM name' VBoxInternal2/EfiGopMode N Where N can be one of 0,1,2,3,4,5 referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively.
Volunteer Posts: 911 Joined: 3. Mar 2009, 00:29 Location: Between Heaven and Hell Primary OS: Mac OS X other VBox Version: PUEL Guest OSses: Windows Server 2003 SP2, Windows XP SP3, Windows 7.