Arbadacarba

Members
  • Content Count

    100
  • Joined

  • Last visited

Community Reputation

10 Good

About Arbadacarba

  • Rank
    Member
  • Birthday 10/10/1974

Converted

  • Gender
    Male
  • Location
    Canada

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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
  2. 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
  3. 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
  4. 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 :
  5. 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-6a2
  6. 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 l
  7. Yes, I am and that could be contributing to the problem... I'll have another 980 Pro this weekend and will try it again.
  8. 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?
  9. 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.
  10. 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.
  11. 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
  12. 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 co
  13. 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.
  14. 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.
  15. 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.