John_M

Not high utilisation, but if the image is in use its size can't be changed. Perhaps it couldn't be unmounted because there was an open file on it. Rebooting would have fixed that problem.

It doesn't. If you select Catalina, it downloads Catalina - I did it last week, and discussed it in this thread. However, if you select Big Sur, it downloads Catalina instead. This is a known problem and has been discussed repeatedly in this thread. The author hasn't updated the container to fix it. Also discussed is the fact that it's possible to install Catalina and then upgrade to Big Sur, if you really want to. I wouldn't expect you to read all 71 pages but it might be worth skimming through the last four or five.

The first thing to consider is whether the NIC is supported by macOS, either natively or by means of a driver supplied by the manufacturer.

You didn't follow the instructions to edit the script before running it for the second time. Timecode 14:00 in the video guide. (See the previous page of this thread)

Even when all the necessary components have been downloaded the VM doesn't appear until after you have run the helper script for the first time. The vmready_notify script isn't necessary. All it does is tell you that the downloads are complete and it's time to run the helper script with default settings.

FWIW if I ping 17.164.1.12 I get request timeout too. Also FWIW, Big Sur isn't all that great at the moment, even with the update to 11.2. It's needed on Apple Silicon, of course, but Catalina is fine on AMD64.

Correct. 9th December. "How to Install Big Sur and Other macOS Versions with New Macinabox"

That's ok. The timecode of the first run of the helper is 8:10 and of the edit and second run 14:00.

It's there. I suggest you watch it again and using play and pause do the operations in real time. There are a lot of them and the order is important. I certainly can't remember them all!

A couple of things. Testing a Windows VM doesn't mean that the Apple server nearest to you is accessible, just as some people lose access to GitHub occasionally and complain that updates aren't available, but others don't. You have to run the helper script unedited before you run the VM for the first time to do the installation. Then, after the installation, you need to edit the user script and run it again. Are you doing that?

Could there be a local connectivity issue that's unrelated to Unraid?

One of the things the helper script does is change the network type from vmxnet3 to e1000-82545em, when it's run after the initall installation. I wonder if @avinyc forgot to set it up and run it?

I have never experienced that error. Have you tried Method 2?

Have you considered installing Catalina instead, making a backup and upgrading? There are people now reporting success if you follow the method outlined on the previous page. The key to success seems to be to perform the upgrade before trying to migrate OpenCore EFI partition to the macOS boot drive.

It has. 11.2 is officially available and is currently installing on my MacBook Pro.

I wasn't asking on my behalf, but because so many people posting here seem frustrated and because you've had some success. I'm happy with my set-up. Thanks anyway. Perhaps this is the clue that will help those who are struggling.

Other people have reported that simply running the software update doesn't work and that is trashes their Catalina installation, making it not bootable. Perhaps this is what people need to do to make the update work. Maybe some guidance here would help.

For the benefit of others wishing to upgrade, would you mind providing details of how you did it?

Has anyone had any success doing that? Several people have reported failure - I'm not aware of anyone reporting success in this thread. Even people attempting it on actual Apple hardware have reported problems.

I don't expect different browsers to behave identically, so I was surprised to find that Firefox, Chrome, Brave and Safari (the four browsers I have installed) actually do behave identically in this respect. I think the slight delay before the tool-tip appears is to avoid the mess of flashing pop-ups that would otherwise appear while moving the mouse pointer around. I find it very easy: just hover the pointer over the gears icon for a second and the state of the switches is revealed. I can't speak for other operating systems (I'd be surprised if Windows was very different in this respect) or tablets/phones, which have a different user interface due to the lack of an on-screen pointer. Tool-tips work for me on this site, too. Here's an example to compare with yours:

It looks a lot neater, making much better use of the limited space, and your efforts are much appreciated. The change took a little while to get used to but it's very worthwhile, in my opinion. I can't believe that anyone needs to change the switches often so it makes sense to move them to a secondary page. The tool-tips all work fine with my browser/OS combination (macOS/Firefox). Move the mouse pointer over an icon and it changes to a hand with a pointing finger. After one second the tool-tip appears and stays there until I move the pointer away from the icon. This avoids the need to click the icon just to check the position of the switches.

Well, that worked fine. It's all installed and it found a security update and a new version of Safari, which also installed without a problem. There's also an update to Big Sur offered but I'm ignoring that - other people have tried it and report that it trashes the existing Catalina VM. I don't have a suitable GPU in this server to try to pass through but I have an RX 580 in another server that works. There are a lot of steps to complete after the installation, including setting up OpenCore to make the vdisk bootable, choosing a machine type and checking that the serial number is NOT valid, then shutting down, editing the template to add RAM and CPU cores to the VM and remove no longer required vdisks, editing the helper user script and finally running it. They have to be performed precisely and in the right order, so no wonder some people are having problems. However, it's all dealt with in the YouTube video and I found it very useful to have the video open on one monitor, playing and pausing it, while working on another.

I've only just started, on a test server that has never had any version of MacInABox installed before and it's looking promising so far. I just accepted all the defaults and made sure Catalina was the macOS version chosen (it is the default). The VM icon is the default one because I don't use Ed's method. I'll add my own later.

https://www.insanelymac.com/forum/topic/346245-gt-710-kepler-not-working-oob-with-big-sur-but-did-with-catalina/

I used an early version of the container to make a Big Sur VM, though it wasn't as straight-forward as the instructions suggest and I had to re-try several times. It has since been updated two or three times and it seems not to work properly in its current state. Certainly, getting it to download the Big Sur recovery media seems problematic and the user scripts seem to take longer than expected to show up. Maybe I'll try to set up a Catalina VM from scratch on a test server and see how it goes. If I have any success, I'll report back. One thing that seems certain to cause failure is if you change certain paths from their defaults as they appear to be hard-coded into the script that patches the XML. I see a lot of frustration in the comments on the last two or three pages here. I'm just another user, though. Perhaps a comment from the author would help.