-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Unable to boot #124
Comments
Also looked at Big Sur and Sonoma get same error the autopilot script worked without error messages in the log file and screen said success. |
Hello! Can I ask you to provide your system specifications and autopilot logs if possible? |
Ubuntu 24.10 |
Hello, please let me know if you need anything else for resolving this boot issue! |
Hello, might need something else too - run the script back, go to Compatibility Checks... and then run System Profiler, and send the .log that it gives, please. For now can't figure out the root of the cause... |
Results SPT_26-09-2024_11-37-09.log |
So we are starting to piece some some stuff together and we see maybe this is about memory? But in order to verify that, I will (for last time I hope) ask you for your generated vm-script. It should be somewhere in your project's root directory (aka where you launch main.py at) |
Ah. In the boot script, you've tried to specify 4 threads on 2 cores - but QEMU multiplies the amounts together for total thread count, so think of your virtual machine using literally 8 cores. For it to launch, you will need to change this value to:
Please tell me if this fix has worked for you. Cheers! |
TODO: Write this in the GOTCHAS page |
Changed to 2 threads and still get the same issue, it's nice of you for taking the effort, thanks. |
Does it straight up not boot or gets to some point on macOS bootloader? |
When I run the boot.sh the system will either reboot or just stop and gives the error code listed above. |
...wait, like, the entire host system? |
Unable to boot on
Vendor: LENOVO Lenovo Legion 5 15ARH05 laptop
Crashes during boot with errors on Ventura, Monterey , Sequoia.
Errors 152 service cannot load in current environment for launchd
The text was updated successfully, but these errors were encountered: