AutoPilot

Introduction

So, what is AutoPilot? Are we talking about an Airbus A320? Nope, just some random GitHub project on the internet. Regardless, here's the rundown.

AutoPilot is a script developed by me - Coopydood - to automate the creation of an executable QEMU script file. However, it doesn't just automate it, it also personalises it based on your preferences.

The way it works is by asking you - the user - a series of questions about your preferences for the virtual machine. This includes things like the virtual CPU cores, allocated RAM, target OS, etc. Then, AutoPilot uses this information to generate a fully-customised script file, derived from a pre-made base script - with all your preferences.

The generated script file is immediately valid and can be run instantly after AutoPilot completes - which in most cases is under 3 minutes - depending on what you choose to customise. This makes it super easy to get a basic macOS VM up and running with zero user tinkering, all while catering to personal preferences.

With the intro out of the way, I'll now go into more detail about each AutoPilot stage, including acceptable values and how to enter them.

---

1. Name your config file

This really is as simple as it sounds. You can choose what you want the file name of the config script to be. This can be an alphanumeric string with no special characters except _ and -.

Default	Accepted	Examples
boot.sh	[string].sh	macOS.sh macOS-1015.sh ultimate_kvm.sh

---

2. Set target OS

This setting only really has one definitive use right now - virtual network adapter model auto selection. Other than that, it is purely cosmetic at this time. It's still recommended to set this value properly in case future functionality and features depend on it.

If defining a custom value, only a 4-digit value for macOS 10.XX releases, or a 2-digit value for macOS 11 or later is accepted. Do NOT include any subversions (i.e. 10.13.6, 10.15.7, etc.).

Default	Accepted	Examples
1015	10XX (10.XX) XX (>=11)	1013 1014 11 12