casperse

Thanks for the feedback! I have a Xeon E2100G and even this setup is causing problems during passthrough of the NVidia cards 😞 I am starting to consider a setup like yours with plenty of possibilities for future expansion! But NOT running Unraid as a bare-metal hypervisor (Like I always have done!) But instead run Proxmox as my hypervisor and then having all the VM's running here! (Passthrough should be much easier) And Unraid running as a virtual setup on Proxmox with HW passthrough of all the drives That way I could re-boot Unraid and keep all my VM running + the backup of VM's and snapshots would be built into Proxmox

After some more experimenting I found that this total freeze is only happening if I try to start the VM Windows 11 With the passthrough graphic card! if I remove it and select VNC the VM starts without freezing the Unraid web UI (And I don't have to SSH in and do a powerdown -r) I have also done a Bios dump of the actual card I also made sure that the card is not the one selected in the Bios I also tried a different card whit a bios dump that worked before? Then after following these changes to the XML: So finally got to the Windows 11 and I can see that the GPU is in state 43 I managed to install the Nvidia drivers (Because the card was listed) and after a reboot I am back to only have the remote display adapter Any input on how to fix this? Is it just that the card isn't supported? 3060 card

Just want to hear if you got the ROMED8-2T motherboard stable running VM's? Are you happy with this MB & CPU? - I am asking because I am in the middle of ordering the same MB as an upgrade to my stable Xeon MB

Testing different cards and Bios dumps that worked before now have it not freezing the entire Unraid but get this error message (Normally seen on AMD but I am running Xeon?) 2022-05-13T14:47:31.447653Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 -smp 8,sockets=1,dies=1,cores=4,threads=2 \ -uuid f29f275c-5941-8a32-f3de-fb21812cbab9 \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=49,server=on,wait=off \ -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-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \ -blockdev '{"driver":"file","filename":"/mnt/cache_shares/game-server/vdisk.qcow2","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"qcow2","file":"libvirt-3-storage","backing":null}' \ -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=libvirt-3-format,id=virtio-disk2,bootindex=1,write-cache=on \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/Win11_Danish_x64v1.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \ -device ide-cd,bus=ide.0,unit=0,drive=libvirt-2-format,id=ide0-0-0,bootindex=2 \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.217-1.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device ide-cd,bus=ide.0,unit=1,drive=libvirt-1-format,id=ide0-0-1 \ -netdev tap,fd=50,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:f9:6f:ba,bus=pci.0,addr=0x2 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0,index=0 \ -chardev socket,id=charchannel0,fd=48,server=on,wait=off \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -chardev 'socket,id=chrtpm,path=/run/libvirt/qemu/swtpm/6-Windows 11 GAMER-VM--swtpm.sock' \ -tpmdev emulator,id=tpm-tpm0,chardev=chrtpm \ -device tpm-tis,tpmdev=tpm-tpm0,id=tpm0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -audiodev '{"id":"audio1","driver":"none"}' \ -device vfio-pci,host=0000:01:00.0,id=hostdev0,bus=pci.0,addr=0x5,romfile=/mnt/cache_shares/game-server/Bios_dumps/ASUS_DUAL_RTX3060_12G_V2_GA104.rom \ -device vfio-pci,host=0000:01:00.1,id=hostdev1,bus=pci.0,addr=0x6 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/5 (label charserial0) 2022-05-13T14:47:31.447557Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 2022-05-13T14:47:31.447653Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 The card is selected to VFIO

I created the file: Ant when I use the IGFX it stops just before the login promt with a blinking cursor on the screen like in the video? But if I add any graphic card to the server (Dont have a free PCI slot for this) then it works! Something breaks the internal GPU when launching the UI in firefox? All the loading is shown fine on the screen

Sorry maybee stupid Q - I am a little confused 🙂 I use my P2000 Nvidia graphic card for Plex transcoding works 100% My plan was to maybe use the IGFX on a Windows 10 VM for video editing? So I think I can remove the lines with the i915 from the GO file Not sure if blacklisting the i915 will prohibit me from using it in the VM, but it shouldn't stop the P2000 transcoding should it?

I just checked my "GO file" and I found this very old setup for the GFX (Have not been a problem before, but all the updates might have broken this from the "old days") should I remove everything below the line #Setup**** root@PLEXZONE:/boot# cat /boot/config/go #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & #Setup drivers for iGPU hardware transcoding modprobe i915 chown -R nobody:users /dev/dri chmod -R 777 /dev/dri root@PLEXZONE:/boot# Yes I have created a file named i915.conf and in it I have the line: blacklist i915 I will reboot it when possible 🙂

Yes I get this no - no further problems 🙂

Thanks I will try that! UPDATE: I dont have any file in that dir? Also I would really like to clean up any old configuration like stub's! Can I just delete them ? (I can see that the stubs are for some old netcard not the IGFX!) Guess I need to keep the append.....?

Ok so after updating to RC7 I did some more testing and I found that if I change the BIOS Display output From IGFX output to my P2000 Graphic card then after showing all the boot text (See video above) I actual get to the login screen of Unraid and it works! So IGFX always worked before? - I am not using it for anything like transcoding Any idea why IGFX doesn't work anymore? Update: Testing no plugins did NOT make any difference! 😞

I have made the changes and I havnet seen any memory warning for some time, but got one today (Havent found any Emby reference) Is this just one off these things where you have to upgrade your memory 😞 Attached new Diag file diagnostics-20220508-1427.zip

I was on RC4 I am now on RC5 Do you need anymore info or additional running commands from me? :--)

But I can se that no plugin in safe mode also stops the GUI? So how to boot with GUI and not load any plugin to verify if a plugin is causing this error?

I have actually removed that before didn't do any difference? Also between it working and it stopped working no changes was made? Anyway to stop all script during boot - would safe boot do that? (Would be easy thing to check then?)

Great! Thanks - But can anyone tell me what does this mean? 😀 I have no fancy boot settings just GUI as preferred boot

So sorry My BAD I got a little freaked out and did a reboot - hoping all my data would reappear again and it did.... I am monitoring my new cache very closely. I promise to send a new Diag if it happens again

I have updated it multiple times.... also rebooted it Just tried to run it again.... And just after running it I loose my new Win 11 icon again? Not sure how to get it again last time I added a new windows 11 and just copied my XML data after making sure the docker was not running No special settings:

THANKS again! - I decided to change every path to get the better performance and everything worked great! Also updated plugins to do appdata backup etc.... so everything was running just fine and I wanted to check files on my new cache drive But this time it was EMPTY! and in my main view I had this: (This was not present when running the new cache drive at start?) Somehow my new cache drive was in both places? Afraid that I had now lost all my cache files I did a reboot and everything is back again? I upgraded to rc5 yesterday, not sure this is an error or something else?

I can now confirm that the VM icon Docker from spaceinvader did something to the windows 11 icon? Only problem now is have missing icons on all my VM's 🙂 That I got from spaceinvaders docker

Thanks trurl I found a post saying I should reboot again, but that didnt help. I then removed the new cache drive it was empty anyway, and then I started without the new cache and stopped and added it again and now its active! But I have a question , very afraid to mess up my existing Appdata on my existing cache drive! If I rename my existing cache to a new name cache_appdata and then start the Docker service! Whar will happen to all the paths that are assigned to the currunt path So its actually best and recommended to just use the default /mnt/user/appdata and set prefer Cache! And NOT like me and others to have set it manually on each docker to use the /mnt/cache/appdata - because when adding pools and renaming you have to change the paths on all dockers!

This is very strange after adding the new cache drive I have it listed as un-assigned? its the Cache_shares

Hmm the only thing related to icons is Space invaders docker? GitHub - SpaceinvaderOne/unraid_vm_icons: To download and install custom vm icons onto an Unraid server Could tha be causing the problem? Just updated to rc5 same problem (Diag below) diagnostics-20220429-2039.zip

Argh no its a black screen right after the last load on screen of the nvidia loading So somehow the login promt and the local UI resolution does not like my 4K monitor? I could see that it changed resolution while loading on the screen 1080P -> 4K (Very small text) -> back to 1080P and at the login promt black screen? Is there any setting to get this working on a 4K screen? I am now pretty sure that is the problem Diagnostic attached below diagnostics-20220426-1930.zip