From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Eamon Walsh <ewalsh@tycho.nsa.gov>
Cc: George Coker <gscoker@tycho.nsa.gov>,
Xen-devel <xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Fbdev graphics broken in xen/next dom0
Date: Fri, 12 Mar 2010 13:42:49 -0800 [thread overview]
Message-ID: <4B9AB559.1070709@goop.org> (raw)
In-Reply-To: <4B9AA301.6090303@tycho.nsa.gov>
On 03/12/2010 12:24 PM, Eamon Walsh wrote:
> I work in the same group as Dave Quigley and George Coker. I'm working
> on a graphical switcher application for Xen which uses the DirectFB
> library on top of Linux VESA fbdev. This runs in dom0 at the moment.
> I'm using the latest xen/next pvops dom0 and xen-unstable hypervisor
> compiled from source, with vga=ask so I can boot dom0 in a graphical mode.
>
> The problem I'm having is illustrated by the attached test program that
> displays a green background with a white square for 10 seconds when run
> as root. It doesn't work on the xen/next / xen-unstable combo. The
> program runs and exits normally but all I see is a black screen.
>
> The program *does* work on xen/next running on the bare metal. It also
> works using the xen-unstable hypervisor with an older dom0, the 2.6.31.4
> kernel with Novell patches. So I think the issue is in the xen/next
> kernel. I've run the test program on different machines and observed
> the same behavior.
>
> The xen-unstable / 2.6.31.4 dom0 combination works and I'm using that
> for the moment but I'd like to be using pvops. I would be happy to run
> more tests / provide more data if needed.
>
What's the hardware? Do any messages appear either on the dom0 console
or the Xen console? Does booting with a vga console help?
Thanks,
J
next prev parent reply other threads:[~2010-03-12 21:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 20:24 Fbdev graphics broken in xen/next dom0 Eamon Walsh
2010-03-12 21:42 ` Jeremy Fitzhardinge [this message]
2010-03-13 0:44 ` Eamon Walsh
2010-03-13 0:51 ` Jeremy Fitzhardinge
2010-03-16 0:46 ` Konrad Rzeszutek Wilk
2010-03-16 21:52 ` Eamon Walsh
2010-03-16 22:19 ` Konrad Rzeszutek Wilk
2010-03-25 23:55 ` Eamon Walsh
2010-03-27 9:14 ` Arvind R
2010-03-27 21:52 ` Jeremy Fitzhardinge
2010-03-28 9:33 ` Arvind R
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=4B9AB559.1070709@goop.org \
--to=jeremy@goop.org \
--cc=ewalsh@tycho.nsa.gov \
--cc=gscoker@tycho.nsa.gov \
--cc=konrad.wilk@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).