rix

Yes of course, please refer to https://github.com/rix1337/docker-ripper/blob/master/README.md#how-do-i-set-ripper-to-do-something-else The BluRay quality by default should be equal to the content on disk, as no reencoding is done.

Before we go stable: Please take a look at the SACK exploit. https://access.redhat.com/security/vulnerabilities/tcpsack A kernel update may be advisable..

Working fine in my intel soc. Uptime 1+ day

The error in question being: Temporary failure in name resolution The script could not grab github.com. Ill try to fix the template.. Thanks for the report!

Thank you @peteknot for informing me. I have fixed the regex. The next container build should work again.

I returned my RTX 2080 and might try another brand in the future.

You guys rock. This has increased the value of my system substantially already - I can now pass through 12 of the 16 threads in my cpu without bottlenecking Plex. This has improved VM performance significantly! Can't wait for your updates - but I gladly will. Let me know if you need testers at any point.

Hey u guys - thanks for the update. I have purchased an RTX card last week and am having extremely high power draw. Would be very helpful to try if a current driver resolves this, before my return period runs out (still have a week to go). I tried running build.sh according to your git repo myself, but that file is not found. Could you perchance rebuild RC4 with the latest drivers?

Have you tried a) not stubbing the gpu (not using vfio-pci.ids in the flash config) b) not plugging in anything to the gpu c) not booting gui mode? Is power draw still high when you run unraid then? for me it is even with a, b and c If so, the issue could lie somewhere in the kernel... 😫

I have now installed UNRAID NVIDIA which installs driver version 410.78. To use this as well as disable stubbing I have booted in shell mode (not the UNRAID GUI mode). I also checked for BIOS updates - the card is up to date. The RTX 2080 is now seen by Unraid and nvidia-smi. With that I can achieve 100 W at idle, still 35 W more than previously. Also the vm works as previously. Required: Non-GUI boot Disabled Stubbing No booted VM Spun down array Before returning the GPU I would appreciate input from other RTX 2080 owners! Is your idle power consumption as high as mine? If not, I am very interested in the model you are using. My card is a "Gigabyte RTX 2080 Windforce".

For sure sounds like the same issue. I will test just booting bare-metal windows to lock this issue down to unraid itself.

True, though in IDLE both cards should consume less than 20 W: For the 1070 it was around 7-10 W My issue lies with the 2080 consuming more than 50 W in idle.

Thanks for your reply. top/htop shows my cpu in deep sleep / less than 3% usage the GPU fans spin merrily - the thing is, when stubbing the GPU it becomes invisible to UNRAID - there is no process that should use the gpu as long as the VM is not running. What google tells me, the GPUs GDDR6 might not clock down in idle, without a relatively new driver. Sadly the unraid nvidia plugin is not up to date and as long as the GPU is stubbed it will not use the driver anyway...

I have replaced my server + dedicated Gaming system setup in January and couldn't be happier. I have pinned 12 of the 16 threads in my Ryzen 2700X that are passed solely to a Windows 10 VM. Up until yesterday the system was drawing ~65 W in IDLE, which is high, but acceptable for the hardware inside my UNRAID server. That is until I replaced the GTX 1070 I was previously using with a new RTX 2080. Idle power draw has doubled to 125 W. Please be aware, that I have stubbed the entire GPU (4 specific devices: GPU, Sound, USB-C, Some additional Controller) and Gaming performance inside the Windows 10 VM is satisfactory with the 2080. Power draw is as high when I boot the server without stubbing. There is also no noticable difference between booting GUI and normal Shell mode. What I have noticed however, is that once I boot the Windows 10 VM and log out there (stopping costly background processes in Windows) the power draw goes down. I cant really measure the difference, because booting up the VM itself draws a few dozen extra W but these figures are the best I got: Running a single plex stream in a docker on my UNRAID server increases power draw from 125 W to about 150 W. Booting the VM to the Desktop increases the Draw to roughly 170 W, but logging off in Windows (still running the VM) drops power draw (still streaming Plex) to 100 W. This looks like a kernel/driver issue to me. From various reviews I can see the 20-series from NVIDIA drawing 3-5 W more than the 1070 in IDLE. Any help is appreciated, because running 24/7 this doubles my power bill. I have zero clue where the extra 60 W would be going... EDIT: To clarify: idle means only Unraid and docker containers running - array spun down.

This looks promising

Please enjoy your holidays!

I 100% support that its literally the same with my open source projects - that's why I offered time and resources to help.

As much as I support this notion having little spare time to manage myself: it's been a week. Can we help you guys build and troubleshoot an RC5 build with the latest drivers? I would gladly spin up an unraid VM and try this out if you gave me directions on the steps required.

Could you perchance help me see this up with the Handbrake container? I cannot find any nvenc option there...

<?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='7' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Windows</name> <uuid>HIDDEN</uuid> <description></description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="Nvidia.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>10</vcpu> <cputune> <vcpupin vcpu='0' cpuset='6'/> <vcpupin vcpu='1' cpuset='7'/> <vcpupin vcpu='2' cpuset='8'/> <vcpupin vcpu='3' cpuset='9'/> <vcpupin vcpu='4' cpuset='10'/> <vcpupin vcpu='5' cpuset='11'/> <vcpupin vcpu='6' cpuset='12'/> <vcpupin vcpu='7' cpuset='13'/> <vcpupin vcpu='8' cpuset='14'/> <vcpupin vcpu='9' cpuset='15'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/HIDDEN_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='10' threads='1'/> </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> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-SanDisk_SD8SN8U1T001122_161446440614'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-ST8000DM0004-1ZC11G_ZKG00C3A'/> <backingStore/> <target dev='hdd' bus='sata'/> <alias name='sata0-0-3'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='RANDOM-MAC-ADR'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 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-7-Windows/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> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2f' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2f' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x30' slot='0x00' function='0x3'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1b1c'/> <product id='0x0a14'/> <address bus='5' device='3'/> </source> <alias name='hostdev3'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x28de'/> <product id='0x1142'/> <address bus='5' device='2'/> </source> <alias name='hostdev4'/> <address type='usb' bus='0' port='3'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> <qemu:commandline> <qemu:arg value='-global'/> <qemu:arg value='pcie-root-port.speed=8'/> <qemu:arg value='-global'/> <qemu:arg value='pcie-root-port.width=16'/> </qemu:commandline> </domain> Am I doing something wrong? Still being reported as PCIE0 - I have however never experienced a significant performance drop going virtual in gaming.

Ok thanks for the clarification.

This is awesome and basically works fine. Most importantly the unraid GUI boot now goes 1440p! I cannot use this without stubbing my second GPU, though. I have assigned the 1050Ti to my plex container and the 1070 to my windows vm. Starting up windows breaks my system: hard reset required because vm and docker is not available in the web interface anymore. I would love to not stub the 1070, because with the driver it will finally stop its fans at idle, which it doesn't when stubbed. Am I wrong in assuming this would work if I were not passing through the unstubbed 1070 to anything but the windows vm?

Thanks for the reply, I will rather go with an AIO that can be entirely controlled by my mainboard's headers.

I am looking into buying an x62 cooler. Is the RGB lighting working for you in general? Have you been able to set lighting / fan speed up through usb pass through (that should not at all be harmful)?

Let me know if you find out.