Vidamus

Members
  • Posts

    14
  • Joined

  • Last visited

Vidamus's Achievements

Noob

Noob (1/14)

0

Reputation

  1. This thread was helpful to me for getting my first USB controller passed through. All of my USB controllers were on the same device ID even though they were in 2 different IOMMU groups, but using that "xen-pciback.hide" directive I was able to isolate the 2 buses in one IOMMU group from the 6 other busses in the other group, and was then able to successfully add that group the VM using the XML examples given here. Many thanks
  2. I got it working! Hooray!! The last piece of the puzzle was that I had to hex edit the vbios and remove the nVidia header. I found this in a Spaceinvader One video. Now that I have the vBIOS file right, (and also the multifunction group) it works on both i440fx and Q35 machines. Thanks again for all the help!
  3. Thanks again for sucvh a detailed and helpful post @ghost82! I tried the following steps: Created a new Q35 machine VM using similar settings to the existing i440fx vm I now have 2 VMs called "i440fx" and "Q35" respectively Used GPU-Z to dump the current vBIOS from both of my video cards. I updated the vBIOS for both VMs to use the dumped vBIOS In the XML of both VMs I: Added all 4 devices related to the video card to VM config set multifunction='on' for the primary video card device set bus and slot the same on the 3 other video card devices set function to a different, incrementing number on each device I then tried starting each VM, the Q35 first. Unfortunately in each case the video card still does not initialise and I have to "force stop" the VM to get it to shut down. After attempting to start both, and the force stopping each one, I then took a new diagnostics report which I have attached. Many thanks for your time in helping me with this. It's a lot more complicated than it appears. tower-diagnostics-20220122-1020.zip
  4. I have now also tried using the GTX 1050, in the 3rd slot (not the boot default), with the vBIOS file provided, on both Q35 and i440fx machines. I still can't get the VM to initialise a graphics card in any case.
  5. I still cannot get the graphics card to initialise. I have updated the motherboard BIOS to the latest version downloaded the latest vBIOS for the video card from TechPowerup, put it on the array, and specified the file location in the VM config I tried creating a another VM with machine Q35-5.1 (all other settings the same) But I still get the same result that the video card is not initialised when the VM starts. The latest diagnostics are attached. Regarding what slot the card is in, if I cannot get the GTX 1660 Super working in slot 1 then I'd rather buy new hardware. The whole purpose of this project was to install Unraid while still b eing able to use this machine as a Windows 10 media workstation with native performance. So I am not interested in running the primary video card in a 4x socket just to get it to work. tower-diagnostics-20220121-1409.zip
  6. Thanks @ghost82, that was a very useful post! You were right, it was not hanging on boot, the video merely freezes after VFIO binding as you said. My router assigned a different IP after reboot and I'd not realised it yet. I misinterpreted the frozen screen and inaccessible web interface as a crash. I now have the GTX 1660 Super (all 4 devices) bound to VFIO on boot. Now when I start the VM, the "frozen" boot log display switches to a black screen but then goes no further. Actually it's not quite a "black" screen, my monitor reports that there is no video output signal and goes to sleep. So I am now working my way through this guide here: https://wiki.unraid.net/Manual/VM_Management#Help.21_I_can_start_my_VM_with_a_GPU_assigned_but_all_I_get_is_a_black_screen_on_my_monitor.21 If/when I get stuck again I will post a new diagnostic report.
  7. My current concern is that IF: the Motherboard does not allow to me choose the boot graphics device AND The motherboard always selects the card in PCIe slot 1 as the boot graphics device (Which is the only x16 slot) AND I cannot bind the default boot graphics device to VFIO THEN: That means that it is impossible to passthrough any graphics card on the x16 slot on this Motherboard. Is that correct, or are there other things I can try here?
  8. Hi All, I am trying to turn my Video Editing PC into an Unraid server with Windows installed into a VM with hardware graphics pass through. The primary purpose of this machine is to be both a NAS and a Video Editing Workstation. The key idea being that all my source footage and video projects are safely stored on a redundant NAS, but at the same time my Video Editing Workstation has "local machine" access to the files because it's running on the same hardware. The machine specs are: MSI MPG X570 Gaming Edge Wifi Motherboard AMD Ryzen 7 3700X 32Gb DDR4 2133Mhz MSI nVidia GTX 1660 Super nVidia GTX 1050 Ti (brand escapes me right now) Parity 1: WD Red Pro 16Tb Data 1: WD Red Pro 16Tb Cache: Seagate Firecuda 1Tb Unassigned: Gigabyte Aorus 1Tb SSD (my existing Windows install) So far I have successfully configured and started the the Array as above and I am trying to get a Windows 10 VM going for the first time. Note that I am not trying to import the existing Win 10 install, I am starting from scratch. I am having trouble trying to understand how to properly setup the Graphics Cards for GPU passthrough. I wanted to use the GTX 1660 Super in the PCI-e Slot 1 for GPU passthrough and the GTX 1050 Ti for Unraid or perhaps other VMs in future. When I assign the GPU to the VM and try to start it, I get an "Execution Error". After some digging around I got a hunch (still haven't found docs on this yet) that the thing to do to fix this might be to use Tools -> System Devices to "Bind Selected to VFIO at Boot". However, every time I select the GTX 1660 super here and bind it to VFIO at boot, Unraid then hangs on boot and I have to delete /config/vfio-pci.cfg to get it to boot again. After further digging around, my next hunch was that I can't bind the default boot graphics card to VFIO at boot, and the GTX 1660 is the default boot card. So I went to the BIOS to see if I could select a different boot GFX device but I can't see any BIOS settings relating to this anywhere. I don't think the BIOS allows it. Where can I go from here? Am I on the right path? I am open to buying new hardware if I have to, but I want to make sure I have exhausted all my options with this hardware first. Thanks in advance for any guidance anyone can offer. Cheers
  9. I am using this page here: https://wiki.unraid.net/Manual/VM_Management#Configure_a_Network_Bridge After enabling bridging in the Network Settings, it then says to set the default bridge in the VM Settings page. But there is no "VM Settings page". So I take a guess and go to the "VM Manager" settings page because that's the only one that has "VM" in the name, but on this page there is only "Enable VMs" and "Default Winsows VirtIO driver ISO" settings. I can't find any other settings panels relating to VM settings anywhere.
  10. I am still struggling with this. I am trying to configure a VM, but again the documentation is describing settings pages that don't seem to exist in my Unraid interface and so I am stuck trying to set up my VM network with incorrect docs because I can't find the settings mentioned anywhere in the interface. I don't expect this to be fixed here in this thread or anything like that, I'm just giving feedback that this is a poor experience for the first time user.
  11. @Squid My apologies, you are correct. I had seen the wording "Stable Release" and somehow got the concept of LTS Release in my head. I misspoke, please read "Latest Stable" everywhere I wrote LTS. As you said though, my points still stand. As a new user, when I go to the download page and it says that 6.9.2 is the latest stable release, that does create an expectation that this is the recommended release for new users, and is therefore also likely to be the most well supported release. In the context of this thread, your advice "It's always advised to keep your server up to date" seems to imply that 6.9.2 is not the version I should be installing and that I would be better off starting with 6.10. If that is case, then the Download and Getting Started pages should be updated to reflect this. When I see a version promoted as "Latest Stable" I assume that all versions after that are experimental, and only intended for advanced users. @klepel Thanks, that is helpful, I'll have a look around in the wiki for info on setting the license too. I can see though that the wiki also doesn't support documentation versioning. That page you linked is only useful to me because it hasn't been updated in 2 years, not because it has been preserved as historical documentation for 6.9. It does have a page history, but that page history isn't linked to Unraid versions. All this leads me to the assumption that the wiki is a disorganised patchwork of documentation contributed across many versions of Unraid. My point about the lack of historical documentation archive still stands. For the record, I am not here to say that Lime Tech or Unraid is morally reprehensible for not doing better on these points. I do like what Lime Tech is doing with Unraid and I'd love to see this project get more attention. The new user experience is very important to adoption and therefore success of Unraid in the long term. We each only get one, real opportunity to fully understand what it is like to be a new user, and so I think it's important to share feedback about the new user experience during my only real opportunity to do so. Thanks for your replies.
  12. Hi All, I wish my first post as a new Unraid user was not negative feedback, but here we are... The title pretty much says it all. The current "Getting Started" Guide in the docs looks very different in some places to the current LTS Stable release. For clarity, I am referring to the documentation found here: https://wiki.unraid.net/Articles/Getting_Started Specifically, Step 4 "Setting a root password", and 4.1 "Registering and Installing Your Key". The screenshots and steps shown are very different to what I see when setting up a new Unraid server using the 6.9.2 LTS release. So different in fact, that it seems that the GUI/Features described in the docs do not exist at all in 6.9.2, which seems to make it impossible to adapt the guide for 6.9.2. Furthermore, there seems to be no method for accessing old versions of the docs. It appears that the current Getting Started guide has been written for version 6.10, so I was hoping to be able to view an older 6.9.x version of this page, but I cannot find any reference to old docs anywhere. Surely "Long Term Support" Current Stable Release means continuous access to documentation for that version through-out the LTS period? However the Unraid documentation site seems not to support versioning at all. I am hoping someone can show me that I am wrong, and that there is a Docs archive somewhere for 6.9.x releases. Thanks