Stalkkaaja

Members
  • Posts

    35
  • Joined

  • Last visited

Everything posted by Stalkkaaja

  1. Oh wow thanks, that's a step into the right direction. Can't wait for it to work in 6.11.x Btw, do you have any idea what GPUs this driver supports?
  2. Coming here to lurk for the info about this topic as well. As it's possible to mod the bios for most Pascal and Ampere cards to act as GRID-compatible, I would love to have add one card to share between multiple VMs as well.
  3. I've got this Asus NIC and it's always been plug and play with my Unraid so I don't know why it doesn't work for u, especially if the other one worked out-of-the-box. Weird.
  4. I've had 32Gb of ECC on a Ryzen platform for a couple years now and it's never went past 50% of usage unless I boot more VMs. But yea, having 16Gb is more than enough even with Plex transcoding to memory as VMs are the main culprit if you run out of memory.
  5. Docker Hub: https://hub.docker.com/r/nextcloud/all-in-one Github: https://github.com/nextcloud/all-in-one Seems like this package cannot be found in Community Apps. I haven't installed a docker from Docker Hub before but I really like this setup. Is someone willing to bring this to Community Apps or how easy is it to bring dockers from Docker Hub to my server without screwing everything up?
  6. I know I asked this earlier but never got any answer so here we go again: How can I get custom fonts working for Plex docker? I have many shows with .ass subtitles and TrueType font files to go with them but no idea where to copy them? When the custom fonts are embedded in mkv-file they work but is there a way to get them to work without modding the video file?
  7. Hey guys! How can I get custom fonts working for Plex docker? I have many shows with .ass subtitles and TrueType font files to go with them but no idea where to copy them.
  8. Hey guys! How can I get custom fonts working for Plex docker? I have many shows with .ass subtitles and TrueType font files to go with them but no idea where to copy them.
  9. Ah, ok... I thought the needed drivers could be just loaded during boot and therefore ram usage wouldn't change that much. Thanks for clarifying!
  10. Sure, building that kernel is possible in Linux VM but having a simple plugin for building that same kernel would be even better. Sadly, I have no experience on compiling in Linux... Just like I can manually do the same thing as VFIO-PCI plugin but using that plugin is simply faster, easier and much more noob friendly. What is the main reason for Unraid having to be as light as possible? I doubt anyone is running out of space on their USB sticks... But if so, having two different versions of Unraid could help as well. The normal... And the other one with tons of extra drivers.
  11. I really hope we can get a way to add our own drivers and maybe even patches to Unraid without having to build our own kernels OR maybe get a easy to use tool for building a custom kernel using Unraid GUI. This should be like a plugin system so community could add new drivers and rate them. Right now I’m running the latest stable build BUT with custom kernel(someone here in forums shared this lovely build) with patches for navi reset bug and ryzen usb patch in order to passthrough my usb chipset to Win10 VM(This was broken after I upgraded from 1700X to 3900X). But now that I finally have a working build for daily Workstation use, I can’t add any extra drivers for passing through Nvidia drivers for Plex docker(HW transcode) or DVB drivers for Plex live TV either. Maybe there is something I’m missing but in order to add those drivers, my only option is to learn how to build my own kernel? This is so old school that having a better way should be a priority I think...
  12. Thanks a lot for this great info! Might be a stupid question but is there a way to recognize the dies in Unraid GUI somehow when greating the VM? I’m currently running a 1700X but will upgrade to 3900X soon. Have you found a ”stutter free” way to give 8c/16t to a Windows 10 VM with your 3900X? I’m just wondering because I have a really poor single core performance with 1700X and hoping that this could be fixed with a newer Ryzen(or some settings) but haven’t found a up to date info. Custom Unraid with kernel 5.5.8 and Navi patch did help with RX 5700 XT reset bug but still hoping to fix the poor cpu performance somehow.
  13. What are the best settings for Ryzen 1700X on a Asus Crosshair X470 and latest bios? I’d like to move to using only VM as my daily workstation but haven’t been able to get the single core performance good enough for gaming for example. With RX 5700 XT I lose about 30-40% of it’s performance when compared to a baremetal and I think it’s mostly because of this reason. I benchmarked my CPU with Cinebench 15 and while multithreading it’s actually pretty close to a baremetal, the single core performance is really poor. So... I’ve only isolated and pinned the last cores (4/8)to a fresh Windows 10 VM using Unraid GUI and left the first cores for Unraid. What else do I have to do to improve CPU performance? I hope I could get this sorted out so I can order 3900X and really go all in.
  14. I’m running Asus X470 Crosshair VII so I’d love to have WMI working as well!
  15. I love this topic! It would be lovely to have a neat graphical bootloader start up everytime a primary gpu passthrough OS is shut down so server doesn’t have to restarted or you have to use gui seperately... We also need the new Kernel that supports Ryzen/RX 5700 XT the best. Maybe this should become a real feature to Unraid for us that use Unraid as both, their server and workstation.
  16. I have the same problem... Can't wait for someone to share his wisdom.
  17. Thanks a lot for the info! I really wish that those Navi bugs will be fixed or maybe have a possibility to choose if you want to add a Navi patch(that works with RX 5700/XT + Windows 10 VM at least). I still have to restart my server as a normal Windows 10 PC if I want to game a bit as I'm kind of a noob and haven't been able to get this all work as planned. 😃
  18. Any news on getting an ok support for RX 5700 XT anytime soon? New beta updates are going backwards when it comes to kernel which seems quite disheartening... Has anyone actually got this GPU to really work with a Windows 10 VM and latest gpu drivers?
  19. Bus 001 Device 003:ID 2040:8265 Hauppauge dualHD So this is WinTV-dualHD, USB-tuner. I was able to use this with Plex docker after installing LibreELEC build for Unraid RC6 (and adding "--device=/dev/dvb" to the Extra Parameters in Plex docker's advanced settings view). I just bought this tuner but my problem is that it's a bit like hit and miss... I did most of my testing via Iphone app so I'm not sure if that's the reason but sometimes I could change the channel and it would tune in and start streaming after a couple seconds(I tried both, WiFi and 4G), but sometimes I could only hear voice and see only a frozen picture. I was able to record one program and it came up really nice quality(1080i, 8,2Mbps). But I'm not sure yet what settings to try and change to make this tuner work like a charm. Also I'd like to know if I'm going to buy a GTX 1660/1650 Super to make transcoding easier... Is it automatically going to be used for DVB side as well when I transcode the live channel? I wasn't able to test it for a long time, maybe one hour before I saw that Unraid had released RC7 and installed it without realizing that it would screw up my DVB plugin until the new build is released. Soooo, now I'm just patiently waiting for the update. 😃
  20. Yea got mine a couple days ago and got it working with LibreElec build. Just seems to be having trouble tuning in and start streaming sometimes.
  21. So... No one has any idea what's wrong? Is my motherboard (Gigabyte GA-Q87N) not compatible? I have enabled VT-d and virtualization in BIOS and the chipset should be compatible as well. =/
  22. Any idea, guys? Shouldn't my motherboard be compatible with passthrough? At least HVM and IOMMU are Enabled or so says Unraid. Also Q87 should not be a problem. Where should I start to troubleshoot? =/ This is my log when trying to boot the Windows 7 VM with iGPU and HD Audio: 2017-11-22 10:39:21.141+0000: starting up libvirt version: 3.8.0, qemu version: 2.10.1, hostname: unraid LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 7,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-Windows 7/master-key.aes' -machine pc-i440fx-2.9,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -m 4096 -realtime mlock=off -smp 2,sockets=1,cores=2,threads=1 -uuid 74be7cd7-cd15-e35d-9691-aad9801609ed -display none -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-Windows 7/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 -device ich9-usb-userialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device vfio-pci,host=00:02.0,id=hostdev0,bus=pci.0,addr=0x2 -device vfio-pci,host=00:03.0,id=hostdev1,bus=pci.0,addr=0x6 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on 2017-11-22 10:39:21.141+0000: Domain id=1 is tainted: high-privileges 2017-11-22 10:39:21.141+0000: Domain id=1 is tainted: host-cpu 2017-11-22T10:39:21.189552Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) 2017-11-22T10:39:21.653874Z qemu-system-x86_64: -device vfio-pci,host=00:02.0,id=hostdev0,bus=pci.0,addr=0x2: Failed to mmap 0000:00:02.0 BAR 2. Performance may be slow 2017-11-22T10:39:39.407473Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x0, 0xaa55aa55,4) failed: Device or resource busy 2017-11-22T10:39:39.407496Z qemu-system-x86_64: vfio_region_read(0000:00:02.0:region2+0x0, 4) failed: Device or resource busy 2017-11-22T10:39:40.188394Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x0, 0xaa55aa55,4) failed: Device or resource busy 2017-11-22T10:39:40.188468Z qemu-system-x86_64: vfio_region_read(0000:00:02.0:region2+0x0, 4) failed: Device or resource busy PS. I was actually able to login to this VM using DVI-out and usb keyboard+mouse but the iGPU was not there and the resolution was 800x600 with 8bit color or something disgusting. After RDP'ing to it, I still could not even see the Intel HD 4600 in device manager and for HD Audio device there was "This device cannot start (Code 10)". Anyways... The ultimate goal would be to be able to run this VM headless and always RDP into it.
  23. Help me out guys, please =) Here is my syslinux: default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot label unRAID OS GUI Mode kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot,/bzroot-gui label unRAID OS Safe Mode (no plugins, no GUI) kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot unraidsafemode label unRAID OS GUI Safe Mode (no plugins) kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest And here are my groups after ACS override: IOMMU group 0: [8086:0c00] 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) IOMMU group 1: [8086:0412] 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) IOMMU group 2: [8086:0c0c] 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) IOMMU group 3: [8086:8c31] 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) IOMMU group 4: [8086:8c3a] 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) [8086:8c3d] 00:16.3 Serial controller: Intel Corporation 8 Series/C220 Series Chipset Family KT Controller (rev 04) IOMMU group 5: [8086:153a] 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 05) IOMMU group 6: [8086:8c2d] 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) IOMMU group 7: [8086:8c20] 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) IOMMU group 8: [8086:8c26] 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) IOMMU group 9: [8086:8c4e] 00:1f.0 ISA bridge: Intel Corporation Q87 Express LPC Controller (rev 05) [8086:8c02] 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) [8086:8c22] 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) I have tried multiple different VM options. Win 7(SeaBios) and Windows 10(SeaBios and OVMF), but none of them work. With OVMF Windows 10 I was actually able to connect to it via RDP with the only problem being that I could not get the Intel HD 4600 to work. Win10 VM with SeaBios is the most crazy one. This is the log after I try to boot it: 2017-11-20 15:12:56.641+0000: Domain id=7 is tainted: high-privileges 2017-11-20 15:12:56.641+0000: Domain id=7 is tainted: host-cpu 2017-11-20T15:12:56.687714Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) 2017-11-20T15:12:57.151444Z qemu-system-x86_64: -device vfio-pci,host=00:02.0,id=hostdev0,bus=pci.0,addr=0x2: Failed to mmap 0000:00:02.0 BAR 2. Performance may be slow 2017-11-20T15:13:13.478899Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0xfe5c000, 0x0,1) failed: Device or resource busy 2017-11-20T15:13:13.478926Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0xfe5c001, 0x0,1) failed: Device or resource busy 2017-11-20T15:13:13.478934Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0xfe5c002, 0x0,1) failed: Device or resource busy 2017-11-20T15:13:13.478948Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0xfe5c003, 0x4,1) failed: Device or resource busy 2017-11-20T15:13:13.478955Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0xfe5c004, 0xc000000,4) failed: Device or resource busy 2017-11-20T15:13:13.478959Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0xfe5c008, 0x30413109,4) failed: Device or resource busy 2017-11-20T15:13:13.478967Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0xfe5c00c, 0x0,1) failed: Device or resource busy 2017-11-20T15:13:13.478975Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0xfe5c00d, 0x0,1) failed: Device or resource busy 2017-11-20T15:13:13.478984Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0xfe5c00e, 0x0,1) failed: Device or resource busy 2017-11-20T15:13:13.478990Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0xfe5c00f, 0x0,1) failed: Device or resource busy 2017-11-20T15:13:13.478996Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0xfe5c010, 0x1,1) failed: Device or resource busy 2017-11-20T15:13:13.479002Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0xfe5c011, 0x0,1) failed: Device or resource busy 2017-11-20T15:13:13.479011Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0xfe5c012, 0x0,1) failed: Device or resource busy 2017-11-20T15:13:13.479019Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0xfe5c013, 0x4,1) failed: Device or resource busy 2017-11-20T15:13:13.479038Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0xfe5c014, 0x0,1) failed: Device or resource busy 2017-11-20T15:13:13.479048Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0xfe5c015, 0x0,1) failed: Device or resource busy 2017-11-20T15:13:13.479054Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0xfe5c016, 0x0,1) failed: Device or resource busy . . . etc... Sooo... Should I modify my syslinux somehow or something?