On 5/25/2024 at 11:18 AM, plantsandbinary said:

I gave up on this whole thing. Nothing but hours wasted and even after 1 week I can't send a message. Pretty sure my account is shadowbanned and I cbf'ed trying to get it to work. Just told my relatives if they want to speak to me they can get Whatsapp or something.

 

I'm not as young and bored as I used to be so tinkering with this sort of thing is just a waste of my time. Thanks a ton to everyone who helped. I hope the information I provided will lead people in the right direction or help convince them that their time is more precious.

@plantsandbinary I'm sorry this didn't end up working for you.  I think the difficulty is troubleshooting without a control device.  If you have a friend who can sign in with their credentials on the MacVM and they can communicate, then you can rule out the VM as being the issue.  If you can sign in on someone's apple device that works for them, you will know if it's your appleid that is't working.

 

I still believe since you can message yourself that the appleid has been activated and isn't blocked from apple, but I can be completely wrong.  I wouldn't suggest a wipe and fresh install of the mac os before troubleshooting further, but it's all I can think of to help.   Again, sorry this was such a waste of time, but if you manage to figure out a fix in the future, feel free to share an update.

 

Good luck! 

Honestly it's much easier and safer for your Apple ID to go on eBay and buy an old Mac Mini or Macbook Air and use that to host BlueBubbles. OCLP is great for installing a newer version, currently the best version to use for BlueBubbles is Ventura and it's pretty much set and forget.

 

I keep a Macbook Air with a dummy HDMI plug and ethernet adapter sitting on top of my Unraid server with an iPhone plugged into it charging for phone number registration. My setup is bridged into Beeper and everything works great.

15 hours ago, mackid1993 said:

Honestly it's much easier and safer for your Apple ID to go on eBay and buy an old Mac Mini or Macbook Air and use that to host BlueBubbles. OCLP is great for installing a newer version, currently the best version to use for BlueBubbles is Ventura and it's pretty much set and forget.

 

I keep a Macbook Air with a dummy HDMI plug and ethernet adapter sitting on top of my Unraid server with an iPhone plugged into it charging for phone number registration. My setup is bridged into Beeper and everything works great.

I agree it's easier when money isn't a factor, but it's another hardware set to maintain and use power.

 

I don't know what you are inferring about "safer for your Apple ID, " as using an Apple ID on a VM is not inherently dangerous.  People may not understand the cause when something goes wrong, but no need to jump to conclusions that apple is going to blacklist an account when it's never happened.  Temporary difficulties and lock outs occur, but I have yet to hear about a permanent ban from a user.

 

Finding a bargain on a used Mac mini like the 2018 version that allows a person to upgrade the RAM and run the latest macOS smoothly will be less work than getting this working on the server.  Some of us like to tinker, and others just want it to work without hassle.  To each their own:)

 

 

Hey Guys,

is there an estimation on when Sonoma will be available?

On 6/23/2024 at 6:13 AM, bl00dy-c0d3 said:

Hey Guys,

is there an estimation on when Sonoma will be available?

You can search around for guidance, but it can be installed with some effort, see previous post on this topic: 

 

On 6/19/2023 at 9:03 PM, VJO said:

hello everyone, this being my first attempt in installing mac vm, following SIO's  youtube video, but i am struck in installation where it says "an internet connection is required to install macOS", what i have missed ?

For anyone coming across this issue, for me it was caused by the "Machine" setting, it worked when I set it back to Q35-4.2

 

Has anyone verified success doing a brand new Macinabox install while running Unraid 7.0.0-beta1?

 

 

11 minutes ago, Espressomatic said:

 

Has anyone verified success doing a brand new Macinabox install while running Unraid 7.0.0-beta1?

 

 

this is on my to do list. I have not gotten to that step in my dev testing.

Currently, finishing docker networking stuff and will post back when i have more information. As the new beta 7 has other kvm spots for qemu and that will come in handy for "hackintsh" / the mac in the box docker to run.

Unless the docker has finally been updated. the last mac os form the docker is Big Sur reliable in my testing and will be tested when i run as such.

 

I can say that any docker made VM did transfer and runs under the VM tab in beta 7.

As said ealrier i can confirm premad docker images in 6 still work in beta 7 just not have tried the docker in 7 to se if it still makes a VM.

 

Beta 7 has some nice vm updates:

Setting VM:

 

vms ex:

 

 

 

6 minutes ago, bmartino1 said:

just not have tried the docker in 7 to se if it still makes a VM.

 

I've also successfully ran the image I made in 6.12 while running 7, but I didn't have success making a new image when I tried. It was just some quick testing but I was hitting a wall and haven't gone back to try again.

 

 

Edited July 10, 20241 yr by Espressomatic

18 hours ago, bmartino1 said:

images in 6 still work in beta

 

I'm having an issue where (most) VM vdisk files won't boot and instead go straight to UEFI shell when I try to import into 7-beta - this is by creating a new VM and using the prervious vdisk.

 

In my testing, this has affected VMs for Fedora Server 40, Debian 12 and MacOS. Strangely, it doesn't affect my Home Assistant vdisk.

On 3/16/2024 at 7:02 PM, OldManBeard said:

<interface type='bridge'> <mac address='xx:xx:xx:xx:xx:xx'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </interface>

 

This was the only thing I was able to do to see Ethernet and have it Connected in the Mac VM. Otherwise, without any manual edits, only a serial port is ever displayed

 

7.0.0-beta.1 doesn't ever list "e1000-82545em" as available, just "e1000" - and manually changing to that doesn't make Ethernet show up.

 

If you make the changes above, but use "e1000" instead, Ethernet will show up, but will be disconnected with no way to make it work.

 

Macinabox most definitely doesn't work properly in 7.0.0-beta.1 and likely 6.12.10 either. No matter what oddball setting you leave for interface, running the helper script always says it's correct.

 

Your network type was already correct. Network has not been changed.

 

But it does always seem to revert to Virtio-Net - which doesn't work in MacOS to show any Ethernet support.

Edited July 12, 20241 yr by Espressomatic

Do you have any ETA for the Macinabox update? There was a mention of a new version in one of Spaceinvader One's recent videos. Thank you for everything!

3 hours ago, jafi said:

Do you have any ETA for the Macinabox update? There was a mention of a new version in one of Spaceinvader One's recent videos. Thank you for everything!

@SpaceInvaderOne has not posted any updates here, what video are you referring to?

On 11/6/2023 at 5:34 PM, Pirokiki said:

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

Hi I successfully installed big sur. trying sonoma. I did all the steps above but i am stuck at part 5 it does not go further the efi command lines. i always go back to uefi shell not the recovery screen.

any tips? thanks

On 11/6/2023 at 5:34 PM, Pirokiki said:

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

 

THANKS!!

I've successfully installed sonoma with your guidelines and its working well.
BUT! I have 100% cpu spikes doing low process intensive tasks like browsing a single tab web or opening some os windows. 
I'm running a i3 10100 host cpu with 2cores 2threads and 16GB of ram dedicated to vm. 
I suspect it's a GPU emulation thing as i only have my igpu.

Can I do something on configuration (increase gpu ram, some qemu settings...) to speed up things? It's really slow.

Thanks!!

Edited August 8, 20241 yr by Mamaun

1 hour ago, Mamaun said:

to speed up things? It's really slow.

all macos vm without dedicated dGPU passthrough are "slow" and eating CPU Power ...

 

so i would guess, not really ... you can increase the cores as mentioned before, but macos really aint fun without a dGPU in my experience ...

Yeah macos is basically unusably slow with no supported GPU, even if you give it 16 cores...

Oh. I see.. 

So the next question is what is the cheapest dgpu to passthrough to the VM? And, can it be fully shutdown when I don't use the VM?

3 hours ago, Mamaun said:

And, can it be fully shutdown when I don't use the VM?

to answer this, no, you can set it in persistent mode to spare something ... but in sum it ll always use power in idle

 

1/ the gpu itself (sample, rtx3080ti 4 W, GTX 1060 6 W)

2/ but ... as soon pcie slots are in use (also in idle), the board itself will use more ... here as sample, about 10-12 W just for keeping the cards in the slots ... in persistent idle mode

 

3 hours ago, Mamaun said:

what is the cheapest dgpu to passthrough to the VM?

cant answer this one as its AMD only meanwhile afaik ... and im out with them  due too many passthrough issues overall.

 

my macos testings stopped with sierra (last Nvidia capable macos)

Hello,

 

quick Question : I had an Monterey VM with a 6600xt passthrough created by macinabox. I added agdpmod=pikera  to get the display working

 

I update the opencore to the latest version and changed the xml command line to 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='ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off'/>
    <qemu:arg value='-global'/>
    <qemu:arg value='nec-usb-xhci.msi=off'/>
    <qemu:arg value='-cpu'/>
    <qemu:arg value='Haswell-noTSX,vendor=GenuineIntel,+invtsc,+hypervisor,kvm=on,vmware-cpuid-freq=on,+avx,+avx2,+ssse3,+sse4.2,+popcnt,+aes,+fma,+bmi1,+bmi2,+xsave,+xsaveopt,+rdrand,+kvm_pv_eoi,check'/>
  </qemu:commandline>

 

After that I upgraded to sonoma and the VM starts without problem, but I cannot get the GPU working.

 

I notice that maps is not working which is the symptom that hardware acceleration is not activated. Of course no external display.

 

All is working well with VNC ( but slow )

 

I tried to upgrade the lilu.ktxt and the whatevergreen.ktxt to the latest version, but no way to get the GPU working.

 

Am I missing something ?

EDIT: updated the container and it now runs perfectly

 

-------------------------------------------------------

 

Hi all,

 

I hope this post is in the correct place and is intelligible

 

I followed all instructions and as far as I can see my XML is fine and I also ran and re-ran the new macinabox which I think was updated yesterday.

 

I am getting the "Guest has not initialized the display (yet)."

 

My server is running on 12th Gen Intel® Core™ i5-12400 @ 2475 MHz, 32GB RAM. UNRAID 6.12.13.

 

I'm giving it 8 of 12 cores...

 

I'll include my XML (minus the key) and after this the VM log.

 

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>Sonoma</name>
  <uuid>6bf37a5a-94f8-42bc-9a3d-62049fe4330b</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" icon="macinabox.png" os="osx" webui="" name="Linux"/>
  </metadata>
  <memory unit='KiB'>8388608</memory>
  <currentMemory unit='KiB'>8388608</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>8</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='2'/>
    <vcpupin vcpu='1' cpuset='3'/>
    <vcpupin vcpu='2' cpuset='6'/>
    <vcpupin vcpu='3' cpuset='7'/>
    <vcpupin vcpu='4' cpuset='8'/>
    <vcpupin vcpu='5' cpuset='9'/>
    <vcpupin vcpu='6' cpuset='10'/>
    <vcpupin vcpu='7' cpuset='11'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-7.2'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/6bf37a5a-94f8-42bc-9a3d-62049fe4330b_VARS-pure-efi.fd</nvram>
  </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'/>
  </cpu>
  <clock offset='utc'>
    <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/user/domains/Sonoma/Sonoma-opencore.img'/>
      <target dev='hdc' bus='sata'/>
      <serial>vdisk1</serial>
      <boot order='1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/isos/Sonoma-install.img'/>
      <target dev='hdd' bus='sata'/>
      <serial>vdisk2</serial>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/Sonoma/macos_disk.img'/>
      <target dev='hde' bus='sata'/>
      <serial>vdisk3</serial>
      <address type='drive' controller='0' bus='0' target='0' unit='4'/>
    </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='0x11'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0x12'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
    </controller>
    <controller type='pci' index='5' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='5' port='0x13'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
    </controller>
    <controller type='pci' index='6' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='6' port='0x14'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/>
    </controller>
    <controller type='pci' index='7' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='7' port='0xa'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    </controller>
    <controller type='pci' index='8' model='pcie-to-pci-bridge'>
      <model name='pcie-pci-bridge'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x03' 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='ac:87:a3:5b:17:2f'/>
      <source bridge='br0'/>
      <model type='virtio-net'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 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'/>
    <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <audio id='1' type='none'/>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x08' slot='0x01' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
    </memballoon>
  </devices>
  <qemu:commandline>
    <qemu:arg value='-device'/>
    <qemu:arg value='isa-applesmc,osk=thisiswherethekeygoeswedontpostontheforums'/>
    <qemu:arg value='-smbios'/>
    <qemu:arg value='type=2'/>
    <qemu:arg value='-usb'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='usb-tablet'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='usb-kbd'/>
    <qemu:arg value='-cpu'/>
    <qemu:arg value='Skylake-Server,vendor=GenuineIntel,+hypervisor,+invtsc,kvm=on,+fma,+avx,+avx2,+aes,+ssse3,+sse4_2,+popcnt,+sse4a,+bmi1,+bmi2'/>
  </qemu:commandline>
</domain>

 

2024-09-23 07:26:14.777+0000: starting up libvirt version: 8.7.0, qemu version: 7.2.0, kernel: 6.1.106-Unraid, hostname: Reliquary
LC_ALL=C \
PATH=/bin:/sbin:/usr/bin:/usr/sbin \
HOME=/var/lib/libvirt/qemu/domain-3-Sonoma \
XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-3-Sonoma/.local/share \
XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-3-Sonoma/.cache \
XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-3-Sonoma/.config \
/usr/local/sbin/qemu \
-name guest=Sonoma,debug-threads=on \
-S \
-object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-3-Sonoma/master-key.aes"}' \
-blockdev '{"driver":"file","filename":"/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \
-blockdev '{"driver":"file","filename":"/etc/libvirt/qemu/nvram/6bf37a5a-94f8-42bc-9a3d-62049fe4330b_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}' \
-machine pc-q35-7.2,usb=off,dump-guest-core=off,mem-merge=off,memory-backend=pc.ram,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format \
-accel kvm \
-cpu host,migratable=on,host-cache-info=on,l3-cache=off \
-m 8192 \
-object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":8589934592}' \
-overcommit mem-lock=off \
-smp 8,sockets=1,dies=1,cores=4,threads=2 \
-uuid 6bf37a5a-94f8-42bc-9a3d-62049fe4330b \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=35,server=on,wait=off \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=utc,driftfix=slew \
-global kvm-pit.lost_tick_policy=delay \
-no-hpet \
-no-shutdown \
-boot strict=on \
-device '{"driver":"pcie-root-port","port":8,"chassis":1,"id":"pci.1","bus":"pcie.0","multifunction":true,"addr":"0x1"}' \
-device '{"driver":"pcie-root-port","port":9,"chassis":2,"id":"pci.2","bus":"pcie.0","addr":"0x1.0x1"}' \
-device '{"driver":"pcie-root-port","port":17,"chassis":3,"id":"pci.3","bus":"pcie.0","addr":"0x2.0x1"}' \
-device '{"driver":"pcie-root-port","port":18,"chassis":4,"id":"pci.4","bus":"pcie.0","addr":"0x2.0x2"}' \
-device '{"driver":"pcie-root-port","port":19,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x2.0x3"}' \
-device '{"driver":"pcie-root-port","port":20,"chassis":6,"id":"pci.6","bus":"pcie.0","addr":"0x2.0x4"}' \
-device '{"driver":"pcie-root-port","port":10,"chassis":7,"id":"pci.7","bus":"pcie.0","addr":"0x1.0x2"}' \
-device '{"driver":"pcie-pci-bridge","id":"pci.8","bus":"pci.1","addr":"0x0"}' \
-device '{"driver":"ich9-usb-ehci1","id":"usb","bus":"pcie.0","addr":"0x7.0x7"}' \
-device '{"driver":"ich9-usb-uhci1","masterbus":"usb.0","firstport":0,"bus":"pcie.0","multifunction":true,"addr":"0x7"}' \
-device '{"driver":"ich9-usb-uhci2","masterbus":"usb.0","firstport":2,"bus":"pcie.0","addr":"0x7.0x1"}' \
-device '{"driver":"ich9-usb-uhci3","masterbus":"usb.0","firstport":4,"bus":"pcie.0","addr":"0x7.0x2"}' \
-device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.3","addr":"0x0"}' \
-blockdev '{"driver":"file","filename":"/mnt/user/domains/Sonoma/Sonoma-opencore.img","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-3-storage"}' \
-device '{"driver":"ide-hd","bus":"ide.2","drive":"libvirt-3-format","id":"sata0-0-2","bootindex":1,"write-cache":"on","serial":"vdisk1"}' \
-blockdev '{"driver":"file","filename":"/mnt/user/isos/Sonoma-install.img","node-name":"libvirt-2-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-2-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-2-storage"}' \
-device '{"driver":"ide-hd","bus":"ide.3","drive":"libvirt-2-format","id":"sata0-0-3","write-cache":"on","serial":"vdisk2"}' \
-blockdev '{"driver":"file","filename":"/mnt/user/domains/Sonoma/macos_disk.img","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-1-storage"}' \
-device '{"driver":"ide-hd","bus":"ide.4","drive":"libvirt-1-format","id":"sata0-0-4","write-cache":"on","serial":"vdisk3"}' \
-netdev tap,fd=36,id=hostnet0 \
-device '{"driver":"virtio-net","netdev":"hostnet0","id":"net0","mac":"ac:87:a3:5b:17:2f","bus":"pcie.0","addr":"0x3"}' \
-chardev pty,id=charserial0 \
-device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \
-chardev socket,id=charchannel0,fd=34,server=on,wait=off \
-device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \
-device '{"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"}' \
-audiodev '{"id":"audio1","driver":"none"}' \
-vnc 0.0.0.0:0,websocket=5700,audiodev=audio1 \
-k en-us \
-device '{"driver":"qxl-vga","id":"video0","max_outputs":1,"ram_size":67108864,"vram_size":67108864,"vram64_size_mb":0,"vgamem_mb":16,"bus":"pci.8","addr":"0x1"}' \
-device '{"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.5","addr":"0x0"}' \
-device '************************' \
-smbios type=2 \
-usb \
-device usb-tablet \
-device usb-kbd \
-cpu Skylake-Server,vendor=GenuineIntel,+hypervisor,+invtsc,kvm=on,+fma,+avx,+avx2,+aes,+ssse3,+sse4_2,+popcnt,+sse4a,+bmi1,+bmi2 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
char device redirected to /dev/pts/1 (label charserial0)
2024-09-23T07:26:14.839965Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.hle [bit 4]
2024-09-23T07:26:14.839990Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.rtm [bit 11]
2024-09-23T07:26:14.839993Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512f [bit 16]
2024-09-23T07:26:14.839996Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512dq [bit 17]
2024-09-23T07:26:14.839998Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512cd [bit 28]
2024-09-23T07:26:14.840001Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512bw [bit 30]
2024-09-23T07:26:14.840004Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512vl [bit 31]
2024-09-23T07:26:14.840007Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6]
2024-09-23T07:26:14.840010Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 5]
2024-09-23T07:26:14.840013Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 6]
2024-09-23T07:26:14.840015Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 7]
2024-09-23T07:26:14.840843Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.hle [bit 4]
2024-09-23T07:26:14.840849Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.rtm [bit 11]
2024-09-23T07:26:14.840852Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512f [bit 16]
2024-09-23T07:26:14.840855Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512dq [bit 17]
2024-09-23T07:26:14.840857Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512cd [bit 28]
2024-09-23T07:26:14.840860Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512bw [bit 30]
2024-09-23T07:26:14.840863Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512vl [bit 31]
2024-09-23T07:26:14.840866Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6]
2024-09-23T07:26:14.840869Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 5]
2024-09-23T07:26:14.840873Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 6]
2024-09-23T07:26:14.840876Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 7]
2024-09-23T07:26:14.841579Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.hle [bit 4]
2024-09-23T07:26:14.841584Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.rtm [bit 11]
2024-09-23T07:26:14.841587Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512f [bit 16]
2024-09-23T07:26:14.841590Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512dq [bit 17]
2024-09-23T07:26:14.841592Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512cd [bit 28]
2024-09-23T07:26:14.841594Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512bw [bit 30]
2024-09-23T07:26:14.841598Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512vl [bit 31]
2024-09-23T07:26:14.841603Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6]
2024-09-23T07:26:14.841609Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 5]
2024-09-23T07:26:14.841613Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 6]
2024-09-23T07:26:14.841617Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 7]
2024-09-23T07:26:14.842292Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.hle [bit 4]
2024-09-23T07:26:14.842296Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.rtm [bit 11]
2024-09-23T07:26:14.842299Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512f [bit 16]
2024-09-23T07:26:14.842302Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512dq [bit 17]
2024-09-23T07:26:14.842304Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512cd [bit 28]
2024-09-23T07:26:14.842306Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512bw [bit 30]
2024-09-23T07:26:14.842309Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512vl [bit 31]
2024-09-23T07:26:14.842313Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6]
2024-09-23T07:26:14.842319Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 5]
2024-09-23T07:26:14.842324Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 6]
2024-09-23T07:26:14.842328Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 7]
2024-09-23T07:26:14.843004Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.hle [bit 4]
2024-09-23T07:26:14.843008Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.rtm [bit 11]
2024-09-23T07:26:14.843011Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512f [bit 16]
2024-09-23T07:26:14.843013Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512dq [bit 17]
2024-09-23T07:26:14.843016Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512cd [bit 28]
2024-09-23T07:26:14.843018Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512bw [bit 30]
2024-09-23T07:26:14.843021Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512vl [bit 31]
2024-09-23T07:26:14.843025Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6]
2024-09-23T07:26:14.843031Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 5]
2024-09-23T07:26:14.843035Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 6]
2024-09-23T07:26:14.843039Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 7]
2024-09-23T07:26:14.843590Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.hle [bit 4]
2024-09-23T07:26:14.843594Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.rtm [bit 11]
2024-09-23T07:26:14.843597Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512f [bit 16]
2024-09-23T07:26:14.843599Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512dq [bit 17]
2024-09-23T07:26:14.843602Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512cd [bit 28]
2024-09-23T07:26:14.843605Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512bw [bit 30]
2024-09-23T07:26:14.843609Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512vl [bit 31]
2024-09-23T07:26:14.843614Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6]
2024-09-23T07:26:14.843619Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 5]
2024-09-23T07:26:14.843623Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 6]
2024-09-23T07:26:14.843627Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 7]
2024-09-23T07:26:14.844477Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.hle [bit 4]
2024-09-23T07:26:14.844481Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.rtm [bit 11]
2024-09-23T07:26:14.844483Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512f [bit 16]
2024-09-23T07:26:14.844486Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512dq [bit 17]
2024-09-23T07:26:14.844488Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512cd [bit 28]
2024-09-23T07:26:14.844491Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512bw [bit 30]
2024-09-23T07:26:14.844493Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512vl [bit 31]
2024-09-23T07:26:14.844497Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6]
2024-09-23T07:26:14.844502Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 5]
2024-09-23T07:26:14.844507Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 6]
2024-09-23T07:26:14.844511Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 7]
2024-09-23T07:26:14.845182Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.hle [bit 4]
2024-09-23T07:26:14.845186Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.rtm [bit 11]
2024-09-23T07:26:14.845189Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512f [bit 16]
2024-09-23T07:26:14.845191Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512dq [bit 17]
2024-09-23T07:26:14.845194Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512cd [bit 28]
2024-09-23T07:26:14.845197Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512bw [bit 30]
2024-09-23T07:26:14.845201Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.avx512vl [bit 31]
2024-09-23T07:26:14.845206Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6]
2024-09-23T07:26:14.845212Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 5]
2024-09-23T07:26:14.845216Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 6]
2024-09-23T07:26:14.845220Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 7]
qxl_send_events: spice-server bug: guest stopped, ignoring

 

Edited September 23, 20241 yr by Moniker Lewinski

When you see  "Guest has not initialised the display yet". This is due to the nvram the vm is using. This can happen with any VM windows, Mac, linux.

Easiest fix. Just delete the vm (but dont select select disks). Run macinbox again. It will see the disks already there and will not need to download again. It will recreate the nvram and xml template. 
then run the VM and you should be good

 

NEW MACINBOX AT LAST !!

Now I know many people have been asking for updates to this container for a long time.  So firstly sorry for the wait, but hopefully its worth it.
I decided too fully rewrite it and add new features. Now supports all macOS from High Sierra to Sonoma. 
Macinabox is now self-contained and no longer requires any helper scripts being able to fix xml itself.  
It dynamically build the XML based off not only the choices made in the container template but also by checking the host for which is latest qemu etc and building accordingly.

Also rerunning the container fixes XML problems, replacing missing custom xml, making sure the NIC is on the correct bus so macOS see it and can use it. And if you have an odd core count  macinabox will see this and remove the topology line to ensure the VM still boots

I have made the container so it will be much easier in future for me to update so expect more regular updates going forward.
Any suggests please let me know and open a request on GitHub    https://github.com/SpaceinvaderOne/Macinabox


Here is a video showing its use.
 

Basic Usage.
 

• Set notifications to Detailed.

• Configure Docker update notification to any option other than Never (e.g., Once per Day).

 

Installation Steps

 

1. Compliance: Ensure you are compliant with the Apple EULA for macOS virtual machines. Select whether you are compliant or not.

2. Select OS: In the template, choose the macOS version you wish to install.

3. VM Name: By default, Macinabox uses the OS name for the VM. If you prefer a different name, enter it in the Custom VM Name field (default is blank).

4. VDisk Type: Choose the vdisk type: Raw or QCOW2. The default option is Raw.

5. VDisk Size: Specify the size for the macOS vdisk in gigabytes. The default size is 100 GB.

6. Default Variables: You can leave all other settings as default. If needed, you can change the default locations for your domains, ISOs, or appdata shares.

 

Running the Container

 

• Launch the container. It will download the recovery media from Apple servers, name it, and place it in your ISO share.

• The container will create your vdisk and an OpenCore image for your VM, which will be placed in your domain share within a folder named after your VM.

• The XML for the VM will be dynamically generated based on your settings, and the container will perform checks on your server:

• It will check the version of QEMU installed and calculate the highest compatible version of Q35.

• It will set the default VM network source in the XML.

• It will add the appropriate custom QEMU command line arguments to the XML.

 

Notifications

 

During the container’s operation, you will receive notifications:

 

• When the installation media has been successfully downloaded.

• When the VM has been defined and is available on the VMs tab of your server.

• Or if any errors occur during the process.

 

Additional VM Configuration

 

Once the VM is installed, you may want to adjust it to your preferences:

 

1. On the Unraid vm tab. Click the vm and click edit. Now modify the CPU core count and RAM amount as needed.

 

Fixing broken XML Configuration

 

When making changes to the VM in the Unraid VM manager, the XML will be changed making the VM XML inorrect for macOS, which requires specific configurations. To fix this:

 

• Run Macinabox again. It will check if a macOS VM with the specified name already exists. If it does, it will fix the XML instead of attempting to install another VM. (This step is necessary for both Unraid 6 and 7.)

• If you make any changes to the VM in the Unraid VM manager, be sure to run the container again to update the XML.

 

Starting the VM

 

1. Start the VM and open a VNC window to proceed with the installation.

2. Boot into the OpenCore boot loader and select the bootable image labelled macOS Base System. Press Enter to continue.

 

Installing macOS

 

1. Once booted into recovery media, open Disk Utility to format your vdisk.

2. After formatting, close Disk Utility and select Reinstall macOS. Follow the wizard to complete the installation. The installation process may cause the VM to reboot approximately four times.
 

Hope you guys like this new macinabox

2 hours ago, SpaceInvaderOne said:

When you see  "Guest has not initialised the display yet". This is due to the nvram the vm is using. This can happen with any VM windows, Mac, linux.

Easiest fix. Just delete the vm (but dont select select disks). Run macinbox again. It will see the disks already there and will not need to download again. It will recreate the nvram and xml template. 
then run the VM and you should be good

 

Hi Ed,

I'm having the same issue, tried the fix but still the same.

 

I'm running on AMD Epyc.

 

It turns out I had to remove the nvram file manually (located in /var/lib/libvirt/qemu/nvram).

 

Also, if I make any changes to the cpu allocation, it won't boot for the 1st time.

 

So i kept the cpu assigned to 0 and 2 from the original template, and set ram to 16GB in the xml.

 

Now i'm doing the initial boot and install, I'll try to change cpu allocations after it's up and running (if that happens...)

 

Thanks!