New Macinabox almost complete. Should be out soon. Hoping for the end of next week or shortly there after
Will have a few new features such as Ventura and Sonoma support
Also the companion User Scripts will no longer be necessary, the container will do everything itself.
Also I plan to add checks so the container can see that your cpu has the correct features to be able to run macOS ie checking for AVX2 etc
And a few other new things

 

Nice ! Again a good & hard work !!!

What about the aivability to install from an image on USB stick ?

Have just installed https://www.kasmweb.com and wow being able to run full desktops in browser from a single container!

 

Will see if we can integrate macinabox to this. Might not be possible but would be cool.

Edited October 5, 20232 yr by dopeytree

5 minutes ago, PicPoc said:

Nice ! Again a good & hard work !!!

What about the aivability to install from an image on USB stick ?

Hi there. Unfortunately, integrating the ability to install from a usb stick directly into macinabox is not feasible due to the existing mechanisms and how the vm templates are generated. To utilise USB media for installation, a manual edit of a vm template to enable usb passthrough would be necessary. However, a simpler alternative, if you need to install the os from a usb, would be converting your usb media to an image file. This would allow you to utilise an existing image on your usb without requiring direct passthrough of the actual physical device to the VM template.

the macinabox docker seems to stop itself after creating the user scripts; if i start it again, i do not see the option to launch the WebUI for virt-manager. Is virt-manager no longer included in the docker image? have i missed a part of the procedure?

My Big Sur installs have been successful following the video guide in this post, but i would like to manage with virt-manager if still possible.

Thanks for the great work.  I have been unsuccessful getting the mac VM to install.  It creates the VM, but then when I choose macOS Base System, I get a message that the computer restarted because of an error.  It then goes back to the screen with macOS Base System, UEFI Sherr, Reset NVRAM and seems to loop thru this.  I have tried installing both Monterey and Big Sur with no luck.  My unraid server has a ryzen 7 5700g.  Any help you can give is greatly appreciated.

On 12/14/2022 at 2:26 AM, BUSTER said:

I have been using Macinabox Monterey on my Unraid for a long time and now I would like to connect my macOS to a monitor without VNC,

 

After a lot of research, I decided AMD Radeon HD 7770, I Dump the Vbios self and also assigned it in Unraid, but when I start it, the VM goes to a CPU 100% and it doesn't run, also downloaded Bios Dump from TechpowerUP same issue.

 

As a test I assign the macOS the Graphics card from my Windows VM, it is an Nvidia Quadro P600, this works, I get screen on the Monitor, but since High Sierra there has been no Nvidia driver for macOS.

 

Tested the AMD HD 7770 on Windows VM with self generated and Downloaded Bios Dump it Works be fine.

 

On the Dortania page I read that I have to include the following in the config.plist "radpg=15" (Fixes initialization for HD 7730/7750/7770/R7 250/R7 250X), I did that too, but still no success.

 

On the Dortania page there is also the following about this AMD HD 7770 card --> InjectAMD: While deprecated, some users require this for proper initialization, avoid unless absolutely necessary,

I didn't understand what is meant by that --> InjectAMD, can anyone comment on it , would be super nice

 

My XML --> (Don't be unsettled by the name of the machine in the xml, I'll have to rename it later, I installed BigSur first and then updated it to Monterey)

  Reveal hidden contents

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>Macinabox BigSur</name>
  <uuid>0c84f110-2682-48e5-aad4-1bb2558f7e84</uuid>
  <description>MacOS Big Sur</description>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="default.png" os="osx"/>
  </metadata>
  <memory unit='KiB'>8388608</memory>
  <currentMemory unit='KiB'>8388608</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>8</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='4'/>
    <vcpupin vcpu='1' cpuset='12'/>
    <vcpupin vcpu='2' cpuset='5'/>
    <vcpupin vcpu='3' cpuset='13'/>
    <vcpupin vcpu='4' cpuset='6'/>
    <vcpupin vcpu='5' cpuset='14'/>
    <vcpupin vcpu='6' cpuset='7'/>
    <vcpupin vcpu='7' cpuset='15'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-4.1'>hvm</type>
    <loader readonly='yes' type='pflash'>/mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/0c84f110-2682-48e5-aad4-1bb2558f7e84_VARS-pure-efi.fd</nvram>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none' migratable='on'>
    <topology sockets='1' dies='1' cores='4' threads='2'/>
    <cache mode='passthrough'/>
    <feature policy='require' name='topoext'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/virtualmachines/VirtualMachines/Macinabox BigSur/macos_disk.img'/>
      <target dev='hdc' bus='sata'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <controller type='pci' index='0' model='pcie-root'/>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x8'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x9'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0xa'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0x13'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:5f:d8:d4'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <audio id='1' type='none'/>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
      </source>
      <rom file='/mnt/user/isos/AMD.Radeon.HD.7700.rom'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x04' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x24ae'/>
        <product id='0x2013'/>
      </source>
      <address type='usb' bus='0' port='2'/>
    </hostdev>
    <memballoon model='none'/>
  </devices>
  <qemu:commandline>
    <qemu:arg value='-usb'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='usb-kbd,bus=usb-bus.0'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='************************'/>
    <qemu:arg value='-smbios'/>
    <qemu:arg value='type=2'/>
    <qemu:arg value='-cpu'/>
    <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+avx2,+aes,+fma,+fma4,+bmi1,+bmi2,+xsave,+xsaveopt,+rdrand,check'/>
  </qemu:commandline>
</domain>

 

My System: MSI B550 Gaming Plus, Ryzen 3700X, 32GB DDR4 3200MHz Ram,

Windows 10 VM Passthrough´ed NVIDIA Quadro P600 Works fine.

issue, wold be like Passthrough AMD HD 7770 to macOS

 

I'm grateful for every tip and help

 

cYa BUSTER

 

 

Do you remember how you updated from Big Sur to Monterey? I have not been able to achieve this yet.

Hi, im getting the following error and Big Sur not showing up under the VM tab. Any suggestion on how to resolve: Script location: /tmp/user.scripts/tmpScripts/1_macinabox_helper/script
Note that closing this window will abort the execution of this script
Starting to Fix XML
error: failed to get domain 'Big Sur'
No network adapters in xml to change. Network adapter is already virtio











Added custom qemu:args for macOS
topolgy line left as is
custom ovmf added
error: Failed to define domain from /tmp/Big Surfixed.xml
error: (domain_definition):3: Extra content at the end of the document

^

This is what has been done to the xml

Your network type was already correct. Network has not been changed.
The custom qemu:args have been added to you xml.
VM is set to use custom ovmf files.
xml is now fixed. Now goto your vm tab and run the VM
Rerun this script if you make any other changes to the macOS VM using the Unraid VM manger
 

On 10/6/2023 at 4:05 AM, SpaceInvaderOne said:

New Macinabox almost complete. Should be out soon. Hoping for the end of next week or shortly there after
Will have a few new features such as Ventura and Sonoma support
Also the companion User Scripts will no longer be necessary, the container will do everything itself.
Also I plan to add checks so the container can see that your cpu has the correct features to be able to run macOS ie checking for AVX2 etc
And a few other new things

 

May I ask if there is a more detailed release plan at the moment?

On 10/5/2023 at 10:05 PM, SpaceInvaderOne said:

New Macinabox almost complete. Should be out soon. Hoping for the end of next week or shortly there after
Will have a few new features such as Ventura and Sonoma support
Also the companion User Scripts will no longer be necessary, the container will do everything itself.
Also I plan to add checks so the container can see that your cpu has the correct features to be able to run macOS ie checking for AVX2 etc
And a few other new things

 

 

Great news! Any updates yet about the release date?

Edited October 25, 20232 yr by Helmer

On 10/5/2023 at 3:05 PM, SpaceInvaderOne said:

New Macinabox almost complete. Should be out soon. Hoping for the end of next week or shortly there after
Will have a few new features such as Ventura and Sonoma support
Also the companion User Scripts will no longer be necessary, the container will do everything itself.
Also I plan to add checks so the container can see that your cpu has the correct features to be able to run macOS ie checking for AVX2 etc
And a few other new things

 

Also looking forward to this 😇

Hey @SpaceInvaderOne let us know if we can help with any testing or anything 

I'm willing to be a lab rat tester as well.  I am a well educated novice of both VM and Mac, but recently have upgraded my server enough that I've been setting up several VMs just for the learning experience.  My fresh eyes may see things that other folks who have spent more time doing this would just accept (or had configured long in the past).

I’m happy to be a tester as well. 

Hi all,
Yesterday I finally finished installing vm in my Unraid server following the YouTube video (ever if some passage - for example the EFI part - was a bit different.

I rebooted then my VM and now it is stuck at boot: I see Apple logo and the bar at 33% . No changes or progression in at least 3 hours. Before last tentative I clicked on recover and was able to reach the setup guide page but frankly I don’t want to start from scratch once again.

Any suggestions?

Thanks in advance

Hi, I managed to create Sonoma vm with some tweaks to spaceinvaderone's macinabox created template, maybe someone will find this helpful.

 

1. Firstly I have created Sonoma image with this tutorial: https://i12bretro.github.io/tutorials/0763.html (method of obtaining macOS does not matter and you skip usb creation part, just go straight to "creating bootable .iso"), but in "creating bootable.iso" part you have to make an image at least 15000m in size and change image name from *.cdr to *.img not to *.iso. than copy this image to unraid

 

2. Download mentioned earlier: https://github.com/thenickdude/KVM-Opencore/releases/download/v20/OpenCore-v20.iso.gz this also copy to unraid

 

3. Run macinabox with Monterey option (you can try custom open core, but this option didn't worked for me, I had just manually changed path in automatically created Monterey vm) and override network interface to "vmxnet3", than normally go to user scripts and run vmready_notify and helper scripts as in spaceinvaderone's tutorial but do not run newly created vm

 

4. In new monterey vm, change opencore image path to downloaded one, and change Monterey path to Sonoma path. and in the last part of xml (qemu commandline) add missing flags from part 22 of this tutorial: https://i12bretro.github.io/tutorials/0566.html , mine tweaked part looks like this:

 

  <qemu:commandline>
    <qemu:arg value='-usb'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='usb-kbd,bus=usb-bus.0'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='************************'/>
    <qemu:arg value='-smbios'/>
    <qemu:arg value='type=2'/>
    <qemu:arg value='-global'/>
    <qemu:arg value='nec-usb-xhci.msi=off'/>
    <qemu:arg value='-global'/>
    <qemu:arg value='ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off'/>
    <qemu:arg value='-cpu'/>
    <qemu:arg value='host,kvm=on,vendor=GenuineIntel,vmware-cpuid-freq=on,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+avx2,+aes,+fma,+bmi1,+bmi2,+xsave,+xsaveopt,+rdrand,check'/>
  </qemu:commandline>

 

this tweaks are working for xeon e5-2690v4

 

5.now run vm and go to UEFI shell, in UEFI shell type System\Library\CoreServices\boot.efi and it should take you to standard recovery screen, next steps are as in spaceinvaderone's tutorial

 

6. after configuration you can copy open core files (https://github.com/thenickdude/KVM-Opencore/releases/download/v20/OpenCoreEFIFolder-v20.zip) to efi partition of Sonoma installation and remove opencore and Sonoma installer entries from xml

 

7. if everything works, you can change core assignment to 4 cores 2 threads, 8gb of ram and it should boot just fine without any additional things, keep in mind that you have to edit everything in xml view because spaceinvaderone's xml fixing script won't work anymore in present form

(you can try different core count and ram size, but these just worked for me)

 

8. you can fix performance of this vm with this guide: https://github.com/sickcodes/osx-optimizer , it made huge difference with my setup

 

Performance isn't terrific, but vm is totally usable, in my case the biggest issue is graphics performance because I don't have suitable graphics for macOS and I'm stuck with qemu emulated graphics

 

edit: idk why but after posting this part of qemu args with apple osk changed to asterisks

 

edit2: i have just ran passmark, and it hit 9449, not bad I think

Edited November 6, 20232 yr by Pirokiki

5 hours ago, bmartino1 said:

 

Thank you for this information, this helped alot !!! . Unfortunate, I still seem to have an issue with getting a Monterey or newer installer working. I have a amd board and this boots bigsur.

 

Spaceinvader haven't finished working on the new Macinbox at the moment. If you try donwnload  Monterey - it download Ventura or Sonoma with opencore from BugSur( that's why you get black screen with text different languages).

I see you success install BugSur. You can passthrough gpu and use it OS

On 11/8/2023 at 4:20 AM, Exlife said:

Spaceinvader haven't finished working on the new Macinbox at the moment. If you try donwnload  Monterey - it download Ventura or Sonoma with opencore from BugSur( that's why you get black screen with text different languages).

I see you success install BugSur. You can passthrough gpu and use it OS

 

to understand this, I just tried this morning to get Monterey and it fails. You are saying that when you execute the docker it downloads the Monterey image but an version of opencore for bigsur hence the failed boot?

3 hours ago, ijuarez said:

 

to understand this, I just tried this morning to get Monterey and it fails. You are saying that when you execute the docker it downloads the Monterey image but an version of opencore for bigsur hence the failed boot?

I think so. All you can do is wait for a new release or try to manually create a VM yourself

I Don't understand the disconnect...

 

If I use the docker for Monterey setup, it downloads Sonoma labeled as montery-installer.img. This Sonma installer is in an edited recovery system with opencore v16 kvm edits meant for BigSUR. This media doesn't boot. Which could potentially be fixed if the github line was updated to grab Monterey instead of Sonoma. (Line 467) from the docker github file used to grab the installer:

 

###################

 

I don't know what the edits are being down to the recovery/install media. Nor what I would need to do to make my own using above-mentioned glib to download or my own apple disks. I have an ISO and other acquired install media, just none that boot in the VM environment with open core. My authenticate Apple ISO disk: Monterey_12.6.1_v17.6.11 doesn't boot in open core v20 KVM with the updated QEMU following the GUID or previous QEMU edits.

 

This tell same either my ISO is bad or there is a step missing making the install media.... (I even passed a disk drive to read the disk with similar) I just can't' see to get install media to boot with the white text error. Hitting enter get me to the Apple logo and eventual a forced reboot.

 

I even made a 20GB raw disk image, trying to make recovery media similar to having a USB. And dabbled with some other guides to use open core to boot, but still was not able to install nor upgrade bigsur. So I'm not sure of a MISconfiguration, but it is clear that since bigsur / catalina images downloaded via the docker boot and install in the edited XML file that there is a configuration needed for sonma and/or montery to install the OS.

 

I'm looking for that configuration or way to make the file.

atm that is this guide:

Edited November 11, 20232 yr by bmartino1
spelling

12 hours ago, bmartino1 said:

I Don't understand the disconnect...

I was able to successfully install Monterey 12.6.7

If you need, I can share the opencore and img installer. I can also tell you how to make the installer yourself.
XML from BigSur worked for me.

You can write me a private message, I can tell you how I did it.

On 11/10/2023 at 12:14 PM, Exlife said:

I think so. All you can do is wait for a new release or try to manually create a VM yourself

Yep switch back to big sur and it worked.

 

 

On 10/25/2019 at 4:12 PM, SpaceInvaderOne said:

09 Dec 2020

 

Basic usage instructions.

 

Macinabox needs the following other apps to be installed.

CA User Scripts (macinabox will inject a user script. This is what fixes the xml after edits made in the Unraid VM manager)

Custom VM icons  (install this if you want the custom icons for macOS in your vm)

 

Install the new macinabox.

 

1. In the template select the OS which you want to install

2. Choose auto (default) or manual install. (manual install will just put the install media and opencore into your iso share)

3. Choose a vdisk size for the vm

4. In VM Images: Here you must put the VM image location  (this path will put the vdisk in for the vm)

5. In VM Images again : re enter the same location  as above. Here its stored as a variable. This will be used when macinabox generate the xml template.

6. In Isos Share Location: Here you must put the location of your iso share. Macinabox will put named install media and opencore here.

7. In Isos Share Location Again: Again this must be the same as above. Here its stored as a variable. Macinabox will use this when it genarates the template.

8. Download method. Leave as default unless for some reason method 1 doesnt work

9. Run mode. Choose between macinabox_with_virtmanager or virtmanager only.

 

( When I started rewriting macinabox i was going to only use virtmanager to make changes to the xml. However I thought it much easier and better to be able to use the Unraid vm manager to add a gpu cores ram etc, then have macinabox fix the xml afterwards.

I deceided to leave vitmanager in anyway, in case its needed. For example there is a bug in Unraid 6.9.beta (including beta 35.) When you have any vm that uses vnc graphics then you change that to a passed through gpu it adds the gpu as a second gpu leaving the vnc in place.  This was also a major reason i left virtmanger in macinabox. For situations like this its nice to have another tool. I show all of this in the video guide. )

 

After the container starts it will download the install media and put it in the iso share. Big Sur seems to take alot longer than the other macOS versions. So to know when its finished goto userscripts and run the macinabox notify script (in background) a message will pop up on the unraid webui when its finished.

 

At this point you can run the macinabox helper script. It will check to see if there is a new autoinstall ready to install then it will install the custom xml template into the VM tab.

Goto the vm tab now and run the vm

This will boot up into the Opencore bootloader and then the install media.

Install macOS as normal.

 

After install you can change the vm in the Unraid VM Manager. Add cores ram gpu etc if you want.

Then go back to the macinabox helper script. Put in the name of the vm at the top of the script and then run the script.

It will add back all the custom xml to the vm and its ready to run.

 

Hope you guys like this new macinabox

What version of OpenCore Configurator is used in the YouTube.  
 

Looks like the version of open core used is 78 from the picker screen. 

 

This a bit dated.  Looking forward to your update. 
 

Dennis

Edited November 28, 20232 yr by DWomack
Add info.

I have a question. I tried searching, but maybe I'm using the wrong keywords. What additional steps do I need to do to build different VM's? Like I have a Big Sur one running, but I want to try Monterey. Also, Can you simply update the VM like normal to get OS updates to newer versions? 

I love all the community support here to get it working while we wait!

 

I will practice my zen and still wait for SpaceInvaders version as I’m sure there’s a logical reason behind delay (Work is kicking up,etc) 😌