Hey,

 

anyone know, how to set it up with vhost0? If is set it up with chost0 to get an extra IP which I would be able to access with guacamole, I don't have ethernet connection.

 

If I set it up with virbr0 I have ethernet connection on VM, but then the VM would not have a IP which i can reach.

 

Any idea?

Do I need to compile OpenCore to enable kernel display after successfully completing the installation? Otherwise, his interface cannot perform basic operations

Does the VM start for you?

On 12/16/2024 at 3:29 PM, h3llfire83 said:

I myself have had difficulties for months using macinabox with a graphics card after a motherboard change.
I even recently updated to the latest Unraid version, although it's a beta, but without success.
Apparently, the issue lies with the selected QEMU version. With all the new versions, despite correct IDs and multifunction=1 for the graphics card, I was never able to boot the VM successfully with the graphics card.
The VM would get stuck at the Apple logo.

In the meantime, I also had trouble passing through a dedicated USB-PCI card correctly.
Over VNC, there were never any issues.

I am using a 6800XT and not a 6900 like you (here, the card may need to be spoofed).
What works for me now is QEMU version 6.0; unfortunately, anything above that doesn’t work and causes the VM to hang at the Apple logo again.

Maybe this helps someone.

Can someone explain why it works with QEMU v6.0 and why other QEMU versions cause this issue?
I’m just glad to have GPU passthrough working again under Unraid and macOS, and I’m happy, but I'm still curious about the root cause.
Of course, I have updated OpenCore. I was about to give up since this issue has been frustrating me for months, and without graphics acceleration, macOS wasn’t really usable for my purposes.

 

Tried QEMO 6.0 - didnt change anything for me - get stuck at apple boot screen at the same line (see screenshot)

 

I am not able to bring my 6900XT to work with macinabox 😞

 

 

I've been a long time Unraid user, it's fantastic as a NAS solution with very easy docker implementation and I have a 18 core Xeon setup with 128GB ram that I was hoping to use the Unraid VM functionality to run MacOS as the machine was always on 24/7 anyway.

 

I have tried and failed repeatedly get GPU (and USB controller) passthrough for MacOS working under Unraid 7 (currently running 7.0.0-rc2). I've had it running on earlier unRaid versions and MacOS installs.

 

With MacOS Ventura through to Sequoia, I've used Spaceinvader One's macinabox to install the machines and they run fine without any passthrough in a VNC session. As soon as I try and pass through a GPU, I can't get passed the initial apple logo screen (no progression on the progress bar). If I just pass through a USB controller, the VM doesn't seem to see it either. I have no problem with passthrough in a Windows 10 or 11 VM, both GP and USB pass through works fine.

 

I've tried various versions of Q35 machines and custom xml edits but I think the problem lies with the underlying linux kernel/KVM used by unRaid.

 

I also have quite a lot of experience running proxmox and this has been great for VM's, I can get a MacOS Sequoia (15.2) VM working with full functionality, iMessage, handoff etc etc (only things that don't work are T2 chip related such as iPhone mirroring and apple intelligence) so I've given with MacOS VM setup in Unraid up and gone back to my hybrid setup

 

It's been well documented within the proxmox community that the linux kernel 6.x+ broke PCI passthrough for certain setups and especially MacOS VM's. By booting earlier linux kernels, pci passthrough works fine. I have a proxmox install that runs the Linux 5.15.158 kernel which handles passthrough in MacOS flawlessly. 

 

I'm now running proxmox as my base bare metal install and configure and run VM's directly from proxmox. I then run Unraid as a VM with necessary controllers (HBA, USB, Nvidia GPU for hardware plex transcoding etc) passed through.

 

The UnRaid VM handles all my NAS needs for storage and backup and docker needs such as Plex, Sonarr, radar etc. I can seamlessly have the UnRaid VM running 24/7 and then boot up a windows 11 VM with Nvidia GPU passed through and a MacOS Sequoia VM with an AMD RX 580 passed through simultaneously and running smoothly with full functionality.

 

If the passthrough issues do get resolved in UnRaid, I'll move back to that as my hypervisor to save config faff and complexity but for now it seems that no one seems to have gpu passthrough working very well.

still cant passthrough RX580 in unraid 7 rc2. stuck at apple logo with 0% progress bar... need help...
it seems like happens on all MacOS version

On 11/10/2024 at 2:16 PM, wewantrice said:

Could anyone point me to current resources detailing how to get iMessage working? When I set up my Big Sur VM using macinabox many moons ago I got locked out of my apple account after signing in to apple services on the VM. Had to call Apple to unlock. I then used this guide to get iMessage working. I've got a Sonoma VM running now using this updated version of macinabox.

 

Is this method still applicable?

Did anybody get this going?  Does that method still work?  I'm looking to do the same with a VM i just built with Ventura and was hoping to find proper instructions to get imessage going.

any idea how to get things like maps to show the map? i just see the application with the map being black.

20 hours ago, st1994 said:

Did anybody get this going?  Does that method still work?  I'm looking to do the same with a VM i just built with Ventura and was hoping to find proper instructions to get imessage going.

I followed this guide.  I get to where i sign into imessage and it works and kicks me right out after a few seconds.  Then if i login again and just let it sit idle, it does the same and kicks me out after a few seconds.

mac in the box as a apple vm docker maker is not meant for Hackintosh setups.

I use this more for my Apple device to get an apple environment for easier recovery and recovery making...
 

Quote

 

Tldr: Yes definitely but be prepared to tinker

As others say, it may (or may not) require a bit of effort. A factor to consider is having natively compatible hardware (Intel CPU, avoid dGPUs in laptops as far as I know).

You need to also keep in mind that it is possible to get your Apple account suspended by logging in on a Hackintosh, especially if you don’t follow instructions on configuration of your serial number and ROM to a point.

Specifically with serial numbers, you have the option of choosing an invalid serial number or one that belongs to a real Mac with the same SMBIOS as your Hack but not in use (purchase date not validated).

Using the latter can be helpful in getting things to work, but can be dangerous in the long run. Some have had luck with invalid serials, especially if your account is in good standing with Apple (think of it kind of like an internal credit score Apple as, said to be improved by having a credit card on file, some purchases, etc.) I personally in my most recent Hack used an invalid serial to no avail and called Apple, complaining that the iMac I had just bought on Ebay wasn’t working with iMessage and Facetime, saying the seller had said he had upgraded it. After a bit more than an hour on the phone, they released the block.

Many people wouldn’t be comfortable doing this, but I was fine with it since I have a long history on my Apple account and a good amount of legit devices registered. Plus, I had an unrelated issue with iMessage/Facetime my genuine Macbook, so I needed to call anyway

If you haven’t already found it, I’d like to point you to this guide on installing macOS with OpenCore. Make sure to give it a read before jumping out in anything.

https://dortania.github.io/OpenCore-Install-Guide/

 

as this docker implements open core to install this in unraids VM systems.

if not, make your own with https://dortania.github.io/OpenCore-Legacy-Patcher/

Edited January 3, 20251 yr by bmartino1
typo

This would be great if you could install to a container instead and get gpu accel like they do with steam-headless.

 

I have installed macos in a container before using this (but I didn't try gpu):   https://github.com/sickcodes/Docker-OSX

 

It works really well.

5 hours ago, uek2wooF said:

This would be great if you could install to a container instead and get gpu accel like they do with steam-headless.

 

I have installed macos in a container before using this (but I didn't try gpu):   https://github.com/sickcodes/Docker-OSX

 

It works really well.

I have found that most implementation of dockers for a OS usually involve running kvm.qemu with in a linux environment. the issue with device passthoguh has more to do with editing the kvm/qemu within the docker and adds a layer of complexity.

easy enoth to have the docker see and use it, not easy enouth to get the kvm/qemu osx to use the dockers hardware given...

That is a neat project.
 

20 hours ago, uek2wooF said:

I have installed macos in a container before using this (but I didn't try gpu):   https://github.com/sickcodes/Docker-OSX

 

It works really well.

This just sets up a VM, so same thing as built-in. 

Edited January 6, 20251 yr by Kilrah

On 12/23/2024 at 10:09 AM, mikep70 said:

 

Tried QEMO 6.0 - didnt change anything for me - get stuck at apple boot screen at the same line (see screenshot)

 

I am not able to bring my 6900XT to work with macinabox 😞

 

 

 

 

Can you give me some Details ?
Do you have setup the Bootarguments ?
 

agdpmod=pikera

Maybe you can fix it : 
https://github.com/TylerLyczak/Unsupported-6900XT-Hackintosh-Fix

keep my fingers crossed🤞

But still i dont know why it does not work with other QEMU Version above 6.0

 

On 1/2/2025 at 9:12 AM, notepads said:

still cant passthrough RX580 in unraid 7 rc2. stuck at apple logo with 0% progress bar... need help...
it seems like happens on all MacOS version

I had it running in earlier Versions (macOS 11/12) under a earlier Unraid Build, but i replaced it with the 6800XT and other HW
 

Has anyone managet to passthrough the iGPU? I'm currently running Sequioa macinabox without any problems. Would like to passthrough my iGPU from my 12600k processor. 

On 1/3/2025 at 12:19 PM, st1994 said:

I followed this guide.  I get to where i sign into imessage and it works and kicks me right out after a few seconds.  Then if i login again and just let it sit idle, it does the same and kicks me out after a few seconds.

If you set up the icloud account with your new VM, it may not be an approved imessage account yet.  Check here and see if this helps: 

 

Installing the VMHide kext resolves the issue with Apple accounts on macOS Sequoia. After installing the kext, I was able to click continue on the "Update Apple account settings" prompt and it succeeds.

Has anyone been able to passthrough usb devices? Couldn't passthrough my iphone

I've been playing around with passthrough again in Unraid (V7.0.0) and finally got my GPU (rx580) and a PCIe USB controller passed through and working.

 

My system is an Intel Xeon, this 'fix' may not work for everyone and I've not done enough testing to see if it can be refined at all with some of the arguments used:

 

1.  Click on Main tab then the flash drive and replace the line that reads ‘append initrd=/bzroot’ under the UnraidOS box in the syslinux configuration with the following:

          

append video=vesafb:off,efifb:off initcall_blacklist=sysfb_init default initrd=/bzroot

 

2.  Install MacOS using Macinabox as per video/instructions and configure as required. Mine was already installed and working under VNC. As I'm on intel, I'm using CPU host passthrough passthrough arguments in the Macinabox docker configuration.

 

3.  Stub GPU and any other passthrough devices (Tools/System devices) and reboot

 

4.  Edit VM config and add GPU and PCI cards as required.

 

5.  Start Macinabox docker to correct XML

 

6.  Go back and edit VM, switch to form view and locate the following line:

 

<type arch='x86_64' machine='pc-q35-9.1'>hvm</type>

Replace machine type q35-9.1 with q35-6.0

 

7.  Save but do not start macinabox docker again otherwise it will revert the machine type to 9.1

 

8.  Boot VM and hopefully you get video passthrough.

On 1/20/2025 at 3:45 AM, Ancalagon said:

Installing the VMHide kext resolves the issue with Apple accounts on macOS Sequoia. After installing the kext, I was able to click continue on the "Update Apple account settings" prompt and it succeeds.

As a complete MacOS noob, I do not understand how to install this. Can you give me some explanation about how to install this? 

19 hours ago, de Techneut said:

As a complete MacOS noob, I do not understand how to install this. Can you give me some explanation about how to install this? 

You'll need to edit your EFI partition. You can use a tool like OpenCore Configurator to mount the partition or just run this command from the terminal:

sudo diskutil mount EFI

 

Kexts are located under EFI/OC/Kexts. Download the latest VMHide-X.X.X-RELEASE.zip and extract. Copy VMHide.kext to EFI/OC/Kexts.

 

You'll also need at least Lilu 1.7.0+. Download the latest Lilu-X.X.X-RELEASE.zip and extract. Copy and replace Lilu.kext in EFI/OC/Kexts.

 

In order to load a Kext, it needs to be configured in OpenCore's configuration, located at EFI/OC/config.plist. You can open it in a plist editor, like ProperTree, or just a text editor. Under Kernel->Add add an item for VMHide.kext, similar to the other entries (Lilu should already be there), after the last entry and before </array>. The entry should look like this:

<dict>
  <key>Arch</key>
  <string>Any</string>
  <key>BundlePath</key>
  <string>VMHide.kext</string>
  <key>Comment</key>
  <string></string>
  <key>Enabled</key>
  <true/>
  <key>ExecutablePath</key>
  <string>Contents/MacOS/VMHide</string>
  <key>MaxKernel</key>
  <string></string>
  <key>MinKernel</key>
  <string>23.0.0</string>
  <key>PlistPath</key>
  <string>Contents/Info.plist</string>
</dict>

 

Note Enabled is set to true, so the kext is loaded and MinKernel set to 23.0.0 since it's only required in macOS Sequoia+.

 

Save the config.plist file and reboot. The VMHide kext should be loaded and working now.

Thank you for this, I'm having issues with open core configurator saying the version of open core is outdated. If I'm using the method you detailed above do I also need to change the mac serial so it's invalid? Went through this process with my Big Sur vm I have running but that was many moons ago and would like to update to a newer macos. 

5 hours ago, wewantrice said:

Thank you for this, I'm having issues with open core configurator saying the version of open core is outdated. If I'm using the method you detailed above do I also need to change the mac serial so it's invalid? Went through this process with my Big Sur vm I have running but that was many moons ago and would like to update to a newer macos. 

If all you're using OpenCore Configurator for is mounting the EFI partition, you can ignore that version warning. It applies to using the configurator to modify the OpenCore bootloader. I'd still recommend updating your OpenCore bootloader anyway though.

 

It's similar to updating kexts, but a little more involved. There are detailed instructions in the guide. The basic steps are:

1. Backup your vdisk in case anything goes wrong, so you can revert
2. Mount the EFI partition (as described above)
3. Download the latest OpenCore version
4. Copy and replace the files from the release's X64 folder to the EFI partition
5. Compare your EFI/OC/config.plist file with the Docs/Sample.plist in the release using a file comparison utility
6. Add any new keys from the Sample.plist to your config.plist
7. You can look up the purpose of the keys and potentially change the values as needed
8. Reboot and confirm everything's working as expected

I also recommend updating any other kexts that you have in your EFI/OC/Kexts folder to their latest versions.

Hey Everyone, I have installed Sequoia and got to the desktop, but when I try and install a app from the app store and try and log in, I get "Verification Failed: Unknown Error Occurred". I saw a couple of replies similar but no definitive explanation as to how to fix this issue.  Things I have tried are switching the Network adapter to e1000.