lysdexik

Did this ever get resolved? I’m facing a similar issue where nginx is listening on port 80 and I have IPV6 disabled and the unraid gui is not configured to run on port 80.

So it looks like the issue that I am having is that the autoinstall directory is never getting created even after waiting for hours and hours. I manually created the autoinstall directory and copied the installer img and pasted a copy of the XML file from github and then I was able to run the helper script. Edit 1: I am still confused as to what is going on here, I was able to get the VM built but I can't boot it because this file doesn't exist: /mnt/user/system/custom_ovmf/Macinabox_VARS-pure-efi.fd what gives? Edit 2: Man this container is a mess, the big sur install image actually points to Monterrey LOL

I looked through this thread and found 2 others that posted a similar error to mine but the fixes don't seem applicable. This is my first time installing the OS and I don't have an existing VM created in the VM tab (I thought that the script did that?) In accordance with the video instructions I left the vm_ready script running in the background for several hours and I never got the completion notification. The script just stays in a running state and never finishes. I suspect this is problem number one but not sure what to do about it. Can anyone explain to me what I am doing wrong? I'm following the video verbatim and trying to run the helper script for the first time and it is failing with the below error: Script location: /tmp/user.scripts/tmpScripts/1_macinabox_helper/script Note that closing this window will abort the execution of this script Starting to Fix XML error: failed to get domain 'MAC' No network adapters in xml to change. Network adapter is already vmxnet3 Added custom qemu:args for macOS topolgy line left as is custom ovmf added error: Failed to define domain from /tmp/macinaboxfixed.xml error: (domain_definition):3: Extra content at the end of the document ^ This is what has been done to the xml Your network type was already correct. Network has not been changed. The custom qemu:args have been added to you xml. VM is set to use custom ovmf files. xml is now fixed. Now goto your vm tab and run the VM Rerun this script if you make any other changes to the macOS VM using the Unraid VM manger

Hey ich777 -- Interesting. We changed that path to the disk and it seems to be working now . Wonder why we get the error even though the two paths are essentially equivalent. Thank you for this.

In your Kernel parameters section, I noticed you don't prepend with kernel /bzimage or postpend with initrd=/bzroot. Do we not need these lines? Does setting it up this way avoid the system getting stuck on the Unraid GRUB screen on boot?