I was about to install MacInABox, but have decided to wait a bit. I appreciate the hard work that has been put into this and look forward to the next revision.

Edited January 26, 20224 yr by JackSafari

Thanks for everything you did, i love this docker and it's was really helpful!

The new version it's coming out today or has it been delayed?

will it support monterey too?

When will the new Macinabox be available ?

Thanks

On 1/30/2022 at 1:19 AM, PicPoc said:

When will the new Macinabox be available ?

Thanks

 

I heared a rumor, that it will be out, as soon as Ed will finish working on it absolutely free of charge, voluntarily in his free time.

Edited January 31, 20224 yr by Doublemyst
typo fix

Finally the new Macinabox is ready. Sorry for the delay work has been a F******G B*****D lately taking all my time.

 

So It also has a new template so please make sure to make sure your template is updated too (but will work with the old template)

 

A few new things added.

Now has support for

Monterey

BigSur

Catalina

Mojave

High Sierra.

 

You will see more options in the new template.

Now as well as being able to choose the vdisk size for install you can also choose whether the VM is created with a raw or qcow2 (my favorite!) vdisk

The latest version of Open core (OpenCore to 0.7.7.)  is in this release. I will try and update the container regularly with new versions as they come.

However you will notice a new option in the template where you can choose to install with stock opencore (in the container) or you can use a custom one.
You can add this in the folder custom_opencore folder in Macinabox appdata folder. You can download versions to put here from

https://github.com/thenickdude/KVM-Opencore/releases

Choose the .gz version from here and place in the above folder and set template to custom and it will use that (useful if i am slow in updating !! 🤣)  - note if set to custom but Macinabox cant find a custom opencore here to unzip in this folder then it will use the stock one.

Also there is another option to delete and replace the existing opencore image that your vm is using. Select this to yes and run the container and it will remove the opencore image from the macos version selected in the template and replace with a fresh one. Stock or custom.

By default the NICs for the macOS versions are virtio for Monterey and BigSur. Also vDisk Bus is virtio for these too.

HighSierra, Mojave and Catalina use a sata vDisk Bus. They also use e1000-82545em for there NICs.

The correct NIC type for the "flavour" of OS you choose will automatically be added.

However if for any macOS you want to overide the NIC type and install then you can change the default NIC type in the template from Virtio, Virtio-net, e1000-82545em or vmxnet3

By default the NIC for all vms is on

<address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>

This will make the network adapter seem built in and should help with Apple services.

 

Make sure to delete the macinabox helper script before running new macinabox so the new script is put in as there are some changes in that script too.

 

I should be making some other chnages in the next few weeks soon, but thats all for now

 

 

 

11 hours ago, SpaceInvaderOne said:

<address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>

An important clarification!

bus 0x01 is not "built-in", bus 0x00 is.

 

However, in the code in github it is (in)correctly set to bus 0x00.

"Incorrectly" because the address of the nic is currently set at bus 0x00, slot 0x00 and function 0x00, which should be a reserved address for host bridge!

 

This should be changed to bus 0x00, slot 0x02 and function 0x00

Um yeah thanks for pointing that out.

 

The problem is, is that Unraid VM manager on an update from making a change in the GUI (not xml edit) will automatically change the nics to be on bus 0x01 hence address to

 <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>

 

I will take a look at this and perhaps add to the macinabox helper script to fix this.

Hi, 

 

Firstly "good work" to SpaceInvaderOne.

 

Secondly, I am wondering if anyone can help. 

 

I deleted my old Mac VM and now when I am try to run the VM for the first time I get the attached error: I suspect strongly I have b**gered something up, maybe I left half a macinabox lying around. I have tried deleting everything and reinstalling but still no luck. 

Any pointers?

 

Thanks

 

Edited January 31, 20224 yr by Black Aura

I'm never seeing my BigSur/Monterey (tried both) disks upon first reboot after the initial config and disk erase/reconfig - only getting macOS Base System, macOS Installer, Recovery, UEFI Shell, and reset NVRAM. Before this newest version I was able to see the new BigSur disk I created. If I pick either of the first two options it takes me back through the initial install process but my BigSur disk is already formatted. I'm using default settings otherwise and I've tried deleting the scripts, docker, and deleting the appdata twice and retrying, but with the same results...

 

Thank you for your hard work in making it easier for us to install and use MacOS!
I tried to install High Sierra with your various tutorials. Each time I had various and varied problems, probably because of the hardware.
With the new MacInABox I am installing HighSierra, congratulations for working it again.
I noticed excessive slowness when writing files to volumes. The same is true for speeds via the network.
Here is a screenshot of the installation which takes a very long time:

My machine has an X79 motherboard and 64GB of RAM with an SSD.

 

Once again thank you for MacinaBox which helps me to understand MacOS virtualization and all the work you have brought us.

Seems to be faster in RAW (First test was with qcow2 !)

 

 

I try to use HighSierra in passthru with a NVIDIA K600 : works. But no mouse & no keyboard.

I don't know how opencore works

Edited January 31, 20224 yr by PicPoc

5 hours ago, Black Aura said:

Hi, 

 

Firstly "good work" to SpaceInvaderOne.

 

Secondly, I am wondering if anyone can help. 

 

I deleted my old Mac VM and now when I am try to run the VM for the first time I get the attached error: I suspect strongly I have b**gered something up, maybe I left half a macinabox lying around. I have tried deleting everything and reinstalling but still no luck. 

Any pointers?

 

Thanks

 

Are you trying to install Catalina? I'm having the same issue on Catalina. Big Sur installed nicely but I'm having this issue with Catalina. Also the Iso default location is not used in the xml (looking for the iso under /isos/macinabox catalina/ which it shouldn't) so I'm guessing something is off with the template.

Hmm...and now while trying to delete the VM I'm getting:

 

Requested operation is not valid: cannot undefine domain with nvram

 

Edit: managed to clear that out by running virsh undefine --nvram "Macinabox BigSur"

Edited January 31, 20224 yr by polishprocessors

I presume OS X + my 2070 Super is still out of the question?

8 hours ago, polishprocessors said:

I'm never seeing my BigSur/Monterey (tried both) disks upon first reboot after the initial config and disk erase/reconfig - only getting macOS Base System, macOS Installer, Recovery, UEFI Shell, and reset NVRAM. Before this newest version I was able to see the new BigSur disk I created. If I pick either of the first two options it takes me back through the initial install process but my BigSur disk is already formatted. I'm using default settings otherwise and I've tried deleting the scripts, docker, and deleting the appdata twice and retrying, but with the same results...

 

I have this exact same issue, I've tried several times and looked over the XML as well but can't see what I'm missing.  Once installation completes and the system reboots the disk image where MAC OS is installed never appears.

1 hour ago, mrubich16 said:

I have this exact same issue, I've tried several times and looked over the XML as well but can't see what I'm missing.  Once installation completes and the system reboots the disk image where MAC OS is installed never appears.

 

On first reboot, you have to choose "macOS Installer" to complete installation.

 

11 hours ago, EG-Thundy said:

Are you trying to install Catalina? I'm having the same issue on Catalina. Big Sur installed nicely but I'm having this issue with Catalina. Also the Iso default location is not used in the xml (looking for the iso under /isos/macinabox catalina/ which it shouldn't) so I'm guessing something is off with the template.

This makes sense. I'm also having the issue with Monterey, I'll try Catalina or Big Sur tomorrow just to see but I get the "master var store" error.

17 hours ago, EG-Thundy said:

Are you trying to install Catalina? I'm having the same issue on Catalina. Big Sur installed nicely but I'm having this issue with Catalina. Also the Iso default location is not used in the xml (looking for the iso under /isos/macinabox catalina/ which it shouldn't) so I'm guessing something is off with the template.

I am having the same issue with Monterey, Big Sur, Catalina. I tried method 1 and method 2.

 

I suppose I could try the other versions.

There's no more method 1 and 2

12 hours ago, AceRimmer said:

I presume OS X + my 2070 Super is still out of the question

exactly.

Did you know why install is a little bit slow ?

Before for HighSierra, now for Catalina :

Installation is not from disk to disk, but it's a network installation, meaning that you download the base system image and then download from apple servers the installer.

3 minutes ago, ghost82 said:

Installation is not from disk to disk, but it's a network installation, meaning that you download the base system image and then download from apple servers the installer.

OK, I understand now. 

Catalina-install.img & HighSierra-install.img are just a part of DVD install. Thanks !

I tried wiping out the OpenCore image by setting the setting to 'yes' in the docker image and then 'no' as it directed me, but, despite the log claiming it put it in my vm share:

 

OpenCore bootloader image named BigSur-opencore.img was put in your Unraid vm share in the folder named BigSur

 

it did not appear there. 

11 hours ago, PicPoc said:

 

On first reboot, you have to choose "macOS Installer" to complete installation.

 

Correction, for both me and anyone else with the similar issue. I had to choose MacOS Installer *twice* (the first reboot + ~30m of install, the second reboot + ~5m of install) before I saw my disk relabeled BigSur. Then I had to go through the usual (from previous Macinabox install attempts) multiple reboots to get it to install. I'll see how it goes from here, but so far so good, just didn't expect this from previous attempts...