[Kernel-packages] [Bug 1771238] Re: Not able to passthrough > 32 PCIe devices to a KVM Guest

2018-05-15 Thread  Christian Ehrhardt 
At least for the DPC protection it seems more a kernel issue in regard to PCIe handling than anything else for now. Due to that I'm adding a task for the kernel as well. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you

[Kernel-packages] [Bug 1771238] Re: Not able to passthrough > 32 PCIe devices to a KVM Guest

2018-05-16 Thread Andy Whitcroft
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771238 Title: Not able to passthrough > 32 PCIe devices to a KVM Gues

[Kernel-packages] [Bug 1771238] Re: Not able to passthrough > 32 PCIe devices to a KVM Guest

2018-05-17 Thread Alex Williamson
Agreed with the initial analysis, there's nothing in device assignment to limit to 32 devices except where downstream distros have intentionally added a limit for support purposes. The issue here is that the host hit a PCIe Downstream Port Containment uncorrectable error, apparently causing at lea

[Kernel-packages] [Bug 1771238] Re: Not able to passthrough > 32 PCIe devices to a KVM Guest

2018-06-06 Thread  Christian Ehrhardt 
Thanks Alex for cross checking. I got handed a seabios change that was mentioned to make this work. I'll clean it up and build/test on my own. Once I have a good feeling I'll submit an RFC upstream for review and set you on CC. -- You received this bug notification because you are a member of Ke

[Kernel-packages] [Bug 1771238] Re: Not able to passthrough > 32 PCIe devices to a KVM Guest

2018-06-11 Thread  Christian Ehrhardt 
I got access to such a machine and successfully added >32 cards via hotplug as well as statically in the initial guest xml of libvirt. I face maybe related issue around "accel/kvm/kvm-all.c:952: kvm_irqchip_commit_routes: Assertion `ret == 0' failed." now but noting seems like the old DPC issue.