Jump to content

tjb_altf4

Members
 View Profile  See their activity

  • Posts

    1,430

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Everything posted by tjb_altf4

  1. tjb_altf4
    Try 5.0, instead of 5.1. One of my Windows VMs black screens on 5.1, but is happy on 5.0
  2. tjb_altf4
    I'm guessing because CA pulls dockerhub stats (not just unraid) and FoxxMD is using the official image.
  3. tjb_altf4
    Try update the machine type to the latest (or even second latest version). My VMs with a GTX 1060 passed to it work fine in 6.9.2
  4. tjb_altf4
    shims appear are when you enable "Host access to custom networks" in docker settings
  5. tjb_altf4
    Off topic slightly, but wow if accurate https://www.tomshardware.com/news/nvidia-gpu-virtualization-unlocked-on-client-gpus
  6. tjb_altf4
    Changed Status to Solved
  7. tjb_altf4
    They didn't lock it, they just refused to fix a bug (hardware reset) that made pass-through unusable. As soon as the community started to build working fixes, AMD's next generation didn't have these issues, but the fixes weren't backported to previous gen. I should also note these hardware reset problems have never appeared in AMD's professional GPU lineup (Quadro competitors), funny that.
  8. tjb_altf4
    Changed Status to Solved
  9. tjb_altf4
    Changed Status to Closed
  10. tjb_altf4
    Fixed since upgrading to 6.9.2
  11. tjb_altf4
    The option now needs to be enabled in CA settings to be visible, however using the "Add container" button on the docker screen is actually an easier method (that I later discovered).
  12. tjb_altf4
    Memory ballooning is disabled once you pass through a physical device.
  13. tjb_altf4
    Has been fixed in 6.9.1
  14. tjb_altf4
    Changed Status to Closed
  15. tjb_altf4
    There's a bunch of factors that can cause this, nearly all are Microsofts doing. Read through this thread, it has all the known fixes. https://forums.unraid.net/topic/89452-windows-issues-with-unraid/?do=findComment&comment=959725
  16. tjb_altf4
    Switch to Advanced View using the View toggle in the top right
  17. tjb_altf4
    I don't think its drivers, I looked up his motherboard specs and it has the standard intel 1GbE LAN, which should be ok. Assuming a static IP has been set, there will be a routing conflict in the switch where 2 MAC address (old and new system) resolve to the same IP address. Power cycling the network equipment is an easy way to rule this out, as this clears the ARP cache.
  18. tjb_altf4
    Try power cycling your network equipment, and if you set a DHCP reservation in your router make sure its updated for the MAC of your new system.
  19. tjb_altf4
    Left click on them, there should be a context menu that pops up with the option to remove.
  20. tjb_altf4
    Can this be setup as an isolated network without breaking anything? i.e. does this network still need internet access for UnraidOS, docker & plugin (github) updates?
  21. tjb_altf4
    Hopefully this opens up the possibility of SR-IOV at a later date
  22. tjb_altf4
    You shouldn't need a proxy address if you have the vpn enabled. In my system, proxy setting is set to none The reason it no longer works is due to tightening of networking rules in the docker for better security, I would look at the stickied FAQ post if you want to retain the proxy.
  23. tjb_altf4
    Great plugin! this will be very useful
  24. tjb_altf4
    The main riser component and cables are the same for the 4x4 and 2x8 kits, so you should be able to mix parts (which they also sell) to get a x8x4x4 setup.
  25. tjb_altf4
    Expected as mentioned in the release notes that 6.9.0+ would result in reset SMART configuration settings, This should be a one off reset, and was needed to allow management of SMART configurations for multi-pool and UD disks. https://wiki.unraid.net/Unraid_OS_6.9.0#SMART_handling_and_Storage_Threshold_Warnings
×
×
  • Create New...