Jump to content

Warrentheo

Members
  • Content Count

    149
  • Joined

  • Last visited

Community Reputation

7 Neutral

About Warrentheo

  • Rank
    Advanced Member
  • Birthday October 5

Converted

  • Gender
    Male
  • Location
    Earth
  • Personal Text
    Currently running:

    unRaid 6.4.1 Pro License Since 02/02/2018

    Asus IX Hero with i7-7700K and 64GB RAM

    Windows 10 Gameing VM with GTX 1070 passthrough

    5HD's with m.2 Raid-0 Cache

Recent Profile Visitors

517 profile views
  1. Warrentheo

    Unraid OS version 6.7.0-rc1 available

    I read in the patch notes that: Currently I have the following on my Syslinux Configuration: kernel /bzimage append vfio-pci.ids=10de:1b81,10de:10f0 pci=noaer modprobe.blacklist=nouveau initrd=/bzroot Which passes through my nVidia card as well as blacklists it from the nouveau driver... If I am reading that correctly, everyone with passthrough will need to change these after 6.7.0 to something like: kernel /bzimage append BIND=01:00.0 pci=noaer modprobe.blacklist=nouveau initrd=/bzroot Am I reading that correctly? Or does this only affect vfio from the booted command line?
  2. Warrentheo

    Very slow boot if i allocate large amounts of ram

    I have 6.6.6 with Win10 VM and passthrough 50GB out of my 64GB to it... Have not noticed an issue with boot times once I finished tweaking the XML and Windows... I may have accidentally fixed this issue with the tweaks I have applied, but don't think so...
  3. Warrentheo

    Nearly through on GPU pass-through

    I am at a loss, are we sure the card and system works when bare metal?
  4. Warrentheo

    RTX2080 passthrough surprise

    Any issues with gaming so far?
  5. Warrentheo

    Nearly through on GPU pass-through

    Yah, try that...
  6. Warrentheo

    Difficulty creating passthrough VM

    A couple of things, I don't have AMD or Threadripper myself, but some things to keep in mind, GPU passthrough usually requires UEFI boot process... That means for the host you should not enable "Legacy Boot", since turning that on disables UEFI boot (for extra measure I even disable the "Compatibility Support Module" in my motherboard bios that even enables it to legacy boot since it just causes problems usually)... For the VM, you should use OVMF, not SeaBios to enable UEFI in the VM... And use the Q35 machine type since i440fx has to emulate the older PCI to be able to passthrough PCIe... Try those, and if that doesn't work, then we will need more details, like the Diagnostics files from the system, and the VM XML file... Edit: Also, unless you have a specific reason to have it enabled (and there may be one for AMD motherboards, don't know), you should disable the "allow_unsafe_interrupts" option you added to your boot config
  7. Warrentheo

    Issue with WX7100 passtrough

    Try following the instructions on this page: https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF to be able to add vfio_pci.ids=103c:0b0d,103c:aaf0 to your boot process for the host, then reboot... See if that helps... Edit: This should prevent the host from using them, or adding drivers for them...
  8. Warrentheo

    Issue with WX7100 passtrough

    The XML still shows that you are passing a video BIOS file, did you try booting without it? Also the Q35 Machine is preferred since i440fx can only emulate PCI, and not PCIe... I have personally encountered several issues when I first started out because I started with the default i440FX, changing to the Q35 fixed performance issues, and several software compatibility issues...
  9. Warrentheo

    Issue with WX7100 passtrough

    I am not familiar with AMD, but nVidia started encrypting their BIOS, and the connection between their BIOS and drivers a few gens back, and so they need BIOS files passed in to get the drivers to not detect a VM. My current understanding is that AMD doesn't do that, and so doesn't need a BIOS file for the GPU passed into it... Beyond that, we would need diagnostics file, and XML from the VM to help...
  10. Warrentheo

    Passthrough - direct and remote?

    Passthrough means that the card is exclusively connected to one VM, and the UnRaid host no longer has access to it... This means that it acts like any GPU would on any other computer... Without passthrough, you would boot to the UnRaid web gui interface only, then only have access to the "Remote" video card through the web browser interface... The VM would have to have fake GPU acceleration driver installed (Not accelerated by the GPU) and then sent to the VNC interface... Since your GPU horsepower never really gets used, most games wont even run, and the few that do will be unplayably slow...
  11. Warrentheo

    Having GPU/Driver issues - Windows 10 - AMD

    SeaBios should be avoided at this point, Legacy OS's only, and causes issues with GPU passthrough... Don't have an AMD myself so can't help further, looks like you have done everything I would have tried...
  12. Warrentheo

    Terrible gaming performance

    A Titan might be one of the few cards that it actually matters on since it might actually be hungry enough to saturate the bus... Most of us can only dream of having that problem from afar... 😄
  13. Warrentheo

    Windows 10 VM - Slow Network

    I'm afraid your setup is too complicated for me to make sense of personally 😞 From my reading, my current best guess is something to do with the routing in your setup... Sorry I couldn't help more...
  14. Warrentheo

    Boot options are always reset after a reboot

    Boot order is best set in the XML for the VM, and not OVMF... Or using Virt-Manager...
  15. Warrentheo

    Nearly through on GPU pass-through

    If you are sure, then it is a decent way to do it... I don't think there are many scenarios that will cause this, but it may be possible to fry your card or cause wonky issues by having a slightly off bios that doesn't line up with what is on the card... Unlikely, but still prefer to get it from the card in question...