ich777

Sorry but you are using a lot of swear words I if my Google translate is correct and I'm not happy about that because we have forum rules here, they apply also if you are using a foreign language I would however prefer that you use Google translate and post the translation to English here, that would make my life (and maybe the life of other users here) easier because the main forum language is English... However you should really take a look Meta Mod in combination with Source Mod since I use these to have a in game menu and change Maps, Bots, Player commands and so on. You can also do that from the command line with RCON. Sorry, I won't do a full tutorial because I only provide basic functionality, so to speak the game server itself (modding is always up to the user and I can't help with that because there are many games and even more mods for the games and I simply can't know every mod and how to even mod the game - I do for a few and try to help where I can ). However in terms of CS:GO it is a completely different story because if you would have searched for "CS:GO Unraid" on Google one of the first results is the blog post from over here.

What do you mean you have a special DNS for it? Do you set up a domain for the container? You can't access txAdmin from you LAN? There must be something wrong with the network setup, I really don't know what to tell you here, I've set up a instance just for testing and it is working over here and I get no errors so far.

This is expected and was discussed multiple times in this thread. For ZFS it would be better to create a subvolume share that subvolume on the pool and then format it correctly on the initiator side. Exactly.

That sounds complicated for a game server, really complicated. Just use the default bridge network and forward the ports in your router/firewall, that's usually enough for a game server. I don't understand what you mean exactly...?

Yes, but I haven't looked into that yet. This is just the main directory where you want to compile in, doesn't matter where. This is just the tag from here. This is just a shell expansion from the version from above.

It seems that the container can't communicate with the server or does run into some kind of timeout, do you maybe have any adblocking or Unifi network gear on your network? Make sure that the container has exclusive access to the internet. Have you read the description here: Delete text 'server.cfg' from that variable, then you have to create a port entry in the template at the bottom with "Add another Path, Port, Variable, Label or Device" select "Port", at the host and container port you have to specify 40120 and as the protocol TCP. After that you should be able to connect to the txAdmin through YOURSERVERIP:40120

This process it noVNC and is basically what you need to be able to use noVNC. Have you yet thought about that that maybe your Wireguard gateway is blocking the requests? As said above there is nothing in the container by itself that would block outside requests by default, the container is also working fine if you use it in combination with a OpenVPN connection.

In the Diagnostics you've provided you have a Trace here: Dec 23 12:02:29 brain kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access Dec 23 12:02:29 brain kernel: BUG: unable to handle page fault for address: 0000000fffffffe8 Dec 23 12:02:29 brain kernel: #PF: supervisor read access in kernel mode Dec 23 12:02:29 brain kernel: #PF: error_code(0x0000) - not-present page Dec 23 12:02:29 brain kernel: PGD 103b1c067 P4D 103b1c067 PUD 0 Dec 23 12:02:29 brain kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI Dec 23 12:02:29 brain kernel: CPU: 8 PID: 1125 Comm: udevd Tainted: P O 6.1.64-Unraid #1 Dec 23 12:02:29 brain kernel: Hardware name: Micro-Star International Co., Ltd. MS-7D32/MAG Z690 TOMAHAWK WIFI DDR4 (MS-7D32), BIOS 1.F0 11/02/2023 Dec 23 12:02:29 brain kernel: RIP: 0010:kernfs_root+0x0/0x14 Dec 23 12:02:29 brain kernel: Code: 89 cb 44 8b 6c 24 30 e8 24 32 fb ff 48 8b bd 58 02 00 00 48 89 da 5b 48 89 c6 5d 4c 89 e1 45 89 e8 41 5c 41 5d e9 66 ff ff ff <48> 8b 47 08 48 85 c0 48 0f 45 f8 48 8b 47 50 c3 cc cc cc cc 0f 1f Dec 23 12:02:29 brain kernel: RSP: 0018:ffffc9000096fa88 EFLAGS: 00010286 Dec 23 12:02:29 brain kernel: RAX: 0000000000000000 RBX: 0000000fffffffe0 RCX: ffffffff813f52b3 Dec 23 12:02:29 brain kernel: RDX: 0000000000000000 RSI: ffffffff81e987e8 RDI: 0000000fffffffe0 Dec 23 12:02:29 brain kernel: RBP: ffffffff81e986a0 R08: 0000000000000000 R09: ffffffff829513f0 Dec 23 12:02:29 brain kernel: R10: 00003fffffffffff R11: fefefefefefefeff R12: ffff888107c25848 Dec 23 12:02:29 brain kernel: R13: ffff8881011be000 R14: ffff888103809b50 R15: ffff8881011be0d0 Dec 23 12:02:29 brain kernel: FS: 000014e276d8e240(0000) GS:ffff889fff600000(0000) knlGS:0000000000000000 Dec 23 12:02:29 brain kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 23 12:02:29 brain kernel: CR2: 0000000fffffffe8 CR3: 0000000103992000 CR4: 0000000000750ee0 Dec 23 12:02:29 brain kernel: PKRU: 55555554 Dec 23 12:02:29 brain kernel: Call Trace: Dec 23 12:02:29 brain kernel: <TASK> Dec 23 12:02:29 brain kernel: ? __die_body+0x1a/0x5c Dec 23 12:02:29 brain kernel: ? page_fault_oops+0x329/0x376 Dec 23 12:02:29 brain kernel: ? do_user_addr_fault+0x12e/0x48d Dec 23 12:02:29 brain kernel: ? exc_page_fault+0xfb/0x11d Dec 23 12:02:29 brain kernel: ? asm_exc_page_fault+0x22/0x30 Dec 23 12:02:29 brain kernel: ? __blk_mq_run_hw_queue+0x73/0x73 Dec 23 12:02:29 brain kernel: ? kernfs_vfs_xattr_set+0x41/0x41 Dec 23 12:02:29 brain kernel: kernfs_find_and_get_ns+0x1c/0x5c Dec 23 12:02:29 brain kernel: sysfs_unmerge_group+0x16/0x4d Dec 23 12:02:29 brain kernel: dpm_sysfs_remove+0x1e/0x52 Dec 23 12:02:29 brain kernel: device_del+0xa4/0x31d Dec 23 12:02:29 brain kernel: ? i915_ggtt_probe_hw+0x593/0x5be [i915] Dec 23 12:02:29 brain kernel: platform_device_del+0x21/0x70 Dec 23 12:02:29 brain kernel: platform_device_unregister+0xf/0x19 Dec 23 12:02:29 brain kernel: sysfb_disable+0x2b/0x54 Dec 23 12:02:29 brain kernel: aperture_remove_conflicting_pci_devices+0x1e/0x82 Dec 23 12:02:29 brain kernel: i915_driver_probe+0x83f/0xc19 [i915] Dec 23 12:02:29 brain kernel: ? slab_free_freelist_hook.constprop.0+0x3b/0xaf Dec 23 12:02:29 brain kernel: local_pci_probe+0x3d/0x81 Dec 23 12:02:29 brain kernel: pci_device_probe+0x197/0x1eb Dec 23 12:02:29 brain kernel: ? sysfs_do_create_link_sd+0x71/0xb7 Dec 23 12:02:29 brain kernel: really_probe+0x115/0x282 Dec 23 12:02:29 brain kernel: __driver_probe_device+0xc0/0xf2 Dec 23 12:02:29 brain kernel: driver_probe_device+0x1f/0x77 Dec 23 12:02:29 brain kernel: ? __device_attach_driver+0x97/0x97 Dec 23 12:02:29 brain kernel: __driver_attach+0xd7/0xee Dec 23 12:02:29 brain kernel: ? __device_attach_driver+0x97/0x97 Dec 23 12:02:29 brain kernel: bus_for_each_dev+0x6e/0xa7 Dec 23 12:02:29 brain kernel: bus_add_driver+0xd8/0x1d0 Dec 23 12:02:29 brain kernel: driver_register+0x99/0xd7 Dec 23 12:02:29 brain kernel: i915_init+0x1f/0x7f [i915] Dec 23 12:02:29 brain kernel: ? 0xffffffffa0ab7000 Dec 23 12:02:29 brain kernel: do_one_initcall+0x82/0x19f Dec 23 12:02:29 brain kernel: ? kmalloc_trace+0x43/0x52 Dec 23 12:02:29 brain kernel: do_init_module+0x4b/0x1d4 Dec 23 12:02:29 brain kernel: __do_sys_init_module+0xb6/0xf9 Dec 23 12:02:29 brain kernel: do_syscall_64+0x68/0x81 Dec 23 12:02:29 brain kernel: entry_SYSCALL_64_after_hwframe+0x64/0xce Dec 23 12:02:29 brain kernel: RIP: 0033:0x14e2772a0dfa Dec 23 12:02:29 brain kernel: Code: 48 8b 0d 21 20 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d ee 1f 0d 00 f7 d8 64 89 01 48 Dec 23 12:02:29 brain kernel: RSP: 002b:00007ffdde819638 EFLAGS: 00000246 ORIG_RAX: 00000000000000af Dec 23 12:02:29 brain kernel: RAX: ffffffffffffffda RBX: 0000000000468c20 RCX: 000014e2772a0dfa Dec 23 12:02:29 brain kernel: RDX: 000014e277395aad RSI: 00000000004b1868 RDI: 000014e276476010 Dec 23 12:02:29 brain kernel: RBP: 000014e277395aad R08: 0000000000000007 R09: 0000000000464e30 Dec 23 12:02:29 brain kernel: R10: 0000000000000005 R11: 0000000000000246 R12: 000014e276476010 Dec 23 12:02:29 brain kernel: R13: 0000000000000000 R14: 0000000000468600 R15: 0000000000000000 Dec 23 12:02:29 brain kernel: </TASK> Dec 23 12:02:29 brain kernel: Modules linked in: amdgpu zfs(PO+) i915(+) zunicode(PO) zzstd(O) intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel zlua(O) zavl(PO) icp(PO) kvm gpu_sched drm_ttm_helper iosf_mbi drm_buddy i2c_algo_bit ttm crct10dif_pclmul crc32_pclmul zcommon(PO) crc32c_intel drm_display_helper ghash_clmulni_intel sha512_ssse3 sha256_ssse3 btusb sha1_ssse3 znvpair(PO) btrtl drm_kms_helper mei_hdcp aesni_intel intel_gtt mei_pxp btbcm crypto_simd cryptd spl(O) drm wmi_bmof mxm_wmi rapl btintel intel_cstate bluetooth intel_uncore mpt3sas(+) nvme agpgart i2c_i801 mei_me syscopyarea i2c_smbus ahci sysfillrect raid_class ecdh_generic sysimgblt video tpm_crb igc i2c_core mei nvme_core scsi_transport_sas joydev libahci ecc fb_sys_fops thermal fan tpm_tis tpm_tis_core tpm wmi intel_pmc_core backlight acpi_pad acpi_tad button unix Dec 23 12:02:29 brain kernel: CR2: 0000000fffffffe8 Dec 23 12:02:29 brain kernel: ---[ end trace 0000000000000000 ]--- Dec 23 12:02:29 brain kernel: RIP: 0010:kernfs_root+0x0/0x14 Dec 23 12:02:29 brain kernel: Code: 89 cb 44 8b 6c 24 30 e8 24 32 fb ff 48 8b bd 58 02 00 00 48 89 da 5b 48 89 c6 5d 4c 89 e1 45 89 e8 41 5c 41 5d e9 66 ff ff ff <48> 8b 47 08 48 85 c0 48 0f 45 f8 48 8b 47 50 c3 cc cc cc cc 0f 1f Dec 23 12:02:29 brain kernel: RSP: 0018:ffffc9000096fa88 EFLAGS: 00010286 Dec 23 12:02:29 brain kernel: RAX: 0000000000000000 RBX: 0000000fffffffe0 RCX: ffffffff813f52b3 Dec 23 12:02:29 brain kernel: RDX: 0000000000000000 RSI: ffffffff81e987e8 RDI: 0000000fffffffe0 Dec 23 12:02:29 brain kernel: RBP: ffffffff81e986a0 R08: 0000000000000000 R09: ffffffff829513f0 Dec 23 12:02:29 brain kernel: R10: 00003fffffffffff R11: fefefefefefefeff R12: ffff888107c25848 Dec 23 12:02:29 brain kernel: R13: ffff8881011be000 R14: ffff888103809b50 R15: ffff8881011be0d0 Dec 23 12:02:29 brain kernel: FS: 000014e276d8e240(0000) GS:ffff889fff600000(0000) knlGS:0000000000000000 Dec 23 12:02:29 brain kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 23 12:02:29 brain kernel: CR2: 0000000fffffffe8 CR3: 0000000103992000 CR4: 0000000000750ee0 Dec 23 12:02:29 brain kernel: PKRU: 55555554 This usually indicated a bug in the module itself and nothing I can do about, however it seems that everything is now working correct? However it should be not necessary to unbind you AMD card from VFIO.

You don‘t have to do that because the VMs should work fine even if you i stall the older version. However it seems really strange to me that you have issues with the new version since nothing should have changed, but I haven‘t gone through the source from the files what could cause this and haven‘t got a chnce to look into the conversation that you‘ve linked above (Christmas and holidays…).

I don‘t think so because otherwise Chromium wouldn‘t work at all when using it without Wireguard. This seems like more of an issue with the configuration.

Yes.

Can you please post your Diagnostics?

A Tesla P4 is working fine with this driver, do a search in this topic for ‚Tesla P4‘.

What card do you have, some are supported. Can‘t do that because the driver is proprietary and you only can get access to if registred and even if I have the driver, redistribution is not allowed by Nvidia.

I really can't help there since this seems like something proprietary what a "nomral" Target can't understand, if everything is working you have to ignore this message.

Merry Christmas. Only English please. As you can see from the screenshot your are now locked out of your account and probably your IP is also banned for a few hours from Steam so you can't log in. !!! Please never user your real Steam Credentials if they are not marked as required with the red asterisk in the template !!! I can't help with that since modding is always up the the user, I think you should really take a look at the 2nd recommended post on top of this thread, it's for a ARK cluster but you will find, even not for a cluster, useful information and maybe also what you are searching for.

Bitte poste deine Diagnostics. Genau dort liegt das Problem, Unraid basiert auf Linux und nicht alle Karten haben Treiber, vergiss auch nicht das vermutlich auf Windows die Karten auch nicht mehr funktionieren da WHS auf Windows XP basiert bzw. Windows 2000 wenn ich mich nicht täusche (war auch mal an dem Punkt. Ich hoffe du hast es nicht nach außen frei gegeben? Mit der Access Controll in TVH, aber zuerst mal würde ich mich gerne mit den TV Karten beschäftigen welche du genau hast und dazu bräuchte ich die Diagnostics.

Please avoid double posting, I just approved one post.

Please unbind you iGPU from VFIO on the System page since if you bind it to VFIO Unraid can't "see" your iGPU because you reserve it for usage in VMs. After unbinding it reboot and you will have the directory /dev/dri on your Server. Please make sure that you are using the official one from the repository: jellyfin/jellyfin

IIRC you don't have to pass over everything there, you can change values in the config files too. Are these values also reset? TBH I don't remember that these values are also reset on a server restart in the config.

Wo du willst, wo willst du es denn hin haben? Auf ein Pool Laufwerk? Das beispiel zeigt eine Unassigned Device. Das ist ein Plugin, findest du in der CA App: Kein ding, du kommst schon sicher noch dahinter und wir sind ja hier, aber alles erklären wird schwierig, trail and error, wenn du wirklich wo nicht weiterkommst wird dir gerne hier geholfen. Danke Ebenso. 🎄🎁

It should look like this if you want 40 players for example:

Are you sure that you stop the container, edit the file, save the file and then start the container again?

Please remove your guide if possible! This will certainly cause issues for users if they upgrade or modify the libvirt.img in any way, instead I would recommend that you install the files which ship with Unraid 6.11.x via this method, please make sure that you first stop all of your VMs in the first place and then execute these commands from a terminal: mkdir -p /tmp/edk2 cd /tmp/edk2 wget -O /tmp/edk2/edk2.txz https://github.com/ich777/edk2-unraid/releases/download/edk2-stable202305/ovmf-stable202305-x86_64-3.txz installpkg /tmp/edk2/edk2.txz rm -rf /tmp/edk2 This will install the edk2 firmware files from 6.11.5 (should be the build from 202305 - build 3). BTW, you can find all the builds from edk2 over here.

I have to say, I'm always on the latest stable/beta/RC and everything is working as it should. In my opinion this update strategy is really bad but that's just my opinion and the worst, you won't get support by most community developers or even the support desk itself if something is not working. It is more complicated than you think, a lot changed with 6.12.0+ and not everything which was in bzroot is there where it was below version 6.12.0 It is okay to post the command here on the forums I think but you also have to know the risk that somebody that is not that experienced will discover these commands and starts editing files and repacking the bzroot since strictly speaking there are only seven commands needed, just saying... cd /your/work/dir/bzroot dd if=/boot/bzroot bs=512 count=$(cpio -ivt -H newc < /boot/bzroot 2>&1 > /dev/null | awk '{print $1}') of=/your/work/dir/microcode dd if=/boot/bzroot bs=512 skip=$(cpio -ivt -H newc < /boot/bzroot 2>&1 > /dev/null | awk '{print $1}') | xzcat | cpio -i -d -H newc --no-absolute-filenames cd /your/work/dir/bzroot find . | cpio -o -H newc | xz --check=crc32 --ia64 --lzma2=preset=9e --threads=$(nproc --all) >> /your/work/dir/bzroot.part cat /your/work/dir/microcode /your/work/dir/bzroot.part > /your/work/dir/bzroot sha256sum /your/work/dir/bzroot | awk '{print $1}' > /your/work/dir/bzroot.sha256 Maybe you should issue a PR here or even create an Issue. But think again about that, if you would have gone straight to 6.12.6 then you wouldn't have these issues at all. BTW there would be also a way easier fix, just rename the package in /boot/extra if it won't install properly.