All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: deshantm@gmail.com, xen-devel@lists.xensource.com,
	Andrew Lyon <andrew.lyon@gmail.com>
Subject: Re: pv_ops dom0 and kernel console output problem
Date: Wed, 31 Dec 2008 09:44:52 +1100	[thread overview]
Message-ID: <495AA464.6080501@goop.org> (raw)
In-Reply-To: <20081230150331.GF15052@edu.joroinen.fi>

Pasi Kärkkäinen wrote:
> Reading pv_ops wiki page I noticed this:
>
> "If the domain crashes very early, before any output appears on the console,
> then booting with: "earlyprintk=xen" should provide some useful information.
> If you are running a debug build of Xen hypervisor (set "debug = y" in
> Config.mk in the Xen source tree), then you should get crash dumps on the
> Xen console. You can view those with "xm dmesg"."
>
> So I guess earlyprintk=xen is only useful if you're running debug build of
> Xen hypervisor.. ?

earlyprintk=xen has the effect of directing the kernel's console output 
via the console output hypercall.  domU kernel's are not generally 
allowed to do this, but it is when you compile Xen in debug mode.  dom0, 
however, uses the Xen console in the normal case, so it doesn't need a 
debug Xen build.  But when Xen switches its console output to serial the 
kernel's output goes with it, so if you want it to appear on VGA you 
need to use the VGA console output (make sure your kernel has all the VT 
console options enabled).

    J

  reply	other threads:[~2008-12-30 22:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-26 11:51 pv_ops dom0 and kernel console output problem Pasi Kärkkäinen
2008-12-27 17:02 ` Pasi Kärkkäinen
2008-12-29 16:51 ` Pasi Kärkkäinen
2008-12-29 16:55   ` Todd Deshane
2008-12-29 17:02     ` Pasi Kärkkäinen
2008-12-29 17:15       ` Todd Deshane
2008-12-29 17:30         ` Pasi Kärkkäinen
2008-12-29 17:41           ` Todd Deshane
2008-12-29 17:49             ` Pasi Kärkkäinen
2008-12-29 17:55               ` Todd Deshane
2008-12-29 17:57                 ` Pasi Kärkkäinen
2008-12-30 11:02             ` Jeremy Fitzhardinge
2008-12-30 13:07               ` Pasi Kärkkäinen
2008-12-30 13:20                 ` Pasi Kärkkäinen
2008-12-30 14:18                   ` Pasi Kärkkäinen
2009-01-09 17:34                     ` Pasi Kärkkäinen
2008-12-30 15:03                   ` Pasi Kärkkäinen
2008-12-30 22:44                     ` Jeremy Fitzhardinge [this message]
2008-12-31 11:00                       ` Pasi Kärkkäinen

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=495AA464.6080501@goop.org \
    --to=jeremy@goop.org \
    --cc=andrew.lyon@gmail.com \
    --cc=deshantm@gmail.com \
    --cc=pasik@iki.fi \
    --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.