spotopolis

Sorry. Not trying to be demanding. Trying to assist. No rush on my end. I appreciate your work. I use a lot of your containers.

@ich777 Here is a link to the github where they (Wolveix) are working on the API issue. (4) 1.0 API Connection Issue · Issue #260 · wolveix/satisfactory-server (github.com)

I see there is another user hosting a Docker for Satisfactory on the official Discord. It looks like they are working on the API fix as well.

Yes. And this is a local server on my home network, so even If I didn't, port forwarding shouldn't matter as I am directly connecting to the local IP

Trying to connect on 7777

I tried this and also updated the container and while in-game, trying to connect to the server, I am getting an API error

Did you ever find a solution to this? I would like to do the same.

I just tried that, and I didn't see any difference after another reboot. I ran lspci -k and the card is still not binding to vfio-pci

I did find this LINK in the Netgate documentation about this specific QAT device and the issues with VFIO-PCI checks. On their devices the drivers have the QAT on a denylist. Is it possible this is also in a denylist that can be overridden in Unraid?

I undid everything and rebooted to start over from scratch thinking maybe something was done out of order causing the issue. I started by just editing /boot/config/VMPCIOverride.cfg and adding to it "0000:83:00.0|8086:0435": I then rebooted and checked if that made a difference on its own. No. It did not. So I then checked the corresponding box under Tools->System Devices: and then verified that it was actually written to the file in /boot/config/vfio-pci.cfg: (the other two devices are a dual port Intel NIC I have already passed to the VM successfully) Yes it is actaully showing up in the vfio-pci.cfg when the box is ticked in the GUI. So I rebooted once more after making that change. This still did not allow me to add the QAT to the VM. I then checked the VFIO-PCI log in Tools->System Devices. At the top of the log, the device is being detected and has been bound to the vfio-pci, however, at the bottom of the log, I am only seeing the dual port Intel NIC that I have already passed though to the VM. The QuickAssist card is not showing up as listed in /sys/bus/pci/drivers/vfio-pci: I went ahead and tried to add it to the VM XML again anyway: This is how it was added. I got the same error again about the device not being found. So I went back to edit the XML to revert the changes I made, and noticed the bus had changed from '0x00' to '0x04': Im assuming this is referencing the VMs virtual bus that it is attached to, and not the physical bus on the host, correct? I also checked the path for the IOMMU groups since I was getting the error that 37 did not exist: Indeed only the dual port Intel NIC is showing up in that path and 37 for the QAT is not listed.

I got back home and did a manual edit to the XML: After saving the XML and trying to boot the VM, the VM would not boot and I got this error: 37 is the correct IOMMU group

Ill have to pick this up tomorrow if I am going to be editing the XML. I am away from home right now, so anytime I have rebooted my server, I have to wait for that VM to come back up to be able to connect to my VPN, to check the changes made. If I need to edit the XML, that means the VM is down, and I wont have a remote connection.

That resolved the errors at the top of the lspci -k output, but the device is still not showing as in use by vfio EDIT: brain fart. I just realized that the device would not show up as "in use" until it was attached to the VM and "IN USE", however, it is still not displayed as an option to add to the VM when I go to edit it. Am I going to need to manually add it in the XML view again? I dont believe that would work at this point though because I am still not seeing the QAT in

After running lspci -k, I happened to scroll up and caught this up top. It does not look like it is bound to vfio. EDIT: This is what I am seeing in the VFIO-PCI log I dont understand because it looks like its bound to VFIO in the logs.

Came back from a reboot and the option is still not available to pass to the VM. I did notice if I expanded the view from "in use" to "all" drivers, the Common is listed in use as well. Im going to blacklist that as well, reboot and see if that helps.