Merge pull request #219 from bittner/patch-1
added information about deployment
This commit is contained in:
@@ -9,6 +9,8 @@ A default install only requires the user to sit patiently and, less than ten tim
|
|||||||
## Documentation
|
## Documentation
|
||||||
Documentation can be viewed by executing the command `./macos-guest-virtualbox.sh documentation`
|
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 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 NVRAM by editing the script. See `documentation` for further information.
|
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 NVRAM by editing the script. See `documentation` for further information.
|
||||||
|
|
||||||
@@ -21,8 +23,10 @@ The following primary display resolutions are supported by macOS on VirtualBox:
|
|||||||
## Unsupported features
|
## 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, FileVault boot password prompt support, and other 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, FileVault boot password prompt support, and other features.
|
||||||
|
|
||||||
#### Performance
|
#### Performance and deployment
|
||||||
After successfully creating a working macOS virtual machine, consider importing it into QEMU with KVM so it can use hardware passthrough for near-native performance. To use the same virtual machine disk image on VirtualBox and QEMU, choose the `VMDK` virtual disk image storage format before executing the script, or after macOS is installed convert the `VDI` file to a `VMDK` file. See `documentation` for further information. QEMU and KVM require additional configuration that is beyond the scope of the script.
|
After successfully creating a working macOS virtual machine, consider importing it into more performatnt 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 `documentation` for further information. QEMU and KVM require additional configuration that is beyond the scope of the script.
|
||||||
|
|
||||||
#### Bootloaders
|
#### Bootloaders
|
||||||
The macOS VirtualBox guest is loaded without extra bootloaders, but it is compatible with [OpenCore](https://github.com/acidanthera/OpenCorePkg/releases). OpenCore requires 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](https://github.com/acidanthera/OpenCorePkg/releases). OpenCore requires additional configuration that is beyond the scope of the script.
|
||||||
|
|||||||
Reference in New Issue
Block a user