From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Wei Liu <liuw@liuw.name>
Cc: xen-devel@lists.xensource.com,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Console is not working with 2.6.38.4 Dom0 and Xen unstable
Date: Mon, 2 May 2011 10:10:04 -0400 [thread overview]
Message-ID: <20110502141004.GC13192@dumpdata.com> (raw)
In-Reply-To: <BANLkTi=gAYXCh8ATbwRqudY_ex-FS9hQxQ@mail.gmail.com>
On Mon, May 02, 2011 at 07:31:21PM +0800, Wei Liu wrote:
> I test with various command line options, along with Konrad's [1] and
> Jeremy's [2] kernel. It's still blank.
For the Intel graphic cards to work, you need CONFIG_DMAR to be set.
Do you have that?
>
> Konrad's kernel is 2.6.39-rc4, runs well on bare metal, blank screen
> on Xen unstable.
I am 99% sure you have forgotten to set CONFIG_DMAR?
>
> Jeremy's kernel is 2.6.32.39, assertion fails with
> boot_cpu_has(X86_FEATURE_TSC_RELIABLE) when booting on Xen unstable.
>
> I also skim hvc_xen.c, the Dom0 console operations are straight
> forward -- they are just wrapper of console IO hypercall.
For that, try 'debug loglevel=8 console=hvc' on your Linux line to make sure that the output
is being piped through to the Xen hypervisor.
And on the Xen hypervisor do have 'console_to_ring'
>
> Is that a hardware-related problem?
No.
next prev parent reply other threads:[~2011-05-02 14:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 9:13 Console is not working with 2.6.38.4 Dom0 and Xen unstable Wei Liu
2011-04-30 9:59 ` Pasi Kärkkäinen
2011-04-30 10:27 ` Wei Liu
2011-04-30 10:41 ` Pasi Kärkkäinen
2011-04-30 11:17 ` Wei Liu
2011-04-30 11:40 ` Pasi Kärkkäinen
2011-05-02 11:31 ` Wei Liu
2011-05-02 13:54 ` Wei Liu
2011-05-02 14:10 ` Konrad Rzeszutek Wilk [this message]
2011-05-03 3:28 ` Wei Liu
2011-05-03 15:05 ` Konrad Rzeszutek Wilk
2011-05-04 2:31 ` Wei Liu
2011-05-03 13:21 ` Ian Campbell
2011-05-03 13:49 ` Wei Liu
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=20110502141004.GC13192@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=liuw@liuw.name \
--cc=stefano.stabellini@eu.citrix.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).