WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] kernel mode setting

To: Michael D Labriola <mlabriol@xxxxxxxx>
Subject: Re: [Xen-devel] kernel mode setting
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Wed, 10 Feb 2010 16:00:47 -0500
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 10 Feb 2010 13:18:46 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <OF234EAB5D.9199AC80-ON852576C6.00547D95-852576C6.005698F1@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20100210151544.GI2861@xxxxxxxxxxx> <OF234EAB5D.9199AC80-ON852576C6.00547D95-852576C6.005698F1@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05)
On Wed, Feb 10, 2010 at 10:45:52AM -0500, Michael D Labriola wrote:
> Well, here's what I've done so far.  In a fit of rage aimed towards the 
> lameness of the nv driver, I cherry-picked all the drm commits from the 
> official nouveau git tree into my xen/master checkout.  And it semi-works. 
>  Baremetal it looks good for a few minutes then X gets corrupted.  Under 
> Xen 3.4.2, X locks up before anything is even painted to the screen.  If I 
> force the xorg nouveau driver to use software rendering, my system appears 
> to be perfectly stable with good 2d support.  My compiled upstream nouveau 
> tree works perfectly (although the hardware acceleration is slow).
> 
> Now, it was late at night and I was bleary eyed... and that's a TON of 
> commits to get merged in a code base I've never looked at before...  and I 
> GUESSED at which commits to apply... so I'm encouraged that anything 
> worked at all.  :-)
> 
> Now I'm trying to decide if the X lockup under Xen is my fault (mangled a 
> merge conflict, missed a commit, etc), or whether something in the 3.4.2 
> hypervisor in just plain incompatible with KMS DRM drivers.  I suppose I 
> can try getting a Xen 4.0-rc build installed and see if the behavior 
> changes...
> 
> And there's also the potential to try getting it to work under xen/next... 
> although I'm not so sure that that would be wise at this point.

It does not have the backends in yet, so you can't launch guests yet :-(

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>