[Support] SpaceinvaderOne - Macinabox


Recommended Posts

Hello Community, 

short question, i don't know if i have read the wrong comment but unfortunately each time when i start my MacOS, i requires manual partion selection for my Monterey so start. 
Is there any solution for an autoboot option, or is manual interaction required?

 

Cheer and thansk for help in advance

Link to comment

Hello all,

 

I've been trying to get the macinabox to install for the last three days and I keep running into the same issue, even though I believe I have followed the amazing SpaceInvaderOne's directions. Everything goes well up to the point of erasing the 107gb disk and naming it bigsur, followed by the installation. Problem is then it reboots and then goes back to a screen where the bigsur drive is gone and instead there is a drive that says MacOS Base System and when I select that drive or the MacOS Installer drive, it goes back to the reinstall OS, etc. screen. I am really stumped on this one and hoping to see if anyone has any suggestions. Thanks!

macinabox.png

Link to comment

EDIT: Issue solved by using latest modified Nvidia Web drivers obtained through Tonymacx86 forum

 

This is really good. I've got High Sierra working again after last having a working version in unraid 6.8 with Clover.

 

Unfortunately Nvidia drivers had its certificate revoked as of 1st June, so any users using Maxwell with High Sierra are also affected. There is a solution as below taken from the Tonymacx86 forum but anyone here who has been working with Hackintosh and Unraid for a long time, can sort of look through this and also provide the Opencore configurator options for it?

 

I can see some of the steps are written in a way that some one who has been working with this a long time will be able to figure out but alas I'm not one of them :D

 

https://www.tonymacx86.com/threads/the-apps-authorization-has-been-revoked-high-sierra-nvidia-graphics-certificates-expired.320609/page-3#post-2324531

 

 

Update High Sierra till lates 17G14042
Cleanup NVIDIA Web driver (WEB-Drive-Toolkit From Github)
Make this in terminal console:
sudo chmod -R 755 /Library/Extensions/NVDAStartupWeb.kext
sudo chown -R root:wheel /Library/Extensions/NVDAStartupWeb.kext
sudo touch /System/Library/Extensions/ && sudo kextcache -u /
sudo touch /Library/Extensions && sudo kextcache -u /

Add boot arguments in clover configurator as in attached screenshot
Add kext as in attached screenshot
Reboot (If you have black screen add temporary boot argument nv_disable=1)
Install official driver 387.10.10.10.40.140

1445013052_ScreenShot2022-06-05at9_44_30PM.thumb.png.e373a71bde5a9d2c14ce25b58afb78df.png1430653025_ScreenShot2022-06-05at9_29_37PM.thumb.png.5897d4e9c598c76e7f9746594f75686e.png

 

Edited by ars92
Link to comment

EDIT: Issue solved by using latest modified Nvidia Web drivers obtained through Tonymacx86 forum

 

This is how my boot-args looks like, so I added the amfi line to the existing boot-args, and there is a space in between. Apart from that I can see that I already have Lilu and WhateverGreen kext included in the kext folder of Opencore so I didn't do any changes there.

 

 I also have the nvda_drv 31 input too, but it doesn't help. I did also try to repackage the installer using a cert stripper python script. This does help to run the driver installer but no difference after a restart. 

Screen Shot 2022-06-11 at 10.32.17 PM.png

Edited by ars92
Link to comment
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

Sorry I just got my unraid server running for the first time and I tried install this and the dmg said it downloaded right away but was only bytes in size I didn’t have the CA User Scripts installed is that why it didn’t work?

Link to comment

Hello. When i passthrough video card all good. Successful launch VM. But when i passthrough mouse or keyboard i have black screen. 

maybe I'm doing something wrong? I set USB Devices in xml. Then edit 1_macinabox_helper  ( name VM) . Then start 1_macinabox_helper 

Link to comment
On 2/6/2022 at 4:38 PM, cat2devnull said:

 

So it looks like QEMU is having issue with accessing your card (assuming it is on address 04:00.0 and 04:00.1

 

When trying to debug an issue with passing a video card to the VM there are many things to consider/try.

 

1) Ensure the card is in its own IOMMU group and not sharing a group with any other hardware.

Also ensure that it is stubbed so that the host OS doesn't take control of the card.

118039272_ScreenShot2022-02-07at11_16_51am.thumb.png.b66f2b8a3391a4daf2076bc1f7f11539.png

 

2) Ensure your config is correct. Here is an example from my config. My card is on bus 0x12 and I pass it to bus 0x04.

    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x12' slot='0x00' function='0x0'/>
      </source>
      <rom file='/mnt/user/isos/vbios/Yeston-RX550-4G-LP-D5.rom'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x12' slot='0x00' function='0x1'/>
      </source>
       <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/>
    </hostdev>

 

3) Try passing the VBIOS

The goto place for VBIOS files is TechPowerUp but most people recommend that you rip your own BIOS. Spaceinvader has written some software and made a video that is easy to follow. 


4) If it is the primary GPU in the system you will need to prevent the Linux OS from using the virtual frame buffer to display the boot process. So under Main -> Flash you can add video=efifb:off to the Unraid boot option. More details can be found in this blog.607533261_ScreenShot2022-02-07at11_23_17am.png.ea99fdf09bf97f2f3f04a6ec72393721.png

 

If you need more help than this, you will need to provide us more information.

- The motherboard, CPU and video card(s) details.

- Also the relevant logs from the Unraid OS and VM.

 

Also be aware that weird things can happen when you upgrade Unraid (aka upgrade the host OS kernel). I ran for years without needing to do anything but then after one upgrade I suddenly needed to stub the card. Then another upgrade and I had to pass a VBIOS. Then last upgrade to 6.10.0-rc2 I needed to enable efifb:off.

Good Luck!

The only thing I havent tried is the Vbios. Does the config look ok though? these last lines appear wether i use vnc or video card

 

I'm using an rx 6600xt. Its a 9900 non k as well. 

 

2022-06-21 21:13:00.858+0000: starting up libvirt version: 8.2.0, qemu version: 6.2.0, kernel: 5.15.46-Unraid, hostname: StreamingMACPC
LC_ALL=C \
PATH=/bin:/sbin:/usr/bin:/usr/sbin \
HOME='/var/lib/libvirt/qemu/domain-1-Macinabox BigSur' \
XDG_DATA_HOME='/var/lib/libvirt/qemu/domain-1-Macinabox BigSur/.local/share' \
XDG_CACHE_HOME='/var/lib/libvirt/qemu/domain-1-Macinabox BigSur/.cache' \
XDG_CONFIG_HOME='/var/lib/libvirt/qemu/domain-1-Macinabox BigSur/.config' \
/usr/local/sbin/qemu \
-name 'guest=Macinabox BigSur,debug-threads=on' \
-S \
-object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-1-Macinabox BigSur/master-key.aes"}' \
-blockdev '{"driver":"file","filename":"/mnt/user/system/custom_ovmf/Macinabox_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/b73727e7-8fb6-49ef-91b9-a5ab62b8c222_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-4.2,usb=off,dump-guest-core=off,mem-merge=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format,memory-backend=pc.ram \
-accel kvm \
-cpu host,migratable=on,host-cache-info=on,l3-cache=off \
-m 24064 \
-object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":25232932864}' \
-overcommit mem-lock=off \
-smp 8,sockets=1,dies=1,cores=4,threads=2 \
-uuid b73727e7-8fb6-49ef-91b9-a5ab62b8c222 \
-display none \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=36,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 pcie-root-port,port=16,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \
-device pcie-root-port,port=17,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \
-device pcie-root-port,port=18,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \
-device pcie-root-port,port=19,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \
-device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \
-device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \
-blockdev '{"driver":"file","filename":"/mnt/user/domains/Macinabox BigSur/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 ide-hd,bus=ide.2,drive=libvirt-1-format,id=sata0-0-2,bootindex=1,write-cache=on \
-netdev tap,fd=37,id=hostnet0,vhost=on,vhostfd=39 \
-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:68:03:51,bus=pci.1,addr=0x0 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0,index=0 \
-chardev socket,id=charchannel0,fd=35,server=on,wait=off \
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
-device usb-tablet,id=input0,bus=usb.0,port=1 \
-audiodev '{"id":"audio1","driver":"none"}' \
-device vfio-pci,host=0000:03:00.0,id=hostdev0,bus=pci.3,addr=0x0 \
-device usb-host,hostdevice=/dev/bus/usb/001/004,id=hostdev1,bus=usb.0,port=2 \
-device usb-host,hostdevice=/dev/bus/usb/001/007,id=hostdev2,bus=usb.0,port=3 \
-device usb-host,hostdevice=/dev/bus/usb/001/009,id=hostdev3,bus=usb.0,port=4 \
-usb \
-device usb-kbd,bus=usb-bus.0 \
-device '************************' \
-smbios type=2 \
-cpu 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 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
char device redirected to /dev/pts/0 (label charserial0)
2022-06-21T21:13:01.008331Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-06-21T21:13:01.009064Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-06-21T21:13:01.009556Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-06-21T21:13:01.010095Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-06-21T21:13:01.010602Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-06-21T21:13:01.011134Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-06-21T21:13:01.011652Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-06-21T21:13:01.012206Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-06-21T21:13:02.697948Z qemu-system-x86_64: vfio: Cannot reset device 0000:03:00.0, depends on group 14 which is not owned.
2022-06-21T21:13:02.701920Z qemu-system-x86_64: vfio: Cannot reset device 0000:03:00.0, depends on group 14 which is not owned.
2022-06-21T21:13:59.852969Z qemu-system-x86_64: terminating on signal 15 from pid 3234 (/usr/sbin/libvirtd)
2022-06-21 21:14:02.655+0000: shutting down, reason=destroyed

Edited by Cor4eyh
Link to comment

I got a new computer with AMD 5600U, and my Mac VM wont' work anymore, I have tried to do a clean install, but I cannot even get into the format disk part, when I run it, it keeps rebooting.

 

When I checked the log, I got this:

 

-cpu 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 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
char device redirected to /dev/pts/14 (label charserial0)
2022-06-25T17:05:38.958203Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2022-06-25T17:05:38.958268Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-06-25T17:05:38.959351Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2022-06-25T17:05:38.959365Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
qxl_send_events: spice-server bug: guest stopped, ignoring
 

image.png.f23d8e5b22c637cfabf297254a0564b3.png

 

When I checked the Unraid syslog, I noticed this:

 

Jun 22 11:44:34 server mcelog: ERROR: AMD Processor family 25: mcelog does not support this processor. Please use the edac_mce_amd module instead.

 

Is that the reason? 

 

thanks

Link to comment

Hi all,

I've been trying multiple times to get this running, but the same thing keeps happening; the size of the drive that I need to install on it's always too small. Can anyone give me an idea as to why this keeps happening, despite following the guide?

1928342437_Screenshot_20220628-155922_SamsungInternet.thumb.jpg.94d430263f00fdb7a07bfe116a95924d.jpg

 

 

 

 

Link to comment
On 6/25/2022 at 6:20 PM, ruihere said:

+fma4

 

Why is that option included? According to Wikipedia the FMA4 instruction set is obsolete. It was introduced by AMD in its "Heavy Equipment" series (Bulldozer, Piledriver, etc.) but isn't officially supported by Ryzen. Intel has never supported it and therefore is isn't a requirement for macOS.

 

I also replied to your post in General Support.

Link to comment
On 6/9/2022 at 5:43 AM, lex87 said:

Hello Community, 

short question, i don't know if i have read the wrong comment but unfortunately each time when i start my MacOS, i requires manual partion selection for my Monterey so start. 
Is there any solution for an autoboot option, or is manual interaction required?

 

Cheer and thansk for help in advance

 

try this method

Open OpenCore Configurator, mount the EFI, open the config.plist, and to to "Misc" and disable Show Picker

Link to comment
On 6/26/2022 at 3:20 AM, ruihere said:

I got a new computer with AMD 5600U, and my Mac VM wont' work anymore, I have tried to do a clean install, but I cannot even get into the format disk part, when I run it, it keeps rebooting.

 

When I checked the log, I got this:

 

-cpu 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 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
char device redirected to /dev/pts/14 (label charserial0)
2022-06-25T17:05:38.958203Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2022-06-25T17:05:38.958268Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-06-25T17:05:38.959351Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2022-06-25T17:05:38.959365Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
qxl_send_events: spice-server bug: guest stopped, ignoring
 

image.png.f23d8e5b22c637cfabf297254a0564b3.png

 

When I checked the Unraid syslog, I noticed this:

 

Jun 22 11:44:34 server mcelog: ERROR: AMD Processor family 25: mcelog does not support this processor. Please use the edac_mce_amd module instead.

 

Is that the reason? 

 

thanks

Have you had any luck getting this to work?

 

I have a 5600G and can get BigSur to run but not Monterey and get stuck in boot loop and can’t even get to installer.

Link to comment

Hi all,

 

I have High Sierra working pretty well for me so I'm simply trying to run Monterey now to see how it goes. I have another instance of Macinabox running (had to manually change the appdata location and also the userscript syntax to reference the new directory for this to work correctly)

 

The installer runs pretty well until its around 24GB in size installed, and then I get below error. It seems like the bootbase.efi file is missing in the installer itself? Could it be an AMD issue as I'm using a 1st Gen Threadripper

image.thumb.png.cf46468e625e8c4e2c7d091a28c62796.png

 

This is the img installer size, seems kinda small at 3GB but I've tried redownloading a couple of times.

 

image.png.4f05ee76be8e1c7e8987c57eb7d7f3b5.png

Edited by ars92
Link to comment
On 7/2/2022 at 7:54 AM, ars92 said:

Hi all,

 

I have High Sierra working pretty well for me so I'm simply trying to run Monterey now to see how it goes. I have another instance of Macinabox running (had to manually change the appdata location and also the userscript syntax to reference the new directory for this to work correctly)

 

The installer runs pretty well until its around 24GB in size installed, and then I get below error. It seems like the bootbase.efi file is missing in the installer itself? Could it be an AMD issue as I'm using a 1st Gen Threadripper

image.thumb.png.cf46468e625e8c4e2c7d091a28c62796.png

 

This is the img installer size, seems kinda small at 3GB but I've tried redownloading a couple of times.

 

image.png.4f05ee76be8e1c7e8987c57eb7d7f3b5.png

I think it's an error with the install image created. Nothing I did would fix it. I spent two days trying. After a while I used the SAME VM but overwrote the Monterey_Install.img with one I created myself in MacOS and now it's installing fine. 

  • Upvote 1
Link to comment
On 7/6/2022 at 10:51 PM, ydur said:

I think it's an error with the install image created. Nothing I did would fix it. I spent two days trying. After a while I used the SAME VM but overwrote the Monterey_Install.img with one I created myself in MacOS and now it's installing fine. 

Ah knew it, thanks for confirming that! Will try getting an img through my other Mac OS VM and retry

Link to comment

Happy to report that my GTX 1070 TI is working pretty well on Big Sur using OCLP. Will soon try Monterey to see if the same can be achieved. Mainly used elitemacx86 instructions, but also had to edit certain PCI slot values in the XML generated by Unraid/Macinabox or else I was constantly stuck on the UEFI screen. Basically made it the same as what I have working in High Sierra and it came right up.


Love how my monitor USB hub works on my USB controller which is passed through to the VM, while the same doesn't work on High Sierra (it disables itself right after choosing my boot drive which signals something in OC not supporting it I guess, but not a big deal as I think I'm gonna get rid of High Sierra soon since Big Sur is working great!)

 

Im trying to get Bluetooth to work though, and I can see the hardware in Hackintool but not in System Report. Still trying to figure out how can I get this to work, but something tells me its not gonna work since I don't see Broadcomm under Vendor Name here.... any thoughts?

 

image.thumb.png.f5303019556f53dd17c0e8b985189474.png

 

 

image.png.4ba3868d9bdc36ea0af69da526a98300.png

 

Link to comment
On 7/6/2022 at 3:51 PM, ydur said:

I think it's an error with the install image created. Nothing I did would fix it. I spent two days trying. After a while I used the SAME VM but overwrote the Monterey_Install.img with one I created myself in MacOS and now it's installing fine. 

Hi! I'm also having the same problem. Can you explain how you created a new install image?

Thank you

Link to comment
On 7/6/2022 at 4:51 PM, ydur said:

I think it's an error with the install image created. Nothing I did would fix it. I spent two days trying. After a while I used the SAME VM but overwrote the Monterey_Install.img with one I created myself in MacOS and now it's installing fine. 

Hi ydur,

I can get the big 12G  install macOS Monterey.app file (in the applicatios*ns folder of an outdated macmini).

I had a look inside the .app but wasn't able to find any .img file.

Is there a way to convert it ?
Thanks for your support !

Link to comment
On 2/13/2022 at 2:05 PM, ghost82 said:

This is a copy/paste of a private message I sent about how to correctly have an offline installation media:

--

if you have access to mac os, the vm with vnc is ok, you can install the MDS application:

https://twocanoes.com/products/mac/mac-deploy-stick/

 

free download is ok.

This is recommended, since files will be downloaded directly from apple.

mds.thumb.png.8d55d96f21bd1d1ba03997adc974294b.png.1fe38ebb091b4bbd56f72a13a75a2d45.png

 

1. Run it

2. Select Download macOS

3. choose CustomerSeed as catalog

4. Select the os/version you want to download

5. click download and choose the target folder to save the image

Note: no progress bar for download, just let the software there until a popup appears for the successful download (you need to download about 12 Gb)

 

This will download a dmg file.

Once you downloaded that image:

 

1. Run disk utility

2. Select File --> New image --> empty image

3. Give it a name in save as and name fields (let's call it "Monterey" in this example); Dimension: 16 GB; Format: Mac os extended (journaled); cryptography: none; Partitions: single, GUID; Image format: disc image read/write

4. save the empty image somewhere and it will be mounted automatically

5. mount the dmg image you downloaded with MDS and open the mounted image

6. right click on install mac os xxx, then show package content; navigate in Contents/Resources/

7. run a terminal window

8. type "sudo " (sudo+space without quotes) and drag the file createinstallmedia in Contents/Resources/, type a space then add "--volume /Volumes/Monterey" (without quotes), something like:

sudo /path/to/Install\ macOS\ Monterey.app/Contents/Resources/createinstallmedia --volume /Volumes/Monterey

/Volumes/Monterey is the mounted empty image you created with disk utility.

 

9. press Enter, type your password and press again enter; files will be copied to the empty 16Gb image

10. Once finished, unmount both images

11. Rename Monterey.dmg to Monterey.img

12. Use Monterey.img as a sata installation disk in your xml (type='raw')

 

57 minutes ago, urbatecte said:

Hi ydur,

I can get the big 12G  install macOS Monterey.app file (in the applicatios*ns folder of an outdated macmini).

I had a look inside the .app but wasn't able to find any .img file.

Is there a way to convert it ?
Thanks for your support !

Just reply to myself after "just" reading thread to find already posted answer !

  • Upvote 1
Link to comment

Is it possible to passtrough the intel hd 630 to monterey? High sierra runs like a charm with my gtx 1060, but i cant passtrough my igpu to monterey, the vm starts normally but i have a black screen.

 

Hardware: 

i7-7700k

msi h110m pro-d

GTX-1060

 

Edit:

i also have a userscript to run unriad headless

Edited by The_Pilger
Link to comment
2 hours ago, The_Pilger said:

Is it possible to passtrough the intel hd 630 to monterey? High sierra runs like a charm with my gtx 1060, but i cant passtrough my igpu to monterey, the vm starts normally but i have a black screen.

 

Hardware: 

i7-7700k

msi h110m pro-d

GTX-1060

 

Edit:

i also have a userscript to run unriad headless

It should work great according to this site - Intel GPUs | GPU Buyers Guide (dortania.github.io)

 

Your issue sees to be something outside of the MAC OS/bootloader though. Try to make it work with Windows first and then see if you need to change anything to make it work.

 

Link to comment

Are there any issues for older MacOS versions? I'm trying to follow the YouTube video (though it seems outdated, in regards to the settings shown), but get "stuck" on the notify script. It just hangs forever. I'm trying to install Mojave within Unraid 6.10.3, and it creates a "Macinabox Mojave" folder in the VM share, with OpenCore and a vDisk, and also downloads a (roughly) 2GB "Mojave-install.img" file to the ISO location, and that's about it, the script just sits there running in User Scripts

Link to comment

Hi everyone,

 

I'm having issues when i try to actually run my VM for the first time.

 

I'm seeing 

 

Execution error

operation failed: unable to find any master var store for loader: /mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd

 

when i start the VM.... I can also see the following in my VM log:

2022-07-24 20:53:16.702+0000: 27033: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/isos/BigSur-install.img: No such file or directory
2022-07-24 20:53:16.702+0000: 27033: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/isos/BigSur-install.img': No such file or directory
2022-07-24 20:53:16.705+0000: 27036: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/isos/BigSur-install.img: No such file or directory
2022-07-24 20:53:16.705+0000: 27036: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/isos/BigSur-install.img': No such file or directory
2022-07-24 20:53:16.708+0000: 27036: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/isos/BigSur-install.img: No such file or directory
2022-07-24 20:53:16.709+0000: 27036: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/isos/BigSur-install.img': No such file or directory
2022-07-24 20:53:18.152+0000: 27034: error : qemuPrepareNVRAM:4388 : operation failed: unable to find any master var store for loader: /mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd

 

And my XML:

 

?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>5ba73e47-7970-4984-80b4-cccc0aedfbc6</uuid>
  <description>MacOS Big Sur</description>
  <metadata>
    <vmtemplate xmlns="unraid" name="BigSur" icon="BigSur.png" os="osx"/>
  </metadata>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>2</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='1'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-4.2'>hvm</type>
    <loader readonly='yes' type='pflash'>/mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd</loader>
    <nvram>/mnt/user/system/custom_ovmf/Macinabox_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none' migratable='on'>
    <topology sockets='1' dies='1' cores='2' threads='1'/>
  </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/Macinabox BigSur/BigSur-opencore.img'/>
      <target dev='hdc' bus='sata'/>
      <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/BigSur-install.img'/>
      <target dev='hdd' bus='sata'/>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='writeback'/>
      <source file='/mnt/user/domains/Macinabox BigSur/macos_disk.img'/>
      <target dev='hde' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </disk>
    <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>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <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='0x10'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x11'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0x12'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 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>
    <interface type='bridge'>
      <mac address='52:54:00:c2:f1:03'/>
      <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'/>
    <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>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <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='isa-applesmc,osk="REMOVED">
    <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>

 

 

When i read this, first thing that comes to mind is that my file directory is different than what the template shows.. Weird thing is, it's not. My structure is default... I have my domain, ISO, and system shares in /mnt/user/System, /mnt/user/domains, and /mnt/user/ISOs....

 

I've tried removing the container while wiping my app data folder, domains, ISOs, system, and the scripts. I've also tried removing the custom_ovmf dir that someone else had luck doing but that also did not work.

 

Not sure how to proceed from here.....

 

image.png.111dfcaea1a917650392c62b541aa7d0.png

 

 

image.thumb.png.97ee6629e4eda6c66d4827c4a59402c9.png

image.thumb.png.71f35a9944b1c56b2633606f52cb1312.png

 

image.thumb.png.a8eae870c92f97f0215cf4e5decf7f52.png

image.png

Link to comment

I have tried multiple installs of Big Sur but I cannot get Message to work properly.

 

I install with all the defaults. I do the OpenCore steps according to the latest SpaceInvader (love this) video. I have created a new AppleID account. I first log in without AppleID and then connect to appleID.

 

When I open Message and log in, it is successful and then closes 5-10 seconds later. I have looked at the confusing steps that others have put up to "fix" the issue, but they don't seem to apply to me.

 

If I log in with my own apple id in the VM (using vnc viewer), Messages works fine and doesn't shut down. 

 

If I use new appleid and then use messages on my macbook, the appleid works fine.

 

So I think macinabox Messages is fine (works with my appleid) AND new appleID works fine (works on my macbook)

 

BUT I cannot get new appleid to work in macinabox and I don't know where to look or what steps to take next. Any help would be welcomed. 

Link to comment

Join the conversation

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

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

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

×   Your previous content has been restored.   Clear editor

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