Javen

Hello, Recently I am working on my homelab network upgrade from 2.5G to 25G(just new to fiber world). The start point is that I move all my workspaces(lots of source code and pytorch models) to NAS thus I want a fast remote SMB access near local storage speed. Back to the topic, here I have 2 25G NICs. One installed on my working PC and one on Unraid(my NAS). However the one installed on unraid seems doesn't have correct driver thus doesn't show in network settings. But I can see it in system device and can passthrough it to a VM. Since the key point is to get a fast link between my working PC and NAS, without buying another expensive 25G switch, in theory I have 3 options: 1. Just install the 2 NICs on baremetal windows and unraid and use a fiber to connect. This is the most straightforward way. 2. Assign the NIC installed on Unraid to a VM, e.g. openwrt and just bond all the NIC ports and virtual NIC to make it perform like a switch. 3. Totally turn Unraid to a All-in-one server, including a openwrt VM perform like a router. Since it looks my nic doesn't show up in network setting in Unraid, so 1# not work. Or maybe I can try to compile the driver for unraid, but I really don't know how to do that. Now I switched to 2#, which mean a openwrt VM will perform like a switch and bond the 25G NIC ports and the VM's virtual NIC. Then I tried to perform a ipref3 test from the workstation, here is the result: 1. From windows to Openwrt VM, it says around 20G bitrate [ ID] Interval Transfer Bitrate [ 5] 0.00-10.01 sec 23.7 GBytes 20.4 Gbits/sec sender [ 5] 0.00-10.07 sec 23.7 GBytes 20.2 Gbits/sec receiver 2. From windows to Unraid Server(physically it's the same machine with Openwrt), it says around 3-5G bitrate. (With Virtio, others perform much worse, e.g. e1000 around 700~1000MB) [ ID] Interval Transfer Bitrate [ 5] 0.00-10.01 sec 5.05 GBytes 4.34 Gbits/sec sender [ 5] 0.00-10.02 sec 5.05 GBytes 4.33 Gbits/sec receiver 3. From Unraid Server to windows [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 16.5 GBytes 14.2 Gbits/sec 0 sender [ 5] 0.00-10.00 sec 16.5 GBytes 14.2 Gbits/sec receiver Then I try to perform a CrystalDiskMark test toward the cache share on Unraid(2 x 256GB PCIe 3.0 SSD, PM961 and SM961, btrfs+raid1), it says: [Read] SEQ 1MiB (Q= 8, T= 1): 1467.612 MB/s [ 1399.6 IOPS] < 5710.67 us> SEQ 128KiB (Q= 32, T= 1): 1858.934 MB/s [ 14182.5 IOPS] < 2254.66 us> RND 4KiB (Q= 32, T=16): 352.017 MB/s [ 85941.7 IOPS] < 5949.30 us> RND 4KiB (Q= 1, T= 1): 13.625 MB/s [ 3326.4 IOPS] < 300.44 us> [Write] SEQ 1MiB (Q= 8, T= 1): 587.593 MB/s [ 560.4 IOPS] < 14229.88 us> SEQ 128KiB (Q= 32, T= 1): 491.525 MB/s [ 3750.0 IOPS] < 8508.06 us> RND 4KiB (Q= 32, T=16): 136.177 MB/s [ 33246.3 IOPS] < 15352.36 us> RND 4KiB (Q= 1, T= 1): 13.689 MB/s [ 3342.0 IOPS] < 298.99 us> Here I have couple questions: 1. The samba test show good performance with SEQ read. However, 4k(Q1/T1) read/write is much worse than the result from testing locally. Is that because SMB or network? Now I almost keep all disk and SMB setting default in Unraid. 2. While the speed between my PC and openwrt VM is good(almost 25G), there is a big drop between PC and unraid. Is it the VM's virtual NIC the bottleneck? Is there any improvement can do? 3. I am just new to this area, is there any other better solution?

Tried this one, still got error code 43...

Do you mean just leave GPU part as it is in first creation? Will try that. Maybe I tried that before days ago when I just came back from a Windows Server and almost forgot how to passthrough GPU in Unraid.

Hello, I’m facing some issues when passing through my 7900 XTX to windows VM. (Error code 43) My build: AMD Ryzen R9 7950 Gigabyte B650m elite (with latest 1.0.0.7c bios) 4x32GB RAM PowerColor hellhound 7900xtx Nvidia Tesla P40 Tried following setting combination(not all combination tested, but most possible ones all tested and no luck. E.g. if some basic configuration doesn’t work, I might enable unsafe interrupts and test again but not regression test all previous combinations): Bios: 1. Resize bar on or off 2. CSM on or off Unraid: 1. PCIe ACS override set to No or Both 2. VFIO allow unsafe interrupts: No or Yes 3. Append video=efifb:off,vesafb:off for boot entry 4. Switch between UEFI and legacy boot mode 5. VFIO bound GPU and corresponding sound card part 6. Install Radeon reset bug plugin or not VM(I will paste my configuration here): 1. VM and CPU part: <memoryBacking> <source type='memfd'/> <access mode='shared'/> </memoryBacking> <vcpu placement='static'>16</vcpu> <os> <type arch='x86_64' machine='pc-q35-7.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/7cf78376-63b6-b8c6-5499-5421719f1fd7_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vpindex state='on'/> <synic state='on'/> <stimer state='on'/> <vendor_id state='on' value='1234567890ab'/> </hyperv> <kvm> <hidden state='on'/> </kvm> </features> <cpu mode='host-passthrough' check='none' migratable='off'> <topology sockets='1' dies='1' cores='16' threads='1'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> 2. GPU part: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/vbios/7900xtx.rom'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x1'/> </hostdev> Couple combinations I tried for VM configuration: 1. With or without vBios. 2. vBios dump from GPUz(on other bare metal Windows), from Unraid dump vBios script and download from TechPowerup(I use red devil one) 3. Vendor id none or a random one. 4. KVM hidden state on or not specify at all. I tested above combination for about 3 days, followed many guides in other thread, and still no luck. It always report error code 43 in windows device manager. e.g.: 1. A thread talk about 7900xt passthrough 2. Previous AMD 5700xt passthrough Any one can still give me a hint? PS: Not sure if it’s relevant, but in another 7900xt passthrough thread, it’s mentioned to passthrough all 4 devices related to the GPU. However in my case, there is only 2. Let’s say in Unraid System devices section, my GPU is located in 03:00:xx. I can only see a VGA compatible controller and one Audio device in 03:00:xx. I guess is it might related to usbc ports from reference card(which my model doesn’t have).

I just created a new array and tried to import as data via SMB. Here is the setup: Unraid: 1. 1 x 14 TB HDD(as array disk) 2. 1 x 2 TB SSD(as cache) Only one share is created and set "use cache pool" option as "yes". External: 1 x 16TB HDD(contains about 6TB data, ~80GB each file) I tried to copy all data on external HDD to unraid via SMB. As I understood, as "use cache pool" is set to "yes", unraid will try first storing all data on cache, once there is no enough space on cache, it will store remaining data on the HDD. However, I just got an error once the cache is full. Here is my doubt: 1. why unraid won't create new files onto the array directly once the cache is full? even the use cache pool option is set to 'yes' instead of 'only' 2. let's say we have different kind of data, some of them might be accessed frequently. If I only use one share to store all data, will unraid eventually automatically move the frequent used files to cache and leave others in array? Or I have to separate different share for different purpose and set different cache strategy on each?

Hello, Recently I bought a GC Titan ridge card and installed it with my Gigabyte B650M MB. The issue comes when I tried to passthrough the whole card to my VM. I can somehow manage to make the card and dock work, but not fully. Here is my finding: 1. The thunderbolt 3 dock and the GC Titan ridge card are both listed as PCIe devices in system devices and both can be bound to vfio at boot. (I think this might be the cause of the issue) 2. I can passthrough both devices(dock and card) to VM and it works including hotplugging USB devices on the dock and DP display. Thunderbolt software can detect the dock as well. 3. However, the big big drawback of 2# is that the dock is passed through as a PCIe device. That means the dock itself must be connected with the server always. Just as a standard PCIe device, unplug it will cause issue and even VM can't start without it. That means the hotplug feature of the dock itself is completely lost. 4. If I try to only passthrough the card itself, the card can be detected in Windows normally. However, devices connected to the dock will not be recognized. Even there is no any entries in device manager. Is my understanding right that the issue comes because the dock itself is a PCIe device rather than a USB device? The logic is totally different compare to USB controller passthrough. And is there a way to fix it?

I tried to revert the bios to the default one, still crash on VM start up. Here is my VM setting. I would like to collect logs as well, but seems logs under tool-> system log section only contains log this time start up. Anyone know where can find a clue? <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='2'> <name>Windows 11 Home Station</name> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>33554432</memory> <currentMemory unit='KiB'>33554432</currentMemory> <memoryBacking> <source type='memfd'/> <access mode='shared'/> </memoryBacking> <vcpu placement='static'>16</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='16'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='17'/> <vcpupin vcpu='4' cpuset='2'/> <vcpupin vcpu='5' cpuset='18'/> <vcpupin vcpu='6' cpuset='3'/> <vcpupin vcpu='7' cpuset='19'/> <vcpupin vcpu='8' cpuset='4'/> <vcpupin vcpu='9' cpuset='20'/> <vcpupin vcpu='10' cpuset='5'/> <vcpupin vcpu='11' cpuset='21'/> <vcpupin vcpu='12' cpuset='6'/> <vcpupin vcpu='13' cpuset='22'/> <vcpupin vcpu='14' cpuset='7'/> <vcpupin vcpu='15' cpuset='23'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-7.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/3eb57ddf-c897-323c-dc7e-8c78d7333382_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <vpindex state='on'/> <synic state='on'/> <stimer state='on'/> <reset state='on'/> <vendor_id state='on' value='KVM Hv'/> <frequencies state='on'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='8' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> <feature policy='disable' name='monitor'/> <feature policy='require' name='hypervisor'/> <feature policy='disable' name='svm'/> <feature policy='disable' name='x2apic'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='yes'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 11 Home Station/vdisk1.img' index='3'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='2'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.225-2.iso' index='1'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0x16'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0x17'/> <alias name='pci.8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x7'/> </controller> <controller type='pci' index='9' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='9' port='0x18'/> <alias name='pci.9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='10' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='10' port='0x19'/> <alias name='pci.10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/> </controller> <controller type='pci' index='11' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='11' port='0x1a'/> <alias name='pci.11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x2'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </controller> <filesystem type='mount' accessmode='passthrough'> <driver type='virtiofs' queue='1024'/> <binary path='/usr/libexec/virtiofsd' xattr='on'> <cache mode='always'/> <sandbox mode='chroot'/> <lock posix='on' flock='on'/> </binary> <source dir='/mnt/user/NAS'/> <target dir='NAS'/> <alias name='fs0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='52:54:00:3b:d8:e0'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-2-Windows 11 Home Stat/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> <alias name='tpm0'/> </tpm> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x10' slot='0x00' function='0x1'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x0'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0d' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0f' slot='0x00' function='0x0'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x10' slot='0x00' function='0x3'/> </source> <alias name='hostdev4'/> <address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x10' slot='0x00' function='0x4'/> </source> <alias name='hostdev5'/> <address type='pci' domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>

Recently I upgraded my rig with brand new Zen4 series: CPU: AMD 7950x Mem: 2 x 32 GB DDR5 oc to 6200 MB: Gigabyte B650m Aorus Elite ax I can see 4 USB controllers in Unraid system devices, and it seems match the MB specification: I moved the unraid USB disk to the "CPU + USB 2.0 HUB", passed through all other 3 to my Windows VM. I also did a double check followed this guide: And it seems all my USB controller are marked with RESET, sounds very good. (My previous system has no RESET flaged USB controller). Then I bounded these 3 USB controllers to Vfio in system devices pannel, then passed them to VM by using hostdev tag. The issue comes when I tried to start the VM. 1. If these is no devices connected to these 3 controller(strictly it's not possible because these are some onboard devices connected to these controllers), VM can be started normally and all the USB ports works fine later on include data transfering with USB disks.(I didn't test everyone, but seems OK) 2. If there are storage devices connected to any of the 3 controllers(I tried with a Sandisk USB extreme pro disk and Intel 600p 512G with a USB convertor, both will cause issue), immediately after VM start up, the whole rig will be shutdown and reboot automatically. 3. If I try to connect a KVM switcher to any of the 3 controllers (a keyboard, a mouse attached and a USB camera attached), VM can be start normally.(Just like 1#) Why the scenario 2# the rig will shutdown right afer the VM started up while rest scenarios seems working perfectly? Currently I have no access to my server, will attach logs and VM settings later.

I purchase a brand new 7950x recently and tested the exact same scenario. I have allocated 10cores/20 threads and 32 GB RAM to the VM. After the feature enabled, no big difference from daily usage. However, if you monitor the CPU usage and try some benchmark like CPUZ, still you can see a big big performance drop. e.g. CPUz single core: Core isolation off: 740-750 Core isolation on: 600+ If you monitor the CPU usage: Core isolation off: normally <10% or even 5%, Core isolation on: 10%~ 20%, if open a file explorer, it might go up to 30%-40%. (if set off, it's about ~10% CPU usage to open a new file explorer). As I said, CPU like 7950x can still leave it enabled, but the cost is still high. I still perfer it off.

I recently bought a 7950x and it comes with a iGPU. I would like to use it for Jellyfin decoding. However, things are not that smooth. I have installed Radeon top plugin and GPU statistics, passed through the iGPU to the jellyfin docker container though /dev/dri, changed the hw acceleration to AMF, but immediately I got an error when I play a movie. I tried to dig out something in the jellyfin FFmepg log, it did mention some error as below: After some search, some posts mentioned it need amdgpu pro driver. And I do remember that the driver is mentioned as a must in Jellyfin HW transcoding doc. So, looks that manually install amdgpu pro is the only way? But how? I could download the close source linux driver somewhere and install, but isn't that unraid will wipe these customized things every reboot?

Thank you. I learn something new. I have to admit that I new basic operation of linux but not detail.

I'm new to use TMM. Just wonder how to automatically update my movies? I mean I put new movies in the data source, but how to set TMM to automatically update data source and scape without doing any manual work?

Maybe it's too basic... I fixed the issue but just don't understand why. I put my sharing folder to 644(chmod to grant only read/write permission to the owner, , just ignore later 2 bits) and use the exact same user to which I chown to access the Samba folder remotely. The issue appears that I can only see the first level parent folder content and can't navigate to the child folders. (On windows, it just return empty folders. On Mac, it reports permission deny explictly) BTW, I have set the share to private in unraid and set the specific user have read/write permission(unraid permission,not linux) to the share. Again I chmod all files to 755 by using chmod -R 755 *(Surely under the sharing folder), and the Samba sharing is OK now. But why? Isn't that read and write permission(644, just ignore later 2 bits) enough? Why the execution bit is required to make SMB share functional?

There is a very strange issue when I passthrough onboard sound card to my Win 11 VM. After some certain time(maybe hours or days), I will lose the sound from SPDIF interface. Only restart/shutdown the VM will not recover, the solution is to reboot the phycical machine entirely. One more thing, when the sound from SPDIF interface is lost, other sound interfaces from other devices(e.g. GPU, bluetooth) are still working. E.g. If the monitor will play sound if I switch the output to HDMI. What could be the reason for the issue? Here is my VM setting regarding the USB passthrough part. (My onboard sound card is detected as USB device in the 'USB devices' list) I haven 't passthrough any PCIe devices related to sound to the VM. (I do have passthrough a GPU/2 nvme SSD/a USB card to the VM) <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0db0'/> <product id='0x8af7'/> <address bus='1' device='3'/> </source> <alias name='hostdev5'/> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1b1c'/> <product id='0x0c07'/> <address bus='1' device='8'/> </source> <alias name='hostdev6'/> <address type='usb' bus='0' port='2'/> </hostdev> My hardware: Mainboard: MSI MPG Z590 GAMING FORCE (MS-7D06) CPU: Intel i7 11700k oc RAM: 4*8G oc DDR4 3600

I have upgraded Windows 11 VM to the latest version and seems there is a new option in "Device security" named Core isolation/Memority integrity. (Or maybe I didn't notice it before) Enable the option will make the VM extremely slow. Before enabling, the CPU usage is around <5%. After enabling the option, it's jumpping between 40%~70% and sometime goes to 100%. My VM detail: CPU: 11700K (4 Cores/8 Threads, CPU isolation set) Mem: 16G 2 nvme SSD passthrough GPU: Nvidia GTX 1070 passthrough 11700K iGPU to shared to plex docker for HW transcoding. I read somewhere the option might be based on some virtualization tech so I assume it might conflict with virtual machines. Also I understand it can be skipped by just not enabling the option. Only I would like to make sure if I understand it correctly or is there any real fix for it? Here is also my VM settings. <name>Windows 11 Work Station</name> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='8'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='9'/> <vcpupin vcpu='4' cpuset='2'/> <vcpupin vcpu='5' cpuset='10'/> <vcpupin vcpu='6' cpuset='3'/> <vcpupin vcpu='7' cpuset='11'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-6.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/f96ea022-1e18-bc17-4bda-52bba8a978cf_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <vpindex state='on'/> <synic state='on'/> <stimer state='on'/> <reset state='on'/> <vendor_id state='on' value='KVM Hv'/> <frequencies state='on'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='4' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> <feature policy='disable' name='monitor'/> <feature policy='require' name='hypervisor'/> <feature policy='disable' name='svm'/> <feature policy='disable' name='x2apic'/> </cpu> <clock offset='utc'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='yes'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash>