From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: X11 problem with dom0 pvops kernel on Xen 4.0.1 Date: Mon, 20 Sep 2010 17:24:08 -0400 Message-ID: <20100920212408.GE26201@dumpdata.com> References: <4C866E1E.5020409@itd.nrl.navy.mil> <20100920144829.GA14537@dumpdata.com> <3DAD8415-73CB-4336-ABE7-1C2A44578E01@nrl.navy.mil> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <3DAD8415-73CB-4336-ABE7-1C2A44578E01@nrl.navy.mil> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "John McDermott (U.S. Navy Employee)" Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > The kernels boot fine, including video, as dom0. In fact, running as dom0, they forward X11 no problem. When I install an F13 image as a pvops domU, the domU cannot start X. I agree that sounds like an attempt to pass-through is somehow screwing things up, but I have not configured the guest for pass through. Ok, so your problems have nothing to do with DRM/KMS nor X if you see X working as Dom0 on your machine. You don't need those nopat, nomodeset options - those are only needed if you can't get X working under Dom0 and we need to troubleshoot what is happening. > > Is there a known-good F13 image I could try to install, in case the one I am trying is somehow wrong for this? Well, the normal F13 works for me.. but maybe I am installing it differently than you. What does 'lspci -vvv' and 'dmesg' show you under you DomU? And also can you attach the 'Xorg.0.log' from DomU?