From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Cc: Clemens Kolbitsch <clemens.kol@gmx.at>
Subject: Re: [Qemu-devel] view qemu output/console
Date: Mon, 24 Sep 2007 18:11:04 +0200 [thread overview]
Message-ID: <fb249edb0709240911l727691b9y330fea9320de2fcd@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0709241649580.28395@racer.site>
On 24/09/2007, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> On Mon, 24 Sep 2007, Clemens Kolbitsch wrote:
>
> > when the kernel crashes, it displayes the message, however as it is way
> > much more information that can be displayed in the qemu window, i only
> > see the last 20-something lines. as the crash is fatal, no entries are
> > made to the log-files and i have not succeeded redirecting output to my
> > console (using the -nographic option) as my linux does not boot
> > correctly then.
>
> If your host is not windows, you can use the "-monitor stdio" option to
> output monitor information on the console you start QEmu in.
AIUI Clemens wants to redirect the VGA console output, not QEmu
monitor. One idea is to dig out my ncurses interface patch (I believe
debian has a version that applies to post-9.0 qemu, and if you're on
debian just use the "-curses" switch), then GNU screen would let you
log all VGA console output to a file. Another idea is to set a
breakpoint at the guest printk() address.
Regards
next prev parent reply other threads:[~2007-09-24 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070921061109.16713gmx1@mx026.gmx.net>
2007-09-24 15:25 ` [Qemu-devel] view qemu output/console Clemens Kolbitsch
2007-09-24 15:50 ` Johannes Schindelin
2007-09-24 16:11 ` andrzej zaborowski [this message]
2007-09-24 16:34 ` Clemens Kolbitsch
2007-09-29 14:57 ` [Qemu-devel] qcow2 vs. image file format --> pci device Clemens Kolbitsch
2007-09-29 20:49 ` Dor Laor
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=fb249edb0709240911l727691b9y330fea9320de2fcd@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=clemens.kol@gmx.at \
--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).