ross232

Thanks @alturismo and @geekunraid for your help, really appreciate both of your replies. @geekunraid looks like that setting did the trick! Thank you so much I have the following settings working perfectly again now on my Ryzen 5950X: <features> <acpi/> <apic eoi='off'/> <hyperv mode='passthrough'> </hyperv> <kvm> <hidden state='on'/> </kvm> <vmport state='off'/> <ioapic driver='kvm'/> </features> <cpu mode='host-passthrough' check='none' migratable='off'> <topology sockets='1' dies='1' clusters='1' cores='[SETME]' threads='[SETME]'/> <cache mode='passthrough'/> <feature policy='require' name='x2apic'/> <feature policy='require' name='tsc-deadline'/> <feature policy='require' name='hypervisor'/> <feature policy='require' name='tsc_adjust'/> <feature policy='disable' name='arch-capabilities'/> <feature policy='require' name='cmp_legacy'/> <feature policy='require' name='perfctr_core'/> <feature policy='require' name='virt-ssbd'/> <feature policy='disable' name='monitor'/> <feature policy='disable' name='svm'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='tsc' present='yes' tickpolicy='merge' mode='native'/> <timer name='hypervclock' present='yes'/> </clock> And <qemu:commandline> <qemu:arg value='-fw_cfg'/> <qemu:arg value='opt/ovmf/X-PciMmio64Mb,string=65536'/> <qemu:arg value='-overcommit'/> <qemu:arg value='cpu-pm=off'/> <qemu:arg value='-global'/> <qemu:arg value='q35-pcihost.pci-hole64-size=2048G'/> <qemu:arg value='-machine'/> <qemu:arg value='max-ram-below-4g=4G'/> </qemu:commandline>

Thanks, but I'm talking about Hyper-V passthrough specifically. CPU passthrough still works for me.

Just wondering - can anyone else confirm if <hyperv mode='passthrough'> works for them after this update? I'm running a Ryzen 5 5950x.

Had the same issue. Took me a long time to resolve it properly. Weirdly, I can't boot into Windows if I have <hyperv mode='passthrough'> specified - I will still get the Unsupported Processor error in this case. This never used to happen. It appears to have negatively impacted gaming performance for me.

@rushgunner have you got the Intel-GPU-TOP plugin installed? You might need this for an intel iGPU. Make sure it's updated.

I don't think ZFS is displacing any of the existing file system options. It's just another option you can optionally choose to use. In my case I'm using individual ZFS formatted drives in a normal parity protected array. The advantage here is that you can use snapshots, compression etc. But I retain the advantage of being able to use disks of different size and I can mount them individually. I also use ZFS on my cache drives because I don't love the way BTRFS reports free-space and have had issues with this in the past. I can see why there are use cases for people wanting a full ZFS array too. If speed is a priority then this will always win out over a parity + cache combo. People doing media creation (e.g. YouTubers etc) may want to start with a parity array, then migrate to a full ZFS backed one later. Add in the paid support options UNRAID now has and you have something you can rely on as your needs grow/change.

Hello, Does anyone know which file unassigned devices writes it's passthrough configuration to? I am having trouble with a VM. In the libvirt log I can see that it can't resolve a disk previously passed through as I have physically removed it. I can no longer change that configuration via the UI. Thanks, Ross

@SimonF Any reason chroot has to be used for virtiofs? Namespace doesn't want to load for me. Also - Virtiofs doesn't appear to lock up my Fedora Silverblue VM. I wonder if there is any common thread to the reports.

I can get it mounted in linux and write permissions seem to work as well. I just wish it would work for Steam/Proton games - I think flock or symlink functionality might not be working. Here's my config. I have this in my VM XML (memoryBacking also has hugepages but I've removed it from here): <memoryBacking> <source type='memfd'/> <access mode='shared'/> </memoryBacking> <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/'/> <target dir='shares'/> <alias name='fs0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </filesystem> And the following in my /etc/fstab in my VM: shares /mnt/unraid virtiofs 0 0 NB: You must create /mnt/unraid first in the VM.

Does anyone have virtiofs working with Steam games? Specifically those that use Proton? I can't launch games when I do it I get 'OSError: [Errno 95] Operation not supported'. Non proton games seem to work OK.

Oh I've got it now, thanks!

Hi @ich777. I've noticed that 6.10.0-rc1 has dropped. The release notes mention the GNIF plugin but I can't find it. Has it been released yet? Thanks Ross.

Oh that is awesome news Thanks for the reply too, much appreciated!

Hello, Sorry to be a nuisance - could I have my username changed to 'ross232'? Thanks!

@ich777 Thanks again for this. I used the tool to create a custom kernel with the GNIF patch and also coral and DVB drivers. I did want to ask - are plugins compatible with this? Initially I just had the GNIF patch on and then installed the DVB and Coral driver plugins from the app section. But as soon as the coral driver was modprobe'd I got a kernel panic. So I rebuilt with GNIF and coral drivers built in. But then I would get a kernel panic when my DVB hardware was initialised from the plugin as well. So ultimately I built the kernel with all three and that works fine.

Oh right that makes sense. I'll try tonight. Thanks 👍

@thor2002ro Thanks for this - I've just installed 5.13rc7 O3 What do I need to do to enable DVB on this kernel? I see the following in dmesg at the moment: [ 19.006411] dvb-usb: did not find the firmware file 'dvb-usb-dib0700-1.20.fw' (status -2). You can use <kernel_dir>/scripts/get_dvb_firmware to get the firmware The standard DVB plugin doesn't work with this kernel from what I can tell.

You can also put the following in as a user script that runs on first array start: #!/bin/bash echo 0 > /sys/class/vtconsole/vtcon0/bind echo 0 > /sys/class/vtconsole/vtcon1/bind echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind This will allow you to see unRAID booting via your GPU and then unhook it for use as passthrough into VMs.

Thanks for the rapid release Updating to 6.9 beta30 now.

Awesome, thanks for this. It's working really well

When you are not using a vBIOS and are using QF35 is unRAID still freezing for you? Just wondering if you can grab the VM log file and post it here. Also - does your GPU have it's own slot when ACS is disabled? I wasn't sure if you tested with this off.

I'm running an RX 480 on a Ryzen 5 2600 processor. I don't need a vBIOS at all with mine - are you sure you need one? I do use - rcu_nocbs and at the moment have disabled C States (although this may not be necessary). ACS isn't necessary for me (using a Tomahawk B350 BIOS). Have you made sure your BIOS is up to date? Check to see if your video card already has it's own IOMMU group in the unRAID diagnostics prior to enabling this. Also I need to use the Q35 machine type with OVMF for things to work.