All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Russell Morris <rmorris@rkmorris.us>
Cc: qemu-devel@nongnu.org, "David S. Ahern" <daahern@cisco.com>
Subject: Re: [Qemu-devel] Log Console Output to File
Date: Thu, 11 Nov 2010 22:17:41 +0100	[thread overview]
Message-ID: <4CDC5D75.2040500@mail.berlios.de> (raw)
In-Reply-To: <1289507845918233500@rkmorris.us>

Am 11.11.2010 21:37, schrieb Russell Morris:
> 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.*
>
> Thoughts? 

Hi,

I assume that you tried this (as it was suggested by an earlier mail):

qemu -serial stdio -nographic ...

This results in an error message for me, too:

chardev: opening backend "stdio" failed
qemu: could not open serial device 'stdio': No such file or directory

Try this variant (which works for me):

qemu -nographic ...

It will redirect the serial output (first serial port) of your guest os to
standard output, so you can write it to a file with the usual methods,
for example this one:

qemu -nographic ... | tee log.txt

Regards

Stefan Weil

  parent reply	other threads:[~2010-11-11 21:17 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
2010-11-12  3:40         ` qemu
2010-11-11 21:17       ` Stefan Weil [this message]
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=4CDC5D75.2040500@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=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.