Dark-Alex-17/macos-virtualbox
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

see documentation

Browse Source
This commit is contained in:
Jack
2020-01-25 21:54:28 +02:00
committed by GitHub
parent 4bc8c21ce0
commit ff5f0620a9
1 changed files with 5 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+5 -19
View File
@@ -9,33 +9,19 @@ The goal of the script is to allow for a very easy installation without any clos
Tested on Cygwin. Works on macOS and WSL, should work on most Linux distros.
## Documentation
Documentation can be viewed by executing the command `./macos-guest-virtualbox.sh documentation`
## iCloud and iMessage connectivity
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 parameters may be edited at the top of the script, accompanied by an explanation. Editing them is not required when installing or running macOS, only when connecting to iCould, iMessage, and other Apple services.
### Applying the EFI and NVRAM parameters
The EFI and NVRAM parameters may be set in the script before installation by editing them at the top of the script, and applied after macOS is installed by booting into the EFI Internal Shell. When powering up the VM, immediately press Esc when the VirtualBox logo appears. This boots into the boot menu or EFI Internal Shell. From the boot menu, select "Boot Manager" and then "EFI Internal Shell" and then allow the `startup.nsh` script to run automatically, applying the EFI and NVRAM variables.
### Changing the EFI and NVRAM parameters after installation
After installation, the EFI and NVRAM variables may be changed by editing the script and then running `./macos-guest-virtualbox.sh configure_vm create_nvram_files create_macos_installation_files_viso` and copying the generated `startup.nsh` file and `bin` files to the root of the boot EFI partition. From the VirtualBox manager, attach the VISO file to the virtual machine storage, then boot macOS. Start Terminal, and execute the following commands, making sure to replace `/Volumes/path/to/VISO/startup.nsh` with the correct path:
```
mkdir EFI
sudo su # this will prompt for a password
mount_ntfs /dev/disk0s1 EFI
cp /Volumes/path/to/VISO/startup.nsh ./EFI/startup.nsh
cp /Volumes/path/to/VISO/*.bin ./EFI/
```
After copying `startup.nsh` and the binary NVRAM files, boot into the EFI Internal Shell as desribed in the section "Applying the EFI and NVRAM parameters".
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 by editing the script. See `documentation` for further information.
## Storage size
The script by default assigns a target virtual disk storage size of 80GB, which is populated to about 15GB on the host on initial installation. After the installation is complete, the storage size may be increased. First increase the virtual disk image size through VirtualBox Manager or `VBoxManage`, then in Terminal in the virtual machine run `sudo diskutil repairDisk disk0`, and then `sudo diskutil apfs resizeContainer disk1 0` or from Disk Utility, after repairing the disk from Terminal, delete the "Free space" partition so it allows the system APFS container to take up the available space.
The script by default assigns a target virtual disk storage size of 80GB, which is populated to about 15GB on the host on initial installation. After the installation is complete, the storage size may be increased. See `documentation` for further information.
## Graphics controller
Selecting the VBoxSVGA controller instead of VBoxVGA for the graphics controller may considerably increase graphics performance.
## Performance and unsupported features
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, and other features.
After successfully creating a working macOS virtual machine, consider importing it into QEMU/KVM so it can run with hardware passthrough at near-native performance. QEMU/KVM requires additional configuration that is beyond the scope of the script.