Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation troubles when there's not enough space on startup volume #23

Open
tempelmann opened this issue Jun 12, 2022 · 0 comments
Open

Comments

@tempelmann
Copy link

tempelmann commented Jun 12, 2022

TL;DR – User should be given the choice to specify the location of the freshly created VM, especially if the startup disk's space is not sufficient. Also, when moving a freshly created VM, it loses its Boot IPSW image.

I am trying to install macOS on an MB Air M1.

My M1 Mac's disk layout is that I have a fairly small partition for just the macOS system, and then symlink most of the home folders (Desktop, Downloads, Documents) to a different volume that has lots of space. The Library folder remains private to the system partition, though.

The problem with the UTM installation is that it does not ask me where I want to store the VM initially. It always places it in its Sandbox container's Documents folder, which is on the startup disk. In my case, that's too small.

So I retried: I create a new macOS VM with the IPSW, and before starting it, I use the UTM UI to move the VM to another volume. That appears to work, but then I find that it has lost the IPSW reference that I had specified during the VM setup, because when I start the VM now, it'll open a large black screen and nothing happens, not even an error, and no prompt whether I want to install macOS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant