From: "Michael A. Collins" <mike@ark-net.org>
To: "Sven Köhler" <sven.koehler@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: Xen 4.1 PVOPS 3.0.0-RC1 VGA Console
Date: Sat, 04 Jun 2011 08:28:56 -0400 [thread overview]
Message-ID: <40d6b174ce7e2dd32db9d903efca80da@mail.ark-net.org> (raw)
In-Reply-To: <isd2on$7sj$1@dough.gmane.org>
On Sat, 04 Jun 2011 12:55:57 +0200, Sven Köhler
<sven.koehler@gmail.com> wrote:
> Am 04.06.2011 06:41, schrieb mike.a.collins:
>> I've noticed that the VGA console is still not fixed in the 3.0.0
>> kernel
>> when booting with xen dom0. Is there a patch like with 2.6.39? I
>> could
>> probably take what I used with the 2.6.39, but I was wondering if
>> there
>> was a reason for not including it. Thanks.
>
> What have you been using for 2.6.39?
>
> Also, I'd love to hear an explanation why it is necessary, or what I
> have to look out for on the mailing list or the LKML in order to
> follow
> the progress with regard to this issue.
>
From what I've been able to gather there has been a change in the way
that Xen handles the host's hardware, in particular the console
hardware. It was not sending that to the bootloader correctly, or at
all, and so the kernel didn't see that there was a console. That is
what I can tell, just my uninformed opinion. Konrad has a patch that
fixes the way that Xen reports the console hardware to the kernel, but
it looks as if it didn't make it into the 3.0-rc1 release. I just went
to git.kernel.org and pulled up Konrad's xen repository and selected the
stable/2.6.39.x and looked for the commit entitled "xen: allow enable
use of VGA console on dom0" which was on May 31st. I clicked on the
commitdiff page and then downloaded the patch from the link at the top
of the generated page. I used that patch to enable the VGA console on
my dom0, worked like a champ, but I don't know if there is an issue that
kept it from being commited in the mainline. I hope this helped.
Mike
> The problem (blank screen) pops up regularly in the xen-user list
> too.
> Also the wiki page about pvops dom0 doesn't mention this issue.
> (If I could edit that page, I would add the necessary information to
> it.
> Unfortunatly, I don't really know what the problem is, and what the
> solution might be.)
>
>
> Regards,
> Sven
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-06-04 12:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 4:41 Xen 4.1 PVOPS 3.0.0-RC1 VGA Console mike.a.collins
2011-06-04 10:55 ` Sven Köhler
2011-06-04 12:24 ` Pasi Kärkkäinen
2011-06-04 12:28 ` Michael A. Collins [this message]
2011-06-04 12:32 ` mike.a.collins
2011-06-04 13:01 ` Sven Köhler
2011-06-04 14:00 ` Sven Köhler
2011-06-06 8:28 ` Ian Campbell
2011-06-06 14:00 ` Konrad Rzeszutek Wilk
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=40d6b174ce7e2dd32db9d903efca80da@mail.ark-net.org \
--to=mike@ark-net.org \
--cc=sven.koehler@gmail.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).