[Support] SpaceinvaderOne - Macinabox


Recommended Posts

2 hours ago, steve1977 said:

Happy new year to all of you!

 

I have pricked my Macinabox VM a few weeks ago and now finding the time trying to fix it.

 

All used to work well. I think I did an attempt for an upgrade and since then pricked and can no longer start. I switched back from GPU to VNC to eliminate one source of failure.

 

Unfortunately, I only get a Mac logo upon start. This stays for over an hour / forever. So, I cannot even start up.


Below what I am seeing in the log. Please let me know if anything else I can share for troubleshooting. Thanks!

 

https://pastebin.com/ciUjDKwW

Nothing useful in the vm log, as a first try, replace the bootloader with this image:

https://github.com/SpaceinvaderOne/Macinabox/raw/84a82e54ae5f596f492ead2f2d98767029e2826a/bootloader/OpenCore.img.zip

 

If it doesn't boot attach diagnostics.

Link to comment

I'm a total newb, but I'm assuming from the latest comments that we're out of luck on using Macinabox right now? Mine installs Monterey no matter what, as others have mentioned. After going through the entire install procedure twice per SI1's video, I get to loading up the VM the final time after OS install and VM settings tweaks, I get the OpenCore Boot Menu where I have to select the boot disk, then I get the attached text on the screen and nothing else happens. 😕

 

Hopefully he can get this tweaked soon!

macinabox.png

Link to comment
7 hours ago, ghost82 said:

Nothing useful in the vm log, as a first try, replace the bootloader with this image:

https://github.com/SpaceinvaderOne/Macinabox/raw/84a82e54ae5f596f492ead2f2d98767029e2826a/bootloader/OpenCore.img.zip

 

If it doesn't boot attach diagnostics.

Thanks a lot. I was into all of this, but it has been too long, so I forgot. Can you remind me where/how to replace the bootloader file?

Link to comment
9 hours ago, steve1977 said:

Can you remind me where/how to replace the bootloader file?

I don't use macinabox, sorry, but easy way is to check from your xml.

Just see the path of the opencore img file and replace it (hoping that you didn't replace bootloader files in the main mac os disk..)

Link to comment

Folks, been using MacInABox (clover flavour) for a long time with no problems. However,  recently the SSD I was using for the VM died (complete failure).

 

Needed to re-install and retrieve files from TimeMachine, I updated MacInABox and successfully got my Catalina back up and running on OpenCore. (AMD RX580 GPU passed through).

 

Except it's not stable. The main problems are;

 

1. Network access to unRaid shares is glacial, though internet browsing is OK. (I have e1000-82545em configured, no issues accessing shares from a real Mac)

2. Programs (in particular Adobe Illustrator) is causing the OS to freeze regularly

3. Playing any video file in a browser will always cause the OS to freeze after 15-20 seconds.

 

Rebooting the VM fixes the OS freeze, until the next time.

 

I'm not at all familiar with OpenCore so am really stuck as to where I can even start to troubleshoot. Rock Solid on Clover. Multiple Problems on Open Core. Any insights? Back to clover?

Link to comment
On 1/3/2022 at 12:07 AM, Mattaton said:

I'm a total newb, but I'm assuming from the latest comments that we're out of luck on using Macinabox right now? Mine installs Monterey no matter what, as others have mentioned. After going through the entire install procedure twice per SI1's video, I get to loading up the VM the final time after OS install and VM settings tweaks, I get the OpenCore Boot Menu where I have to select the boot disk, then I get the attached text on the screen and nothing else happens. 😕

 

Hopefully he can get this tweaked soon!

macinabox.png

I have exact the same issue...

image.png.c2ede3ecb4e4ab5cd1f6002c890d820a.png

Edited by Boxswurst
screenshot
Link to comment
25 minutes ago, Boxswurst said:

I have exact the same issue...

image.png.c2ede3ecb4e4ab5cd1f6002c890d820a.png

Well, at least we can say we followed the videos correctly? I guess. 😄
Misery loves company! I hope he gets it patched soon. I want to play. Haven't messed with MacOS in decades! 

Link to comment
2 minutes ago, ghost82 said:

Please read some pages of this thread and you will find solutions for this.

Most (near all) of the issues related to mac os are covered in this thread and in this discussion:

 

Thanks @ghost82

First off, as mentioned, I'm new to Macinabox, Mac VMs, VMs, and unRAID...in order from least to most familiar. 😄
I tried doing a search of this thread for some text in what I was seeing, but I didn't come up with much. Once I saw that there was a base issue with Macinabox where it was installing the latest version (Monterey) no matter which version you chose to install, and that MIAB wasn't set up to handle Monterey yet (latest version in MIAB is Big Sur), I just assumed that was the problem.

I have no idea what the whole Core Configurator and all that is doing. I'm guessing it's some intercept to fool MacOS into thinking it's booting from "authentic" hardware so it'll actually boot?

 

Again, I followed SI1's video to the letter (twice) and it didn't work, so I'm not sure where to even start to fix it. I'll have another poke around in the threads and see if I can find anything.

 

Thanks!

  • Like 1
Link to comment
15 hours ago, Mattaton said:

I tried doing a search of this thread for some text in what I was seeing, but I didn't come up with much. Once I saw that there was a base issue with Macinabox where it was installing the latest version (Monterey) no matter which version you chose to install, and that MIAB wasn't set up to handle Monterey yet (latest version in MIAB is Big Sur), I just assumed that was the problem.

With the current container you have basically 2 issues:

1. It downloads monterey, despite method 1 or 2

2. opencore is outdated

 

I wrote some prs to fix, but they are not merged yet:

https://github.com/SpaceinvaderOne/Macinabox/pulls

 

1. You have 2 choices: manually fix the container with new prs:

or uninstall macinabox and create the mac os vm manually.

xml in github repository is still valid:

https://github.com/SpaceinvaderOne/Macinabox/blob/master/xml/Macinabox BigSur.xml

just change paths for the disks and to ovmf files.

 

2. it could not boot monterey and if you use opencore configurator (recent versions) it will break the entire efi

 

Link to comment
5 minutes ago, ghost82 said:

I wrote some prs to fix, but they are not merged yet:

https://github.com/SpaceinvaderOne/Macinabox/pulls

 

I guess a third choice would be to wait for the PRs to be merged, uninstall MIAB as SI1 describes in his video, and then reinstall the new version. Then it should work if I follow his video, correct? In theory?

 

I'm all for tinkering, I just haven't researched and gotten my head into all the details of installing a Mac VM. Obviously, it's much more complicated than installing a Windows VM. 🙂 

 

Thanks!

Link to comment
4 hours ago, Boxswurst said:

So, now I tried to create a Catalina VM and get Monterey. After doing all steps and dismount die EFI Partition i run in the exact same issue. As long as i use the "Catalina-opencore.img" (for Monterey???) everything works just fine.

Looks like @ghost82 has already pointed us (and others) in the right direction here:

I'm going to give it a shot this evening.

  • Like 1
Link to comment
6 hours ago, Mattaton said:

I swapped out the opencore.img file as described below and still have the same problem. 😕

Oh well. I'll just wait for a new version of MIAB and then see what happens.

 

 

 

How did you swap out opencore? Where is the file located?

Link to comment
19 minutes ago, steve1977 said:

 

How did you swap out opencore? Where is the file located?

I did it as @ghost82 described in his post that @KittenMittons said worked for him in the comment I linked to previously. Here's the original comment with the steps:

I must be missing something in what his Step 7 means. (Again, I am a straight-up newb.) Does mount partition and change SMBIOS mean the step where we copy the EFI files to the MacOS disk? Now I'm seeing that his step 8 says NOT to copy the EFI files, but I don't know what else was done in Step 7.

What does changing the SMBIOS look like? What part of SpaceInvaderOne's video did that?

 

Sorry, I'm being dense. 😄 

Link to comment

I seem to be going from bad to worse. All kinds of seemingly unrelated issues.

 

I have fully cleaned out MIAB several times. Here is what's happening...

After creating the VM with the MIAB helper script, I then try to run the VM to install the OS. I get this:

1443801659_ExErrorCODE.png.e77a04c4fbe8542ae2c5829543033c1f.png

 

That led me to realize that the Macinabox_VARS-pure-efi.fd file was not being downloaded. So I downloaded that from GitHub and manually added it to the custom_ovmf folder. That let the VM start.

 

But then I get this:1104866619_displaynotinitialized.thumb.png.be3b5c1941104fe88cec74882a0ebb22.png

 

As I said, I've fully removed MIAB, the VM, appdata, Docker template, etc. I've rebooted my server. Other VMs are running fine. I'm not sure what's wrong here. First time I've seen this. I've installed MIAB yesterday and created VMs, installed MacOS, I just couldn't get it to boot. I started over today and now I can't even get into the VM. 😞 

Edited by Mattaton
Link to comment
On 10/28/2021 at 2:04 AM, ghost82 said:

Hi, as promised I tested the OpenCore.img and it has no issue, I'm able to boot and install mac os, I tried monterey, but the same applies for big sur and catalina.

Now..the easiest way for you, since the original img included in macinabox is still able to install mac os (<-- not true, see below), could be:

 

1. clean the container and the data, spaceinvadersone tell how to do it in his video, this is very important, maybe double check also with terminal commands that everything is deleted

 

2. install again macinabox and install mac os as you did for the first time (<-- not possible, product id is no longer valid, see below)

 

3. do not change smbios data, do nothing, just shutdown mac os

 

4. From unraid, or from another box, download the new opencore.img from

https://github.com/SpaceinvaderOne/Macinabox/raw/2a2400c44af497a00f2610523cb0c0844d2aae27/bootloader/OpenCore.img.zip

and extract it from its zip archive

 

5. From unraid, go to /isos/ (opencore.img should be in the isos share)

Delete BigSur-opencore.img (should be named like this, or similar) and paste the new OpenCore.img you just downloaded and extracted, rename it to the same name it was the deleted one

 

6. Boot mac os

 

7. Download opencore configurator 2.51.0.0 to mount partition and change smbios

https://mackie100projects.altervista.org/download/opencore-configurator-2-51-0-0/

 

8. Side note: you can not copy/replace the efi files from the opencore.img to the mac os disk; by this way if you mess something it will be easier to just replace the opencore img instead of mounting the efi partition inside the vdisk.img (mac os disk)

 

This worked for me. I'm now running Monterey. Maybe it's the Opencore bootloader file that did the trick. 

 

Thanks @ghost82!

Link to comment
22 minutes ago, TekDRu said:

 

This worked for me. I'm now running Monterey. Maybe it's the Opencore bootloader file that did the trick. 

 

Thanks @ghost82!

Thanks. Can you help with a bit more detail on the steps above?


Re "Clean container & data" - Not sure whether I found the right video (first post?) and where this is explained. Does "clean" mean for me to delete the container and also the appdata folder?

Link to comment

Thanks, I have followed the video and removed the macinabox docker and appdata.

 

How now to install the docker again (step 2)? I already have a Mac VM, which stopped working. So, what do I need to set up to "reactivate" it? Do I need to set a vdisk size? Do I need to change the folders? etc.

Link to comment
27 minutes ago, steve1977 said:

How now to install the docker again (step 2)? I already have a Mac VM, which stopped working. So, what do I need to set up to "reactivate" it? Do I need to set a vdisk size? Do I need to change the folders? etc.

 

For me, at the time that I cleaned out macinabox, I also removed the mac VM. I did so to make sure I went through all the steps properly, but I'm not sure if removing the VM is necessary. I did leave the old vdisk as-is but after successfully installing macos, I went back and deleted the old vdisk.  I believe macinabox will create the VM and vdisk for you, so you can delete both before starting all over.

Link to comment

@steve1977 I realize that you had your VM working at one point, so I can see why you wouldn't want to delete the VM or vdisk like I did.  This was my first time ever in getting it to work, so I had nothing to loose in VM or vdisk.  Maybe for your case, it just the new opencore img that you need, but I'm not an expert here.  @ghost82 may be able to shed some light for you.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.