[Intel-gfx] Xen is Busted

[Daniel Vetter]

On Thu, Apr 21, 2016 at 04:31:42PM +0800, Jike Song wrote:
> On 04/21/2016 06:44 AM, cacook at quantum-sci.com wrote:
> > 
> > No one will just come out and just tell us the truth, so that users can quit wasting our time trying to make your Xen work.  Your 4.2 kernel dumps core on i915, and Xen hangs on disk drive ID.
> > 
> > Why don't you just take down the Xen half of this whole thing, and stop causing so many people the loss of so much time?  It is very costly and frustrating for people to spend weeks to learn and customize a project to try and make it work, when it turns out that the underlying software is utterly broken.  Not to mention embarrassing, when we have strongly advocated this approach to our bosses and clients, and it turns out to be snakebit.
> > 
> > And on top of that you universally ignore questions on IRC and listserv, probably because you don't want to own up to the actual state of things?  What do you people think you're doing all day?  You can't, just do an occasional freeze and release a fairly stable point-release so that users can set up and learn about it?  You just leave up a busted bunch of haywires, as if you're satisfying your company's requirements?  I know, you're still getting paid no matter what.
> > 
> > So let's just agree that doing both KVM -and- Xen, is too much for you.  And/or that you've put the n00bs on Xen, who have nothing to lose.
> > 
> > I implore that you be honest, and take this junk down to just concentrate on KVM.  You can't do Xen;  you clearly can't even do its drivers.
> > 
> 
> By "4.2 kernels" are you referring to the 2015q4 release of XenGT?
> 
> If so, please at least use the proper mail list:
> 
> 	https://lists.01.org/mailman/listinfo/igvt-g
> 
> 
> intel-gfx is for "Intel graphics driver community testing & development",
> not graphics virtualization.

And in the future please cut out the flaming - it doesn't help and we
really don't appreciate that kind of style on intel-gfx here. I understand
that it's super-frustrating when things don't work, but that's no reason
to lash out.

For the actual issues, like Jike said the intel-gfx team just does the
bare metal enabling, we're not the experts for virtualization. That's a
different team, and right now most of that code isn't yet merged upstream.

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch