Github mac os virtualbox

Github mac os virtualbox

Run macOS 11 Big Sur (and other versions) in VirtualBox on macOS

Simple script to automatically download, install and run macOS 11 Big Sur (and other versions) in VirtualBox on macOS. Since VirtualBox does not support booting from APFS volumes, this script is copying the APFS EFI drivers automatically.

The following software is needed.

• macOS Installer
• VirtualBox
• VirtualBox Extension Pack (note: released under the Personal Use and Evaluation License)

Step by Step Video

Two minute summary video (Catalina):

Execute make all to setup and run everything. After the installer reboots, press enter in the terminal to finish the installation.

Customizing your build

Additionally the following parameters can be customized with environment variables:

variable name	description	default value
DST_DIR	root directory, where the VM will be stored	$HOME/VirtualBox VMs/
VM_NAME	name of the virtual machine	macOS-VM
VM_DIR	sub directory, where the VM will be stored	$DST_DIR/$VM_NAME
VM_SIZE	the size of the hard disk	131072
VM_RES	monitor resolution	1680×1050
VM_RAM	ram size in megabytes	4096
VM_VRAM	video ram size in megabytes	128
VM_CPU	number of cpu cores to allocate	2

Execute make to get some help:

• Download macOS
  • Q: Where can I download macOS?
  • A: Execute the script installinstallmacos.py — this produces a dmg file which you can open. Within this image you can find the app that should be copied to /Applications .
• Graphic Issues
  • Q: Applications such as Apple Maps do not work as expected.
  • A: There is currently no 3D acceleration, therefore some applications do not work.
• Recovery
  • Q: How do I start the recovery mode?
  • A: Start the VM as usual and be ready to press CMD+C when you see Trying to find a bootable device. to interrupt the regular boot process. At the following EFI shell prompt try to find the relevant volume holding boot.efi in a single randomly-named sub-directory of the root directory. So try to change the current volume by entering fs4: (or fs5: , fs6: , etc.), then enter cd TAB (where TAB is used to auto-complete the randomly-named sub-dir), then look for boot.efi in that dir. If existing, start Recovery by entering boot.efi .
• Installation Loop
  • Q: After starting the installation the VM restarts and I see the installer again.
  • A: You’ve to press enter in the terminal after the installer restarts.
• Installation Not Starting
  • Q: I’ve pressed Continue to start the installation and nothing happens for minutes.
  • A: Your macOS installer might be incomplete or corrupted, please download it again from Apple.
• Error Message
  • Q: I get the error code 2, 3, 4, or 6.
  • A: You need to have some software components installed on your machine (VirtualBox, VirtualBox Extension Pack, awk). If you’ve installed Homebrew, the script will partly install these automatically. Otherwise, you need to install them manually.
• Reboot
  • Q: I see the message MACH Reboot . What should I do?
  • A: The VM failed to restart. Restart manually. However, this should not happen anymore with the latest version.
• Kernel Panic
  • Q: I see the message Error loading kernel cache (0x9) . What should I do?
  • A: This error is shown from time to time. Restart the VM. However, this should not happen anymore with the latest version.
• Black Screen
  • Q: When I then boot I don’t see anything, just a black screen. What should I do?
  • A: Change the VM version in the settings from Mac OS X (64-bit) to macOS 10.13 High Sierra (64-bit)
• Slow
  • Q: Why is the VM so slow?
  • A: Maybe #71 provides some insights.
• Other Issue
  • Q: Something is not working. What should I do?
  • A: Create a ticket

About

Run macOS 10.16 Big Sur (and other versions) in VirtualBox on macOS

Источник

Github mac os virtualbox

myspaghetti released this Jan 24, 2020

macos-guest-virtualbox.sh is a Bash script for creating Catalina (10.15), Mojave (10.14), and High Sierra (10.13) guests on VirtualBox on Windows, Linux, and macOS hosts from scratch

The script creates a VirtualBox guest macOS virtual machine with unmodified macOS installation files downloaded directly from Apple servers. See the readme file for more information.

Known issues

• Guest macOS boot process hangs on “LoadKernelFromStream”, “EndRandomSeed”, or «EXITBS» — see documentation regarding VirtualBox CPU profiles and CPUID settings.
• Hosts with CPUs released in 2020 and later may fail to start or complete the installer, and may require manually adjusting the CPUID settings.
• The script does not verify file integrity for the downloaded installation files.
• Upgrading from Big Sur 11.0 to 11.1 results in boot failure. Upgrading from earlier versions or to later versions succeeds.

Dependencies

The following dependencies should be available through a package manager:
bash coreutils gzip unzip wget xxd dmg2img virtualbox

The following optional packages provide optical character recognition that reduces the required interaction with the script:
tesseract-ocr tesseract-ocr-eng

• VirtualBox ≥ 6.1.6, though versions as low as 5.2 may work.
• GNU Bash ≥ 4.3, GNU coreutils ≥ 8.22, GNU gzip ≥ 1.5, Info-ZIP unzip ≥ v6.0, GNU wget ≥ 1.14, xxd with -e little endian support, dmg2img ≥ 1.6.5, tesseract-ocr ≥ 4

Источник

Github mac os virtualbox

Push-button installer of macOS Catalina, Mojave, and High Sierra guests in Virtualbox for Windows, Linux, and macOS

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

Push-button installer of macOS on VirtualBox

macos-guest-virtualbox.sh is a Bash script that creates a macOS virtual machine guest on VirtualBox with unmodified macOS installation files downloaded directly from Apple servers.

A default install only requires the user to sit patiently and, less than ten times, press enter when prompted by the script, without interacting with the virtual machine.

Tested on bash and zsh on Cygwin. Works on macOS, CentOS 7, and Windows. Should work on most modern Linux distros.

macOS Catalina (10.15), Mojave (10.14), and High Sierra (10.13) currently supported. The virtual machine may be upgraded to the latest Big Sur (11) version through Software Update.

Documentation can be viewed by executing the command ./macos-guest-virtualbox.sh documentation

The majority of the script is either documentation, comments, or actionable error messages, which should make the script straightforward to inspect and understand.

iCloud and iMessage connectivity and NVRAM

iCloud, iMessage, and other connected Apple services require a valid device name and serial number, board ID and serial number, and other genuine (or genuine-like) Apple parameters. These can be set in EFI and NVRAM by editing the script. See the documentation command for further information.

The script by default assigns a target virtual disk storage size of 80GB, which is populated to about 25GB on the host on initial installation. After the installation is complete, the storage size may be increased. See the documentation command for further information.

Primary display resolution

The following primary display resolutions are supported by macOS on VirtualBox: 5120×2880 2880×1800 2560×1600 2560×1440 1920×1200 1600×1200 1680×1050 1440×900 1280×800 1024×768 640×480 . See the documentation command for further information.

Developing and maintaining VirtualBox or macOS features is beyond the scope of this script. Some features may behave unexpectedly, such as USB device support, audio support, FileVault boot password prompt support, and other features.

macOS guests on VirtualBox are incompatible with some CPU models. If the guest macOS boot process hangs on “LoadKernelFromStream”, “EndRandomSeed”, or «EXITBS», see the documentation command regarding VirtualBox CPU profiles and CPUID settings. Some CPU models released in 2020 and later may fail to start or complete the installer, and may require manually adjusting the CPUID settings.

Performance and deployment

After successfully creating a working macOS virtual machine, consider importing it into more performant virtualization software, or packaging it for configuration management platforms for automated deployment. These virtualization and deployment applications require additional configuration that is beyond the scope of the script.

QEMU with KVM is capable of providing virtual machine hardware passthrough for near-native performance. QEMU supports the VMDK virtual disk image storage format, which can be configured to be created by the script. See the documentation command for further information. QEMU and KVM require additional configuration that is beyond the scope of the script.

VirtualBox Native Execution Manager (NEM)

The VirtualBox Native Execution Manager (NEM) is an experimental VirtualBox feature. VirtualBox uses NEM when access to VT-x and AMD-V is blocked by virtualization software or execution protection features such as Hyper-V, WSL2, WSLg, Windows Sandbox, memory integrity protection, Application Guard, Credential Guard, Device Guard, and other features and software. macOS and the macOS installer have memory corruption issues under NEM virtualization. The script checks for NEM and exits with an error message if it is detected.

VirtualBox can run on WSL2 and WSLg with some kernel module compilation, though performance is extremely low. At the point that kernel module compilation is required, it’s preferable to use QEMU/KVM. QEMU/KVM on WSL2 and WSLg is orders of magnitude faster than VirtualBox. WSL2, WSLg, QEMU, and KVM require additional configuration that is beyond the scope of the script.

The macOS VirtualBox guest is loaded without extra bootloaders, but it is compatible with OpenCore. OpenCore requires additional configuration that is beyond the scope of the script.

macOS may not support any built-in VirtualBox audio controllers. The bootloader OpenCore may be able to load open-source or built-in audio drivers in VirtualBox, providing the configuration for STAC9221 (Intel HD Audio) or SigmaTel STAC9700,83,84 (ICH AC97) is available.

VirtualBox does not supply an EDID for its virtual display, and macOS does not enable display scaling (high PPI) without an EDID. The bootloader OpenCore can inject an EDID which enables display scaling.

The VirtualBox EFI implementation does not properly load the FileVault full disk encryption password prompt upon boot. The bootloader OpenCore is able to load the password prompt with the parameter ProvideConsoleGop set to true . See sample config.plist

The following dependencies should be available through a package manager:
bash coreutils gzip unzip wget xxd dmg2img virtualbox

The following optional packages provide optical character recognition that reduces the required interaction with the script:
tesseract-ocr tesseract-ocr-eng

• VirtualBox ≥ 6.1.6, though versions as low as 5.2 may work.
• GNU Bash ≥ 4.3, on Windows run through Cygwin or WSL «1», see NEM
• GNU coreutils ≥ 8.22, GNU gzip ≥ 1.5, Info-ZIP unzip ≥ v6.0, GNU wget ≥ 1.14, xxd ≥ 1.11
• dmg2img ≥ 1.6.5, on Cygwin the package is not available through the package manager so the script downloads it automatically.
• tesseract-ocr ≥ 4

About

Push-button installer of macOS Catalina, Mojave, and High Sierra guests in Virtualbox for Windows, Linux, and macOS

Источник

Github mac os virtualbox

Install Mac OS X 10.4 Tiger on VirtualBox

This guide assumes that you have:

• a Mac OS X host environment, running VirtualBox on an Intel Mac
• a universal or i386 install image or disk for Mac OS X 10.4 Tiger

The environment of the example installation procedure was:

• MacBook Pro (Retina, 15-inch, Mid 2014)
• OS X El Capitan (10.11.6)
• VirtualBox 5.1.18
• the Mac OS X Server v10.4.7 (Universal) Build 8K1079 image (which can be found by searching for «10.4» in https://developer.apple.com/download/more/)

Create a new virtual machine

If trust the files in the repository and want to skip the procedure you can:

• download Tiger.ova and import it in VirtualBox (by double-clicking it or opening it from File → Import Appliance. ), or
• copy the Tiger folder from this repository to your VirtualBox VMs folder and add it in VirtualBox selecting it in from the Machine → Add. menu

If you like to see what it takes to get it done, the following step-by-step procedure will guide you in the creation and configuration of the virtual machine.

1. select Machine → New. from the menu (or click on the New button)
2. choose the name of your virtual machine (the example uses «Tiger»)
3. select Type: Mac OS X
4. select Version: Mac OS X (32-bit) or Version: Mac OS X (64-bit)
5. choose the amount of RAM (default: 2048 MB)
6. choose Create a virtual hard disk now

1. choose the settings for the creation of the virtual hard disk (the default ones should work just fine)

1. from the command-line, run the following commands (replacing «Tiger» with the name of your virtual machine):

The virtual machine should now be ready for the install procedure. Its vbox file should match the reference Tiger.vbox except for the name, timestamps and UUIDs.

Install Mac OS X

1. start the virtual machine
2. since it is the first boot, VirtualBox will open a popup asking for the install media; select the Mac OS X install disk image

1. wait some time for the boot to complete; the system might either immediately start or stay frozen for several seconds in a state like the one shown in the following image before getting to the UI; after a minute, if it shows no progress or if the console shows Still waiting for root device. , try rebooting the machine

1. choose the language you are going to use

from the hidden menu at the top of the screen, select Utilities → Disk Utility.

IMPORTANT: open Disk Utility immediately after selecting the language. Stepping through the installation and then running Disk Utility will likely result in the hard disk not being shown.

1. erase the VBOX HARDDISK hard disk using a Mac OS Extended volume format; you can choose whether to also make it Journaled and/or Case-sensitive; the default is Mac OS Extended (Journaled)

1. quit Disk Utility and proceed with the installation

Источник