From: "David S. Ahern" <daahern@cisco.com>
To: Russell Morris <rmorris@rkmorris.us>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Log Console Output to File
Date: Thu, 11 Nov 2010 13:43:25 -0700 [thread overview]
Message-ID: <4CDC556D.60207@cisco.com> (raw)
In-Reply-To: <1289507845918233500@rkmorris.us>
On 11/11/10 13:37, Russell Morris wrote:
> Hi,
>
>
>
> Thanks for the pointer! I tried this, but I get an error message, as
> follows ...
>
> *chardev: opening backent "stdio" failed*
>
> *qemu: could not open serial device 'stdio': Inappropriate ioctl for
> device.*
qemu command line?
David
>
>
>
> Thoughts?
>
>
>
> Thanks again!
>
>
>
> On Thu, Nov 11, 2010 11:22 AM, "David S. Ahern" <daahern@cisco.com> wrote:
>
> On 11/11/10 09:57, Mulyadi Santosa wrote:
> > On Thu, Nov 11, 2010 at 12:50, <qemu@rkmorris.us
> <mailto:qemu@rkmorris.us>> wrote:
> >> Hi,
> >>
> >> Is there a way to log / copy the console output (like the Linux
> boot info, if booting QEMU to Linux) to a file?
> >
> > I think you could consider booting Linux in serial console...then
> > start Qemu with -nographic. From there, everything will be spilled
> > right in your standart output. Then you can use your favourite method
> > to save the output...let's say using "script" command.
> >
>
> I use 'screen' and its logging capability (Ctrl-a H). Launch the VM with
> '-serial stdio -nographic' and have the guest console directed to ttyS0
> (console=ttyS0 kernel arg).
>
> David
next prev parent reply other threads:[~2010-11-11 20:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 5:50 [Qemu-devel] Log Console Output to File qemu
2010-11-11 16:57 ` Mulyadi Santosa
2010-11-11 17:22 ` David S. Ahern
2010-11-11 20:37 ` Russell Morris
2010-11-11 20:43 ` David S. Ahern [this message]
2010-11-12 3:40 ` qemu
2010-11-11 21:17 ` Stefan Weil
2010-11-11 21:57 ` David S. Ahern
2010-11-12 3:42 ` qemu
2010-11-13 14:39 ` qemu
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=4CDC556D.60207@cisco.com \
--to=daahern@cisco.com \
--cc=qemu-devel@nongnu.org \
--cc=rmorris@rkmorris.us \
/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.