Arbadacarba

Members
  • Posts

    102
  • Joined

  • Last visited

Everything posted by Arbadacarba

  1. In a previous build I had run through the installation of "Dynamix Auto Fan Control" and "Dynamix System Temperature" and run Sensors-detect and inserted the modprobe lines into the go file: # modprobe for each sensor modprobe coretemp modprobe f71882fg modprobe lm78 modprobe nct7802 modprobe i2c-i801 # Copy the sensor.conf file for use cp boot/custom/scripts/sensors.conf /etc/sensors.d In the end I had listings on the Dashboard for 9 fans with speeds for 5 of them... I have 5 fans in the system so all seemed right in the world. * Please note I'm pulling the process from memory... So I could have missed a step. I have since completely rebuilt the server, new build of the OS, but the fans are still plugged into the same spots and it's the same motherboard (EVGA Z170 Classified K). Now I see only 3 fans, and when I run sensors-detect I see no mention of nct7802... Does anyone have any insight as to where me other 2 fans went? Or why it's not reporting any empty slots? on the Dashboard? I'm planning to use the final header on the mainboard for an additional set of fans, but would like to see the speeds they are actually running at. Thanks
  2. Living out in the country, where I have 2 internet connections because they are either unreliable, or brutally restricted: I can't use the remote access, because both of my providers are double NAT'd and unable/unwilling to pass ports through. If only there was some system in place like what is used by Teamviewer that connects my server to the Unraid system to allow me to follow it back in. I don't know nearly enough to know if that is a huge deal, or if it is a huge security issue... Just thought I'd put it out there.
  3. It's absolutely true that the file is not there... the trouble is I can't find any reference to virtio-win-0.1.160-1.iso.. Nothing should be asking for it. The VM's are all using 0.1.190. I'm a little confused... You're right I had not bound it to the VFIO before... I believe that was prior to the newest unraid version, with its easier binding, and I was manually attaching it to the VM in the xml file... I notice the system reports unknown header type as soon Is I log into the gui as opposed to waiting until after I try to run the VM... Not sure what else to try... Not sure what to do next to troubleshoot it. Arbadacarba
  4. Great podcast: I would not have guessed the topic of a server OS would make for such good listening, but it does the way you have done it. I do have a question that arose from the discussion of VFIO allow unsafe interrupts: I have a NVMe disk that looks to be misbehaving in the same way as you describe for video cards... I tried the VFIO allow unsafe interrupts switch but got no joy. NVMe Passthrough Problem (Samsung EVO 980 Pro) - VM Engine (KVM) - Unraid
  5. OK, Maybe I will ask about the other parts of that log: I have a 4 port NIC passed through to my pfSense Firewall (Cerberus) 2021-07-01 02:08:42.220+0000: 6700: warning : networkNetworkObjTaint:5292 : Network name='default' uuid=03992cfe-2f56-45e7-a079-c12c04bf2bfe is tainted: hook-script 2021-07-01 02:08:43.010+0000: 6700: warning : qemuDomainObjTaint:6075 : Domain id=1 name='pfSense - Cerberus' uuid=021a25c9-9a65-6a21-4bf6-dddf2baf2a4f is tainted: high-privileges SQUID: Means that KVM is running as root.  Perfectly normal in unRaid 2021-07-01 02:08:43.010+0000: 6700: warning : qemuDomainObjTaint:6075 : Domain id=1 name='pfSense - Cerberus' uuid=021a25c9-9a65-6a21-4bf6-dddf2baf2a4f is tainted: host-cpu SQUID: Means that you have the CPU passed through to the VM.  Perfectly normal to unRaid 2021-07-01 02:10:30.485+0000: 6688: warning : virHostdevReAttachUSBDevices:1815 : Unable to find device 000.000 in list of active USB devices 2021-07-01 02:10:30.485+0000: 6688: warning : virHostdevReAttachUSBDevices:1815 : Unable to find device 000.000 in list of active USB devices
  6. The first bit here is unrelated to my question (I am asking about it HERE) But 2021-07-01 02:08:42.220+0000: 6700: info : libvirt version: 6.5.0 2021-07-01 02:08:42.220+0000: 6700: info : hostname: Jupiter 2021-07-01 02:08:42.220+0000: 6700: warning : networkNetworkObjTaint:5292 : Network name='default' uuid=03992cfe-2f56-45e7-a079-c12c04bf2bfe is tainted: hook-script 2021-07-01 02:08:42.440+0000: 6790: error : virPCIGetHeaderType:2818 : internal error: Unknown PCI header type '127' for device '0000:03:00.0' 2021-07-01 02:08:43.010+0000: 6700: warning : qemuDomainObjTaint:6075 : Domain id=1 name='pfSense - Cerberus' uuid=021a25c9-9a65-6a21-4bf6-dddf2baf2a4f is tainted: high-privileges 2021-07-01 02:08:43.010+0000: 6700: warning : qemuDomainObjTaint:6075 : Domain id=1 name='pfSense - Cerberus' uuid=021a25c9-9a65-6a21-4bf6-dddf2baf2a4f is tainted: host-cpu 2021-07-01 02:10:30.473+0000: 6688: error : virPCIGetHeaderType:2818 : internal error: Unknown PCI header type '127' for device '0000:03:00.0' 2021-07-01 02:10:30.485+0000: 6688: warning : virHostdevReAttachUSBDevices:1815 : Unable to find device 000.000 in list of active USB devices 2021-07-01 02:10:30.485+0000: 6688: warning : virHostdevReAttachUSBDevices:1815 : Unable to find device 000.000 in list of active USB devices 2021-07-01 02:15:16.456+0000: 6687: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/Software/virtio-win-0.1.160-1.iso: No such file or directory 2021-07-01 02:15:16.456+0000: 6687: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/Software/virtio-win-0.1.160-1.iso': No such file or directory This just repeats over and over... I can't find any reference in any of my VM's to the virtio-win-0.1.160-1.iso file
  7. Libvert Log: 2021-07-01 02:08:42.220+0000: 6700: info : libvirt version: 6.5.0 2021-07-01 02:08:42.220+0000: 6700: info : hostname: Jupiter 2021-07-01 02:08:42.220+0000: 6700: warning : networkNetworkObjTaint:5292 : Network name='default' uuid=03992cfe-2f56-45e7-a079-c12c04bf2bfe is tainted: hook-script 2021-07-01 02:08:42.440+0000: 6790: error : virPCIGetHeaderType:2818 : internal error: Unknown PCI header type '127' for device '0000:03:00.0' 2021-07-01 02:08:43.010+0000: 6700: warning : qemuDomainObjTaint:6075 : Domain id=1 name='pfSense - Cerberus' uuid=021a25c9-9a65-6a21-4bf6-dddf2baf2a4f is tainted: high-privileges 2021-07-01 02:08:43.010+0000: 6700: warning : qemuDomainObjTaint:6075 : Domain id=1 name='pfSense - Cerberus' uuid=021a25c9-9a65-6a21-4bf6-dddf2baf2a4f is tainted: host-cpu 2021-07-01 02:10:30.473+0000: 6688: error : virPCIGetHeaderType:2818 : internal error: Unknown PCI header type '127' for device '0000:03:00.0' 2021-07-01 02:10:30.485+0000: 6688: warning : virHostdevReAttachUSBDevices:1815 : Unable to find device 000.000 in list of active USB devices 2021-07-01 02:10:30.485+0000: 6688: warning : virHostdevReAttachUSBDevices:1815 : Unable to find device 000.000 in list of active USB devices 2021-07-01 02:15:16.456+0000: 6687: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/Software/virtio-win-0.1.160-1.iso: No such file or directory 2021-07-01 02:15:16.456+0000: 6687: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/Software/virtio-win-0.1.160-1.iso': No such file or directory 2021-07-01 02:15:16.485+0000: 6688: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/Software/- ISOs/virtio-win-0.1.160-1.iso: No such file or directory 2021-07-01 02:15:16.485+0000: 6688: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/Software/- ISOs/virtio-win-0.1.160-1.iso': No such file or directory
  8. So I've tried with "VFIO allow unsafe interrupts:" set to yes but am getting the same results. I swapped out the 660p for the 980 Pro - There is a Server 2019 Install on the 980 Pro... Checked that it was set to passthrough in the Unassigned Devices config Page and bound to VFIO in System Devices. Same Error on startup of VM If I edit the Windows VM it displays the drive as available and checked. Here's the link to the Article about the same issue on a RedHat forum: 1542494 – VMs with NVMe devices passed through sometimes fail to be launched (redhat.com) https://bugzilla.redhat.com/show_bug.cgi?id=1542494 Any thoughts? I'm kind of stuck with this drive now. Arbadacarba
  9. Yes, I am and that could be contributing to the problem... I'll have another 980 Pro this weekend and will try it again.
  10. Could this be related to the "VFIO allow unsafe interrupts:" setting? I was listening to the Podcast today and it struck me... I was not restarting the VM... But just trying to launch it after boot... Could it have something to do with the host OS mounting the drive before restarting it for the VM?
  11. Seems to be good... The site shows me connecting through the vpn location. Seems to be working. The Goal is that while I want to lock the Torrent Server out of the more expensive internet connection, I want the unraid server itself to be able to get updates through whatever internet connection is working. Thanks for all the help.
  12. Zeroing out the LOCAL_NETWORK variable has it working correctly I think... I was just unsure if that made sense or if there could be other problems caused by that change.
  13. Does it make sense that I would need to clear the LOCAL_NETWORK: variable? I tried assigning the IP address and could not get into the WebUI. Thanks
  14. I'm trying to figure out how to get ALL transmission traffic to go through one of my internet connections rather than another. One way I do that using Policy Based Routing is that I differentiate by IP address... So that some of my VM's can only communicate through the slower but cheaper (unlimited) ISP. Is it possible to make Transmission use a different IP address than the rest of the Unraid Server? Or, Barring that is there a single outgoing port that is used? or even a range of ports? This is counter to the VPN goal isn't it? Slightly confused I know, but any insight would be appreciated. Arbadacarba
  15. It might very well be that they are formatted NTFS... I've run into this myself when trying to boot UEFI using a thumb drive and a large external USB drive... Didn't recognize the problem myself so I thought I had a bad drive. Went out and spent a fortune of a 1tb external SSD... Came back to find the same problem... Then figured out I was running an unsupported format. Reformatted the original drive fat32 and it worked fine. As a side note I now use the 1tb SSD as a Ventoy disk that - among other things - runs Acronis, to back up servers and such for conversion to VM. Ran into a problem that I couldn't get it to boot on my laptop for testing... After trying every possible option I figured out that it wouldn't boot from the USB-C / Thunderbolt port. But worked flawlessly from one of the standard USB ports. Arbadacarba
  16. Is this true for ANY hardware passed through? I've gone ahead and built a new image on the NVME drive and tried running it exactly as I have my gaming machine. Still no joy, I installed all the drivers from the virtio disk and rebooted, and... rebooted, and... Nothing. Still pulling the full 16GB continuously... Oh Well... I've ordered the 64GB kit to solve the problem that way.
  17. I guess there's always the possibility that it's a software problem with the windows install... Guess I'll make an image and do a fresh install.
  18. I've got a Windows 10 VM running from a passed through NVME drive, with a passed through GTX 1660 Ti. I use it for Gaming primarily with a few other tasks assigned when I need it. I have it connected to a HDMI monitor and it has it's own mouse and keyboard connected to it as well. I have assigne it with 2GB min and 16GB max memory. It uses 16GB from the moment it's turned on until I shut it down... I would like to juet leave it running but I'm running short of memory by the time I run a few other VM's and Dockers (Not that I'm actually encountering a problem) I've rebuilt it using Q35 (it was originally i440fx) and I've stripped out everything but the NVME pass through and I just can't get it to take anything less than 16GB... In Task Manager it claims to be using around 3GB. I've installed the drivers from the Virtio Driver disk. I've built another VM with Windows 10 and using a vdisk and it seem to work fine. Showing as using 2GB after boot. Can anyone steer me to where I've gone wrong? Is it a limitation of passing through the NVME? Thanks for any help Oh, and I'm runing 6.9.1 Arbadacarba <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='41'> <name>Win10 - Minerva</name> <uuid>8589cca6-abd8-cd49-7834-8635f9a804ba</uuid> <description>Windows 10 Gaming VM with Dedicated GTX 1660 TI</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='5'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='6'/> <vcpupin vcpu='4' cpuset='3'/> <vcpupin vcpu='5' cpuset='7'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/8589cca6-abd8-cd49-7834-8635f9a804ba_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </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' migratable='on'> <topology sockets='1' dies='1' cores='3' threads='2'/> <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> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xd'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0xe'/> <alias name='pci.8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='pci' index='9' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='9' port='0xf'/> <alias name='pci.9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x7'/> </controller> <controller type='pci' index='10' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='10' port='0x10'/> <alias name='pci.10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:60:64:6b'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/2'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/2'> <source path='/dev/pts/2'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-41-Win10 - Minerva/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> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </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='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x1f' function='0x3'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x01' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x2'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x3'/> </source> <alias name='hostdev4'/> <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <alias name='hostdev5'/> <address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> <address bus='7' device='3'/> </source> <alias name='hostdev6'/> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc539'/> <address bus='7' device='2'/> </source> <alias name='hostdev7'/> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>
  19. that's what I got when the 660P was working correctly... I've tried blocking it out by binding it to vfio... but that gives the same error followed by the difference in System Devices after I attempt to launch a VM. I've tried creating a new VM and attaching it to a VM running Acronis that I use to clone drives and which is the one that I attached the 660P to in order to clone it before I started the swap. For clarity the only VM running from the start is my pfsense router which is not configured to use the NVMe. Thanks for the input though
  20. Running Windows 10 on a passed through 512GB Intel 660P NVME drive on an EVGA Classified K Z170 board I have the opportunity to swap the 660P for a 1TB Samsung EVO 980 Pro. I know my existing board won't take full advantage of this drive but the extra size and a little future proofing never hurt… (except when it does) Unraid lets me reconfigure the VM but when I start it I get: internal error: Unknown PCI header type '127' for device '0000:03:00.0' And after that happens I don't see the drive anywhere accessible to unraid. If I reboot the machine I can see the drive in Unassigned devices and even access it… and when I look at the System Devices Page I see: But as soon as I try to launch the VM I get the error and the detail page changes to: !!! Unknown header type 7f … I spent a bitt looking around and I see lots of references to similar problems with passing GPU's through, but very little about NVMe drives. I did find this page and it seems to be about the same thing but it goes a bit over my head: 1542494 – VMs with NVMe devices passed through sometimes fail to be launched (redhat.com) Any help would be appreciated… Should I cut my losses and reinstall the 660P? Thank you I'll have to pull this drive and reinstall the 660p tonight, but I'll check back here in case anyone has any ideas or needs different info. jupiter-syslog-20210308-2108.zip syslog-10.40.70.11.zip
  21. Hahahaha I was looking in the wrong spot... Hahaha
  22. OK, so he posted that 57 minutes ago... I should check again...
  23. I'm seeing the same thing... I also can't add plugins to grafana... They seem to work with CLI but then they aren't there.. And if I try to unzip the files into the plugins folder I get an access error. From the Github: Bits and bobs The read-only paths are required for Telegraf to report on host devices. Is this what I'm running into? Arbadacarba
  24. Could we have a section of the top post defining things that need to be done before upgrading... I'm about to go from 6.8.3 to 6.9.0-RC1 and know that I need to remove and reinstall Unassigned Devices, but I also remember reading about the changes that need to be made to VM's for networking... But I don't remember what the change is...