therealchjones / mkmacvm Goto Github PK

Build a simple macOS virtual machine for Parallels Desktop without interaction

License: Other

Shell 86.16% Python 13.84%

mkmacvm's Introduction

Welcome. Have a look around if you wish, but I don't come here often. I mostly just make notes in Gists if I'm looking into something that may be useful to others. If you'd like to reach out, you're more likely to find me on my Mastodon feed.

mkmacvm's People

Contributors

Stargazers

Watchers

mkmacvm's Issues

when softwareupdate updates macOS version, privacy & analytics appears on first login

Bring network up before trying softwareupdate in postinstall

consider not changing host machine user/.ssh/known_hosts

Make startinstall.py respond to changes rather than just `sleep`

# TODO:

mkmacvm/startinstall.py

Line 197 in 967b032

sendEnter(vm, io)

should take shell from host install if in /etc/shells

Remove Install macOS Monterey.app if downloaded?

shell-init getcwd error from createhomedir

run postinstall in debug mode, after createhomedir -c -u chjones:

./postinstall: shell-init: error retrieving current directory: getcwd: cannot access parent directories: Permission denied

but goes on to work properly anyway

consider enabling passwordless sudo during postinstall

does it have access? This would obviate the need for typing password

move docs to readthedocs.io

`softwareupdate` starts the graphical InstallAssistant if already downloaded

Currently closing manually, but distracting; would love to not have it pop up

integrate all other scripts into the body of mkmacvm

Could even make which program is run dependent on $0 and copy itself from ./mkmacvm to packagedir/postinstall

mkmacvm overwrites .ssh/known_hosts entry with same name as vm

softwareupdate doesn't consistently update when run in post install

Fix disk ejecting via postinstall

just abandon doing it in postinstall and remove it from the Parallels virtual CD after shutdown

set time zone

ssh user does not have access to many folders

requires "full disk access". May require MDM deployment to get it to work, such as: https://github.com/rtrouton/profiles/tree/main/EnableFullDiskAccessforSSH

change to levels of verbosity config

-v: verbose
-vv: debug
-vvv: debug + set -x

sometimes install image stays mounted

if createinstallmedia fails, it may leave the temporary installation image in a strange state, where it is not mounted but is attached per hdiutil info. Cleanup does not appear to account for that possibility.

Review code/features for compliance with the guiding aims

Create user with default tool instead of dscl

This is in line with guiding principle of keeping as much "default" as possible

Consider "--vagrant" option

Eg to set up base or vanilla vagrant box

determine what configuration options should be supported

from README Aims, mkmacvm should:

original version:

not have options for configuring the virtual machine by the end user (i.e.,
changing display or text output or the name of the virtual machine is
acceptable)

new version:

support very limited configuration options

My preference would be to include only those options which are necessarily done during the mkmacvm process rather than afterward. The easiest examples are those which change what mkmacvm displays---certainly if there are to be different levels of output during the mkmacvm process, this can't be done after the mkmacvm process completes, so having -h or -v options makes sense. Other options are not as straightforward. For instance, if SSH were optional (rather than always enabled), it would make sense as an option, since leaving it until afterward would mean it couldn't be turned on via the command line, because SSH would not be available. On the other hand, creating an additional user, installing most software, changing lots of different VM and OS configurations, and many other tasks can be done after mkmacvm completes, and should therefore not be options to mkmacvm.

This issue will remain open for suggestions, recommendations, requests, and other discussion regarding addition or removal of command line options to mkmacvm.

Send keystrokes to the VM. Can perhaps tell when the VM is nearly ready to receive them using ping macOS.shared.
Delve into the createinstallmedia installation disk to see if we can bypass the language chooser and menu
Is it worth, in the interim, turning the installation menu into one that has the install script available?