Hi, On 2/9/19 6:37 AM, Elliott Mitchell wrote: > I'm seeing bug #810964 occur in Xen 4.8 as well. Perhaps #810964 > should be reassigned to xen-hypervisor-common or src:xen ? > > I don't know whether it effects Xen 4.11 yet...
Since the issue seems to be a lack of functionality to support certain hardware in the upstream Xen product, I would recommend to not have a bug open against Debian at all. It's not that I don't value your use case, but I just think as a package maintainer team that ships the currently released upstream software, *we* cannot be of any value to you for this, sitting in between you and upstream developers. Sometimes we can work around some things by tweaking the build scripts or other things, but I just need to be honest here about the fact that we will not be able to help you getting low level hypervisor features implemented. This means you will have to do things like hop on the upstream development mailing list, build a reproducable failure case, search for a developer that has similar hardware and wants to spend time on it, donate hardware to someone to reproduce the error scenarios or learn how to do it yourself, or whatever it takes. :) Hans