From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "John McDermott (U.S. Navy Employee)" <john.mcdermott@nrl.navy.mil>
Cc: xen-devel@lists.xensource.com
Subject: Re: X11 problem with dom0 pvops kernel on Xen 4.0.1
Date: Mon, 20 Sep 2010 17:24:08 -0400 [thread overview]
Message-ID: <20100920212408.GE26201@dumpdata.com> (raw)
In-Reply-To: <3DAD8415-73CB-4336-ABE7-1C2A44578E01@nrl.navy.mil>
> 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?
next prev parent reply other threads:[~2010-09-20 21:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 16:53 X11 problem with dom0 pvops kernel on Xen 4.0.1 John McDermott (US Navy Employee)
2010-09-20 14:48 ` Konrad Rzeszutek Wilk
2010-09-20 16:04 ` John McDermott (U.S. Navy Employee)
2010-09-20 21:24 ` Konrad Rzeszutek Wilk [this message]
2010-09-21 12:22 ` John McDermott (U.S. Navy Employee)
2010-09-21 12:29 ` Boris Derzhavets
2010-09-21 12:49 ` John McDermott (U.S. Navy Employee)
2010-09-21 13:32 ` Boris Derzhavets
2010-09-21 14:02 ` John McDermott (U.S. Navy Employee)
2010-09-21 14:58 ` Konrad Rzeszutek Wilk
2010-09-21 15:16 ` John McDermott (U.S. Navy Employee)
2010-09-22 15:21 ` John McDermott (U.S. Navy Employee)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100920212408.GE26201@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=john.mcdermott@nrl.navy.mil \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.