sturmstar

Members
  • Posts

    38
  • Joined

  • Last visited

Everything posted by sturmstar

  1. hmm... you could try to disable "bonding" by setting "enable bonding" to "no" - because you only have one bonding-member (eth0) - so there is no benefit in enable bonding?! i just saw it - you don't have the "bridging members" - certainly because of enabled "bonding" ... i really would try that! ...maybe this makes a difference?! and after that a reboot...
  2. From your screenshot I see that you have indeed NO 'br0' network. That's the reason why the VM fails. WHY you don't have no 'br0' is the other question... my network looks like this:
  3. It's working with this link for me - thanks
  4. Hi - had the same problem. I did solve it with this command in ssh: So - reboot isn't neccessary.
  5. Hi - I get the following error:
  6. Hi everyone. Just for info - at last - I have tested the latest GIGABYTE Bios F50a for my x470 board - and (with ACS downstream enabled) I can use GPU Passthrough for all of my cards (two) without Error 127 It took over half a year (from F6 to F50a) - but they finally fixed the bug. So I can now finally use Unraid without Kernel Patch AND a newer Bios version as F6... Thanks again for the Kernel Patch - it did fulfill its purpose until now I don't need it anymore 🙂 Bye!
  7. Hi everyone. Just for info - at last - I have tested the latest GIGABYTE Bios F50a for my x470 board - and (with ACS downstream enabled) I can use GPU Passthrough for all of my cards (two) without Error 127 It took over half a year (from F6 to F50a) - but they finally fixed the bug. So I can now finally use Unraid without Kernel Patch AND a newer Bios version as F6... Bye!
  8. I have already tested if the gpu bug is fixed with the default kernel ... nope, still not working in 6.8 RC1
  9. Hey. 6.8 RC1 is out - with lots of bug fixes. Are you going to build a kernel for this version? Best regards and thanks
  10. Some people claim that the bug was resolved with their latest bios versions. In my case it wasn't resolved with it. I have a Gigabyte Aourus x470 gaming with latest bios f42d - but the bug remained, I couldn't start a single VM with Gpu passthrough. After using the custom kernel it works. So in your case I would simply try if it works out of the box with latest bios. If it doesn't work you can still try and use the custom kernel.
  11. Today I had time to test the newest Bios which is available for my x470 gigabyte board - still the pci vfio bug bug. But then I tried your custom kernel - and with ACS Override downstream enabled - it works like a charm! Thank you so much. Seems now I depend on your custom kernels until this is fixed from unraid-side - because I don't think there will be any further changes in the bioses... So - please keep up the good work - and I hope you provide us with these versions until it is not needed anymore. Thanks again and best regards!
  12. Hi! Do I have to replace the Kernel or is it possible to rename them - and add it to the Unraid startmenu? Thanks ... never done this before, that's why I'm asking
  13. Very strange... this is exactly my setup too. Which GPU do you use for booting / unraid - before it gets assigned to a vm? Because I have to change my primary GPU in UEFi to 2nd Pcie because this is my smaller Card (1050ti) So unraid starts up with this gpu in legacy and auto starts the first vm with this assigned gpu (GPU bios was necessary) The second Gpu (first pcie) is a 1070 which I can assign freely without need for a gpu bios. This setup works perfectly with f6 hmm... I don't get it
  14. Did you alter any settings in Bios or inside Unraid ... like vm settings? Do you boot unraid in UEFI or legacy mode?
  15. Yes, after the second attempt to start the VMs - first attempt is stuck in D3
  16. I can't confirm - at least with my setup - it's a Gigabyte X470 Board and I have two Nvidia GPUs, neither is working with 1.0.0.3ABB - I had to go back to F6
  17. I just tested it. It still doesn't work with F42a. 😭 Same problems and errors Going Back to f6 again
  18. F42a for Gigabyte with AGESA 1.0.0.3ABB is out - rumors says that the issue with VFIO is finally fixed. Perhaps I'm able to test this tommorow
  19. F41b for Gigabyte Boards (with AGESA 1.0.0.3AB) is out ... I'm not able to test this version until the next couple of days ... maybe someone else can test ...
  20. I had / have exactly this problem. I also have the Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING-CF - currently with F6 Bios Version. Until F6 everything is working fine. Since F30 (also F31 and F40) there is exactly this "VM Unknown PCI header type '127'" error with my Nvidia Cards. I hope there will be another update after F40 - and I hope these bugs will be resolved because it would be a shame if I couldn't upgrade to Ryzen3 because of buggy bios-updates.