From: "Ben Taylor" <bentaylor.solx86@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Scrolling console output
Date: Wed, 2 Apr 2008 12:07:17 -0400 [thread overview]
Message-ID: <cef699d70804020907p2735969dv3ee3bf6aff267457@mail.gmail.com> (raw)
In-Reply-To: <2122f0920804020858s172f620cp3d4bde7f57569be4@mail.gmail.com>
On Wed, Apr 2, 2008 at 11:58 AM, Girish V <girish.xen@gmail.com> wrote:
> Hello,
>
> I am having the same question as asked in this thread
> http://lists.gnu.org/archive/html/qemu-devel/2008-03/msg00399.html
>
> I am trying to debug why my kernel crashes during the boot process. But
> some of the error messages scroll of the target console, before I can see
> what is happening.
Given the fact that it crashes, I might be inclined to actually make the
console a real serial port, one of the virtual serial ports so you could
use a scrolling terminal to catch all the output. Once you get the problem
fixed, then you can go back to the sdl console.
prev parent reply other threads:[~2008-04-02 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 15:58 [Qemu-devel] Scrolling console output Girish V
2008-04-02 16:07 ` Ben Taylor [this message]
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=cef699d70804020907p2735969dv3ee3bf6aff267457@mail.gmail.com \
--to=bentaylor.solx86@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).