-
Yet another GPU passthrough thread..
So I thought it may just be the VM so I installed a fresh copy of Win11, set up VNC server after creating an account, shut it down and switched from virtual to the GPU. Still get a black screen connecting through VNC, and still have no signal on the monitor. The log does show this new error though, and I haven't found anything on google about it. Disregard them being on a different bus, I already fixed that. syslog shows this however: Mar 28 03:03:30 dNAS kernel: vfio-pci 0000:01:00.0: vfio_ecap_init: hiding ecap 0x1e@0x258 Mar 28 03:03:30 dNAS kernel: vfio-pci 0000:01:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 Mar 28 03:03:30 dNAS kernel: vfio-pci 0000:01:00.0: vfio_ecap_init: hiding ecap 0x26@0xc1c Mar 28 03:03:30 dNAS kernel: vfio-pci 0000:01:00.0: vfio_ecap_init: hiding ecap 0x27@0xd00 Mar 28 03:03:30 dNAS kernel: vfio-pci 0000:01:00.0: vfio_ecap_init: hiding ecap 0x25@0xe00 Mar 28 03:03:30 dNAS kernel: vfio-pci 0000:01:00.1: vfio_ecap_init: hiding ecap 0x25@0x160 *edit* Holy cowwww. OKAY! So I changed the machine from i440fx to q35, changed cdrom bus to SATA, removed the vbios, and passed a keyboard through. I have no idea which option fixed it (I changed to q35 before and had no success) but I'm able to keep the virtual gpu and add my physical card as a second gpu. I'm able to connect using VNC, monitor shows output, and most of all I'm able to connect using moonlight and play N64 games through retroarch.
-
Yet another GPU passthrough thread..
Okay, so I ran through everything again. I did notice that going to Main -> Flash -> SysLinux in the webGUI did not output what is saved in my syslinux.cfg, so I added the same lines there. Rebooted and started the VM. If I connect through VNC as soon as it begins booting, I can see the desktop load, but then the VNC connection freezes. So it seems something (most likely a driver) loading at startup is causing the remote view to mess up. I've gone into device manager and uninstalled the nvidia drivers for the 4060 and rebooted, but still have the same issue. I read disabling UEFI may help, so I did that and rebooted the server, still did not help..
-
Valr started following Can't change directory date modified and Yet another GPU passthrough thread..
-
Yet another GPU passthrough thread..
I've got a WIndows 10 VM which I'm trying to do a GPU passthrough. I installed vnc server before switching from the virtual vnc graphics to my GPU so I could still connect after. Upon turning the VM on, VNC connects but it is a black screen. I plugged in a monitor to the GPU, and it also has no connection. RDC connects fine. I am trying to set this up so devices on my network can connect to the VM and play roms on Retroarch using Sunshine/Moonlight. Using the vnc virtual graphics card it worked flawless, clients were able to connect and play games. The issue is that I need opengl to play N64 games, which upon lots of reading I need to do a GPU passthrough. But whatever is causing the black screens when the VM is running with only the GPU is also causing Moonlight to be unable to connect. I can select "Desktop" in the Moonlight options, but it also just gives a black screen. Selecting Retroarch throws an error about rtsp timeout. I have tried a downloaded vbios and removed the header myself, and I also used SpaceInvaderOne's vbios dump script to create my own. Don't see a difference using either one of them. tl;dr GPU passthrough enabled - black screen on vnc and monitor, cannot connect using Moonlight app. RDC still works. Need to make it so VNC and monitor are no longer black screens, which will probably solve my moonlight issue. Thank you!! VM log: VM xml: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='7'> <name>Windows 10</name> <uuid>847d5471-eeb6-764e-c429-aef66e7bc611</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>6291456</memory> <currentMemory unit='KiB'>6291456</currentMemory> <memoryBacking> <nosharepages/> <source type='memfd'/> <access mode='shared'/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='5'/> <vcpupin vcpu='6' cpuset='6'/> <vcpupin vcpu='7' cpuset='7'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-7.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/847d5471-eeb6-764e-c429-aef66e7bc611_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <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' migratable='on'> <topology sockets='1' dies='1' cores='8' threads='1'/> <cache mode='passthrough'/> </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='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10/vdisk1.img' index='2'/> <backingStore/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.262-2.iso' index='1'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <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> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </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='pci' index='1' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='1'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' 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'/> </binary> <source dir='/mnt/user/roms/romm/'/> <target dir='roms'/> <alias name='fs0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='52:54:00:f1:df:32'/> <source bridge='br0'/> <target dev='vnet6'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <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 10/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/isos/Asus.RTX4060Ti.8192.2303291.rom'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x06' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x06' function='0x1'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> syslinux.cfg:
-
File Manager "Move" function erased data?
I had two large torrents saved to /mnt/cache/Data and used the move function instead of copy to move the folder over to /mnt/user/media/Video/TV. File manager acted like it was moving both folders, but the transfer box suddenly disappeared around 80%, and it no longer said it was moving anything at the bottom of the page. I went and checked my share, both folders are in the TV share, but only one folder has files. The second folder has 0 files, 0 folders, 0 bytes. Neither torrents are still in /mnt/cache/Data. Nothing in the main unraid log about the transfer. I'm at a loss. *edit* I noticed I received a warning during the transfer stating my cache drive became hot (49c), could that have affected it?
-
Can't change directory date modified
Thank you but unfortunately that did not work.. I run touch -m -t "201712032212.48" "/mnt/user/media/Video/TV/the last man on earth" touch -m -t "201712032212.48" "/mnt/user/media/Video/TV/the\ last\ man\ on\ earth" sync but the directory still has the date it was copied drwxrwxrwx 1 nobody users 6 Jan 17 13:29 the\ last\ man\ on\ earth/
-
Can't change directory date modified
This is kind of a niche problem I'm having. I run all my media through kodi (i just don't like how plex looks). Been running kodi for years now with a mysql database set up so each tv in the house is connected to the same db. I have my kodi sources sorted as date modified, so newest movies and show episodes are at the top of the list ready to be scraped. Now my huuuuuge problem. I just transferred 20tb over to my new unraid server. Issue? It has changed the date modified on all of my media to the date it was transferred over, so now movies and shows that I downloaded years ago are now at the top. Doing some google searching I found out if I had used a windows cmd "robocopy" it would have kept the original date modified for every folder. I just spent a week transferring all of my data. I do NOT want to have to delete everything and start over. Talking with chatgpt, it made me a few different scripts in both autoit and python that would change directory date modified to one of the video files inside the directory. It worked great!....for some of the folders. About 20% of the folders went back to the original dates. If I have any folders like /TV/Showname/Season1/episode.mkv the Season1 folder will get its date updated, but the main directory won't. But the majority of my shows are just set up like /TV/Showname/episode.mkv and the date did not change. I went through permissions, ownerships, making sure the folders are not read-only, manually inputting the touch and sync commands. Nothing seems to work. It then said two possible reasons were that noatime or +i (immutable) were set on my shares. It gave me two commands to test for these, noatime is definitely set but i cannot use the "chattr" command, it throws an error so I cannot check for immutable. If noatime or +i were the issue, how come some of the directories did change their date modified? What am I missing to this puzzle to reset the rest of my folders? I've been at this for 6 hours now trying to figure it out and it's killing me.
-
Cache drive question
Thanks guys for the reply. I grabbed a 2th nvme for cache. Just waiting on my mobo to come in the mail then I can begin building 😬
-
Cache drive question
Hello everyone! For years I've used two 8tb external hdds connected to a spare laptop running Linux as a "nas." My storage has almost run out, so I bit the bullet and purchased hardware to build an actual nas. I plan to install unraid onto it. Currently I have 8 10tb hdds coming in the mail, I will set 2 parity drives and the rest array. The guide I followed did not mention anything about a cache drive, I had no idea about this until I began reading more about unraid. A reddit post says this Write speed to the array is slower than max gb seeds due to calculations etc. Many use a cache as the landing zone for incoming data, it writes to the cache for a cache enabled share then nightly (or on schedule) the data moves from the cache to the array. So this means that if I include a cache drive, all data is written on the cache. My issue is that I want to transfer my 14tb of data to the nas when I set it up. Does this mean i can only transfer whatever size the cache drive is and then wait for unraid to move it to the array? Also, every thing I read about the cache drive people say to use an ssd. I have a spare 2tb sata mechanical drive. How much would that impact my transfer speeds if I used that compared to an ssd? Thank you all
Valr
Members
-
Joined
-
Last visited