25 minutes ago, iamtim2 said:

Conclusion, unraid running on my server does not do VM's very well!

Do not take it bad, but it must be something else..both unraid and proxmox use qemu to do virtualization and the host os cannot make such a difference.

On 2/13/2024 at 1:21 PM, DWomack said:

Looking for an annotated user script that will remove all of what Macinabox has touched, so a new macinabox can be created.

 

A script would be much better than touch this, and this, delete this, etc.

 

Maybe the script could remove all VMs and the dockers necessary.

 

Sure I can stumble through all the steps, but a script that always works without mistakes would be much better.

 

Thanks to iamtim2 for posting his guide above.

This seems to work, you guys have comments?

 

I made this an UnRaid User Script:

 

#!/bin/bash
#description=This script completely removes all references to the BigSur_VM
#foregroundOnly=true
#arrayStarted=true
#name=remove_macinabox_BigSur_VM

# Replace "name_of_VM" with the actual name of your VM

echo VM_NAME="Macinabox BigSur"
VM_NAME="Macinabox BigSur"
echo

sleep 2

# Undefine the VM (remove it from libvirt)

echo virsh undefine --nvram "$VM_NAME"
virsh undefine --nvram "$VM_NAME"
echo

sleep 2

# Delete the VM's XML configuration file
# Navigate to the directory where VM XML files are stored
# Usually located at /etc/libvirt/qemu/
# Delete the XML file corresponding to your VM
# For example:

echo ls -la /etc/libvirt/qemu/
ls -la /etc/libvirt/qemu/
echo

# echo rm /etc/libvirt/qemu/"$VM_NAME".xml
# rm /etc/libvirt/qemu/"$VM_NAME".xml
# echo

sleep 2

# Restart the libvirt service
# This step ensures that the changes take effect
# You can restart the entire server or just the libvirt service
#
# For example:
# systemctl restart libvirtd
#
# Or since this is Slackware:
# /etc/rc.d/rc.libvirt restart

echo /etc/rc.d/rc.libvirt restart
/etc/rc.d/rc.libvirt restart
echo

sleep 2

# Optionally, you can also delete the VM's disk image
# Locate the VM disk image and delete it
# For example:
# rm /mnt/user/domains/"$VM_NAME"/disk.img

echo rm -r /mnt/user/domains/"$VM_NAME"
rm -r /mnt/user/domains/"$VM_NAME"
echo

sleep 2

echo rm -r /mnt/user/isos/BigSur-install.img
rm -r /mnt/user/isos/BigSur-install.img
echo

sleep 2

echo rm /mnt/user/system/custom_ovmf/*
rm /mnt/user/system/custom_ovmf/*
echo

sleep 2

# Notify any relevant services or users about the VM removal
# You can customize this part based on your setup
# For example, send a notification using Unraid's built-in notification system:
# /usr/local/emhttp/webGui/scripts/notify -i normal -s "VM $VM_NAME removed"

# Clean up any other associated files or directories as needed

echo rm -r /boot/config/plugins/user.scripts/scripts/1_macinabox_vmready_notify
rm -r /boot/config/plugins/user.scripts/scripts/1_macinabox_vmready_notify
echo

sleep 2

echo rm -r /boot/config/plugins/user.scripts/scripts/1_macinabox_helper
rm -r /boot/config/plugins/user.scripts/scripts/1_macinabox_helper
echo

sleep 2

# Done! The VM traces should now be completely removed.

# Remember to make this script executable:
# chmod +x /path/to/your/script.sh

echo Script complete!

 

Is there a way to script stopping and deleting…

the macinabox docker

the vm

the macinabox docker template

 

If I want to start a fresh, I want to just run a script.  

Edited February 26, 20242 yr by DWomack
Added info

On 12/10/2023 at 6:34 PM, mackid1993 said:

Question, once I have a working BigSur VM, what happens if I upgrade to a newer version of macOS from within the VM? Will everything break?

Did you get it it working successfully? I'm trying to do the same @mackid1993

I was able to successfully install BigSur!
Now - Does this work? 

Any suggestions on not having any sound? Big Sur - VM Parameters do not have anything to select from the 'Sound' Option.
The sound works through VNC on my Win7 VM - so it's possible..

10 hours ago, Kev600 said:

I was able to successfully install BigSur!
Now - Does this work? 

The current Macinabox has a very old version of Opencore (0.7.8) so you'll have to upgrade opencore to a much newer version (latest is 0.9.8) and update drivers and kexts. Just trying to apply the update to the newly created Big Sur install will fail.

 

I wrote a basic guide here: https://forums.unraid.net/topic/84601-support-spaceinvaderone-macinabox/?do=findComment&comment=1364505 (previous page) on how I got Ventura working and I also got Sonoma working but Sonoma is much pickier about hardware as Apple has dropped support for quite a lot of legacy hardware in the continuing push with Apple Silicon, especially Broadcom WiFi adapters. There are some workarounds in Sonoma using Opencore Legacy Patcher but these didn't work for me.

 

Mileage will vary depending on hardware, intel or AMD CPU etc, but if BigSur works well for you and any passed through hardware, Ventura will work but Sonoma will probably require quite a lot of fiddling.

@iamtim2 :

Thank you for this contribution 

Do you have any solution to install macOS without (live) download ? With a macOS IMG like a USB install key ?
...Specialy for poor internet connections.

5 hours ago, PicPoc said:

@iamtim2 :

Thank you for this contribution 

Do you have any solution to install macOS without (live) download ? With a macOS IMG like a USB install key ?
...Specialy for poor internet connections.

I don't but there are guides to create a MacOS USB installer. You could create the installer then pass the USB through to the VM. You still need to download the .img in the first place

20 minutes ago, iamtim2 said:

I don't but there are guides to create a MacOS USB installer. You could create the installer then pass the USB through to the VM. You still need to download the .img in the first place

Yep', I know how to create it, but I can't detect "macOS USB installer" to install...

 

Thanks @iamtim2 

 

Any idea on the missing sound?

8 hours ago, Kev600 said:

Thanks @iamtim2 

 

Any idea on the missing sound?

Are you passing through a GPU? If you are, you have to make some edits to the xml to ensure both the graphics and sound portion of the GPU are on the same virtual PCIe slot. Spaceinvaderone has a good tutorial on this in his advanced GPU passthrough video.

 

https://youtu.be/QlTVANDndpM?si=q0MefOd-abbb4wk6

 

I don't know about sound if not passing through hardware but I expect the VM is too laggy to use without it anyway.

Thanks again..
No passthrough @iamtim2

It works fine on my Win7 VM.

 

 

On 1/20/2021 at 10:17 AM, WPCom said:

Would anyone know why I can not pass my internet connection through to the mac VMs? I have tried all the diffrent OS installs, and I can not get past the reinstall macOS because it does not propperly pass through nic.

 

Thoughts? or am I missing somthing obvious?

Is there anything new about this yet? I'm trying to install Big Sur and I get the message "An Internet connection is required to install macOS"

I've already tried different variants under the VM's network interface.

Thank you in advance for your help!

Hello everyone , i'm a new user of unraidOS , my graphic card is an RTX 4070 wich isn't compatible with mac os so i use VNC

How am i suposed to get my VM screen on the host screen ?
I mean i can acces to the VM using web interfaces but i would like to get the VM on my graphic card output 

Hello everyone,

I managed to install Big Sur and logged into the cloud and app store also worked.

I also updated Opencore to the latest 0.9.8 and also updated the KEXTE accordingly.

I then installed Ventura, which also worked without any problems!

Now I would like to pass on my GPU as it is useless without video acceleration.

I bought a Radeon Pro WX 4100 a long time ago specifically for this purpose.
 
But I want to run the VM headless most of the time, i.e. remotely, for example. via VNC, Parsec etc.

How do the settings have to be made?

If I simply add the WX 4100 as a second card with a sound card and run the helper script and then start the VM, I only get to the Apple logo and the loading bar only goes up to about 2/5 after that nothing happens.

Can any of you who also use VNC and GPU provide your XML as an example?

 

Thank you!

When try to install Macinabox, I got below error message, can anyone help me. I don't have any problem in installing other dockers or plugin in App Market, I am running 6.12.8

 

///docker run
  -d
  --name='macinabox'
  --net='bridge'
  --privileged=true
  -e TZ="Asia/Shanghai"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="macinabox"
  -e 'flavour'='Big Sur'
  -e 'vminstall'='Auto install'
  -e 'vdisksize'='100G'
  -e 'vdisktype'='raw'
  -e 'opencore'='stock'
  -e 'replaceopencore'='no'
  -e 'overridenic'='no'
  -e 'VMIMAGES'='/mnt/user/domains/'
  -e 'ISOIMAGES'='/mnt/user/isos/'
  -e 'injectfixxml'='yes'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/SpaceinvaderOne/Docker-Templates-Unraid/master/spaceinvaderone/docker_icons/Macinabox.png'
  -v '/mnt/user/domains/':'/domains':'rw'
  -v '/mnt/user/isos/':'/isos':'rw'
  -v '/mnt/user/appdata/macinabox':'/config':'rw'
  -v '/mnt/user/system/custom_ovmf/':'/customovmf/':'rw'
  -v '/boot/config/plugins/user.scripts/scripts':'/userscripts':'rw' 'spaceinvaderone/macinabox'

Unable to find image 'spaceinvaderone/macinabox:latest' locally
docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp [2600:1f18:2148:bc02:445d:9ace:d20b:c303]:443: connect: network is unreachable.
See 'docker run --help'.

The command failed.///

Evening all, thanks @SpaceInvaderOne for this vm.

Install went great and running fine, however i cannot get internet working at all, i am not new to bare metal hackintosh but this has me stumped.

I also passed through my intel wifi, and inserted Airportitlm kext and snapshot the config plist (unfortunately with OCC, as propertree will not run on this version of BigSur) and its not showing or enabled.

Any help with this please.

 

Sorted: Macinabox defaults helper script do not work for me but editing the xml with the following has:

 

<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>

Edited March 19, 20242 yr by OldManBeard
Problem Solved

Anyone having what I assume is kernel panic issues? 
 

I have other Linux VM’s running without issue but after starting the big sur installer and it's been running for a while the sever crashes as requires a manual reboot. System remains stable until I start this install again 

Macinabox VMs do not show on console.

Installed Macinabox, followed Squid's and chozeur's tutorials, ran into install issues (it just froze at 12 minute mark on install) and had to restart from the beginning .

 

I removed Macinabox Monterey VM through the VM edit tab and then also manually in domains folder.  Then removed Macinabox docker and also removed it from unRAID appdata folders.  I also removed Macinabox docker template by using the "add container" button.

Every time I go to re-install Macinabox, Macinabox shows as a docker, but none of the Monterey or Big Sur VMs show or their files, as did with first install.

What have I messed up?!?!

Edited March 22, 20242 yr by RadRom

4 hours ago, RadRom said:

Macinabox VMs do not show on console.

Installed Macinabox, followed Squid's and chozeur's tutorials, ran into install issues (it just froze at 12 minute mark on install) and had to restart from the beginning .

 

I removed Macinabox Monterey VM through the VM edit tab and then also manually in domains folder.  Then removed Macinabox docker and also removed it from unRAID appdata folders.  I also removed Macinabox docker template by using the "add container" button.

Every time I go to re-install Macinabox, Macinabox shows as a docker, but none of the Monterey or Big Sur VMs show or their files, as did with first install.

What have I messed up?!?!

Did you run the vm setup script from the user scripts section? If so what was the output 

13 hours ago, gareth_iowc said:

Did you run the vm setup script from the user scripts section? If so what was the output 

Hi 🙂

Yes I did and changed VMs name as per SapceInvaderOne's YT instructions.

I ended up re-installing unRAID and did a fresh install of everything with a newer flash drive back-up.  Macinabox seems to be working fine now.  Just ain't installed any macOS yet.

 

Thankyou!!

Been having loads of problems trying to set up Big Sur.

 

Here's my working, hope it helps someone else.

 

1. Downloaded Macinabox

2. Changed only the size to 50GB and image from raw to qcow2 (to fix another error)

3. Ran Macinabox, all good.

4. Ran script #2, and get the popup it's ready.

5. Ran script #1 and noticed this error:

 

error: Failed to define domain from /mnt/user/appdata/macinabox/autoinstall/Macinabox BigSur.xml

 

6. Opened the script and replaced the name in the XML script to the VM name: "Macinabox BigSur" (without quotes).

7. Ran #1 again, looks good. Script says it's ready to go and there's nothing to do.

8. Ran the VM, all good (no complaint about qcow2 issue because I changed from raw in the Macinabox container settings)

9. VM starts up real quick no problem.

10. Disk utils and erase my 50G drive.

11. Back out and open the installer and select 50G drive.

12. Wait about 8 minutes for install (I have a very fast homelab).

13. Get back to the same screen in the beginning "Macos Base Disk", "Big Sur Installer", Recovery, Script one, Script two etc.

14. Try to run the first Disk option. Boots me into the Recovery program as there's something wrong with the disk.

15. Back out again, select option #2 (Installer)

16. Install bar again, takes another 15 minutes or so.

17. Boots me back to the same screen again.

18. Select install again, takes a bit more (3-4 minutes) time.

19. Boots me back out to the same main screen.

20. Now I see "bigsur" disk (which I named from the Disk Util erase step)

21. Boot into that. Finally it loads!

 

So you can skip step 14.

 

I also had to fix some weird error when starting the VM.

Quote

Cannot get interface MTU on 'br0': No such device

error. Which I did by stopping my array and just going into Settings > Network > changed MTU to 9000 > Started the Array > All good.

Was a bit confusing because I am actually using bond0 not br0.

Then I updated the VM by adding more CPU cores to make it faster, ran the helper script again and sadly nope...

 

It just sits at the Apple logo forever now and the loading bar never comes up.

 

So I guess I have to start all over again with the CPU cores in the beginning now. I probably should have just left it..

 

 

EDIT: I simply changed back to the first 2 CPU cores like in the beginning and ran the helper script again.

It immediately started working again, no need to reinstall anything. So I'll just stick with those 2.

 

I saw another video that showed I had to copy and paste the original .XML script again and then change the cores but I cbf'ed doing that.

 

I am using a Ryzen CPU btw, so this works fine for AMD. Take that Apple!

Edited May 3, 20242 yr by plantsandbinary

Yeah so both my Apple accounts have gotten locked just trying to sign into this VM now.

 

Apple definitely can detect these aren't "real" Mac machines. So if you don't need to use AppleID with them or login to Apple, then go ahead. Otherwise STEER CLEAR.

 

If you do need to log in to AppleID you'll get your account flagged, locked and shadowbanned in every way possible.

 

Here's my experience:

 

1. Try login on the device

2. Account immediately locked

3. Start unlock process (give catpcha, phone number, bank card and finally suggest new phone number)

4. "Verification codes can't be sent to this phone number at this time" (even if I try call me)

5. Try another machine (Windows)

6. Same process, exact same problem (because the account is now shadowbanned)

7. Try again with several different numbers, exact same error message

8. Try now on the Mac with another account

9. Other account is immediately locked lmao

10. You must use another Apple device to unlock either device (I don't have one)

11. Try unlocking without another Mac (same phone verification code problem)

12. Try to make a new Apple account on the VM

13. "This Mac has been used to create too many Apple accounts" (lol what?)

14. Call Apple support because it's now been a waste of a few hours

15. "Yeah we can't help, you need to use a fresh Mac or iphone to either unlock your account or register a new account"

16. Complain that this situation is bullsh*t "Yeah sorry, we can see you're trying to login but we can do nothing, that's just our policy"

17. Try telling them I am just an engineer with a new Mac trying to work "Sorry, your company should have some kind of IT support team that can help you" LMAO

18. Tried a few more times on different network (5G) and I have never used a VPN or anything sketchy just this Macinabox VM.

 

They got me by the balls.

 

Guy said he could see me logging in and it failing, but he didn't say more than this. So they know I am trying to log into a virtualized Mac, they refuse to unlock either account. The guy's got a stonewall pokerface on the phone and he knows I am trying to log in with 2 real accounts on a virtualized Mac and they've banned both of them rightly. So he's not going to budge even if he could do anything.

 

Now I have two effed Apple accounts and he tells me my only hope is to either take my device in to an Apple Care store (lol it's a VM, nice bluff call) or buy an Apple device, which is entirely what I am trying to avoid. I gotta hand it to Apple, they're Grade-A scumbags. If they can't stop people making illegal VMs of their OS, they can definitely ban anyone who tries to log in to one and try to force them to get one of their garbo devices.

 

All I wanted was to use BlueBubbles so I can talk to the stubborn/stupid family members of mine who have an iPhone. Maybe it's time to try the old Hackintosh method.

 

If you've managed to log in to AppleID on this VM I would be shocked. You probably just won some kind of lottery.

Edited May 4, 20242 yr by plantsandbinary

44 minutes ago, plantsandbinary said:

but he didn't say more than this

First of all, logging into an apple account from a mac os virtual machine is not illegal and is not against apple terms and conditions; what you can't do is virtualizing a mac in a host which is not a mac. Note that qemu is available also for mac os hosts.

I'm using my apple account in a qemu vm (other than my real macbook pro) from more than 6 years now and, apart being banned/flagged at the beginning (which required calling an operator), because basically I didn't know what I were doing, I never had a single issue after that.

If you want to log with an apple account, first you need to setup your hardware such that the en0 is seen as built in, you should use a mac address belonging to apple hardware, choose proper smbios data, serial number. Do not change serial number or other smbios data once you are logged in, because apple will see logins, coming from different devices, and for "security reasons" it will flag your account. If you want to experiment with a mac os vm do it offline, Once you know what you're doing freeze the configuration and go online.

Once you know what you're doing, call apple and give them the code (if you have one) to unlock the account; it could be that the operator has no idea of what you're saying and doesn't even know what is the code you have to unlock the account; if this is the case call again to speak to another operator untill you find one that knows what you're talking about..I had to call 3 times to find a smart operator that unlocked my account in less than 10 seconds..

Do not tell them you are virualizing a mac on a non apple hardware, you can say you are virtualizing it on a mac host, so..??They have to unlock your account.

Edited May 4, 20242 yr by ghost82