[Nginx still listening on port 80 even though I changed web UI port]

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.

[[Support] SpaceinvaderOne - Macinabox]

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

[[Support] SpaceinvaderOne - Macinabox]

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
 

[[Support] ich777 - Gameserver Dockers]

17 minutes ago, ich777 said:

Please try to physically point to the path on the disk not the user path: /mnt/cache/docker/chyvalrymw

(if your share 'docker' is located on the cache drive, please also make sure to set it to 'prefer' or 'only' at the use cache setting in the share section)

 

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.

[Intel IGD (integrated graphics) Pass Through Support - March 2016 Update]

On 5/13/2020 at 11:00 AM, T0a said:

I was wrapping my head around this solution for a few days now.

 

In order to use legacy passthrough "The IGD device must have a VGA ROM, either provided via the romfile option or loaded automatically through vfio (standard)." [0].

 

From my understanding the iGPU does not expose a ROM via PCI when the host is booted in UEFI mode [1]. Thus, you probably where able to access the VM via remote access with full GPU support, but got no signal from the port. The symptom in most cases is the following error "vfio-pci: Cannot read device rom at 0000:00:02.0 Device option ROM contents are probably invalid" in the VM log. Further telling that the legacy pass through mode [2] [3] is disabled. To solve the issue you need to manually provide a ROM as vfio is not able to provide it.

 

In your case, your MB is capable to boot in legacy mode that allows to expose the ROM via PCI. Sadly, I cannot go this route for my UHD 630 as my MB does not support legacy mode (probably the standard in the future). In this case I think, you need either a second GPU (don't own one) to dump the IGD ROM or ask someone with the same CPU to dump the ROM for you in legacy mode (a collection of IGD ROMs would be really nice):

 

Update 14-05-2020:

 

Finally, found a working solution for UEFI only MB owners out there that works with legacy GVT-G passthrough and OMVF Bios [6,7]. Following, the setup that resolved the black screen issue with an Intel Core i3-8100 (UHD 630). The trick for me made the "vbios_gvt_uefi.rom" (see [7]; disclaimer: be warned to use a random ROM file from the Internet):

 

Unraid Settings:

- Host boots in UEFI (no legacy mode no CSM)

- "Unraid OS" boot mode

- Permit UEFI boot: Yes

- Kernel parameter: append video=efifb:off,vesafb:off modprobe.blacklist=i2c_i801,i2c_smbus,snd_hda_intel,snd_hda_codec_hdmi,i915,drm,drm_kms_helper,i2c_algo_bit

- VFIO-PCI Config to stub 00:02.0

VM Settings:

- Windows 10 OS, OMVF Bios, i44fx-4.2, Hyper-V: Yes

PCI Passthrough

 

cheers,

 

- stay home and don't eat bats

 

[0] https://github.com/qemu/qemu/blob/master/docs/igd-assign.txt

[1] https://www.redhat.com/archives/vfio-users/2018-April/msg00022.html

[2] https://unraid.net/blog/unraid-server-os-6-3-released (Legacy and UTP mode)

[3] https://vfio.blogspot.com/2016/07/intel-graphics-assignment.html

[4] https://github.com/qemu/qemu/blob/master/docs/igd-assign.txt

[5] https://forums.unraid.net/topic/83802-intel-gvt-g-support-multiple-virtual-intel-igpus-we-already-have-gvt-d/?tab=comments#comment-776192&searchlight=1

[6] https://www.reddit.com/r/VFIO/comments/fzje5x/no_output_from_igpu_when_passed_through/

[7] https://github.com/intel/gvt-linux/issues/23

 

PS: I think the IGD passthrough will be more popular in the future as services like Stadia and Geforce Now will emerge and improve. This allows casual gamer to enjoy a gaming session with their IGD driven Windows 10 VM. Also GVT-D is a thing [5]. However, I think we will not see this in Unraid in the near future since its focus are NAS features.

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?