From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=49455 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PGkXd-00072p-2G for qemu-devel@nongnu.org; Thu, 11 Nov 2010 22:43:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PGkXX-000165-FS for qemu-devel@nongnu.org; Thu, 11 Nov 2010 22:43:08 -0500 Received: from vms173011pub.verizon.net ([206.46.173.11]:37695) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PGkXX-00015z-Ai for qemu-devel@nongnu.org; Thu, 11 Nov 2010 22:43:03 -0500 Received: from server ([unknown] [71.170.86.183]) by vms173011.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LBR00KIJ6B46B60@vms173011.mailsrvcs.net> for qemu-devel@nongnu.org; Thu, 11 Nov 2010 21:42:41 -0600 (CST) From: Date: Thu, 11 Nov 2010 21:42:36 -0600 Message-id: <1289533356158143500@rkmorris.us> In-reply-to: <4CDC5D75.2040500@mail.berlios.de> References: <1289454632425616500@rkmorris.us> <4CDC2666.5000705@cisco.com> <1289507845918233500@rkmorris.us> <4CDC5D75.2040500@mail.berlios.de> Subject: Re: [Qemu-devel] Log Console Output to File MIME-version: 1.0 Content-type: multipart/alternative; boundary="===axigen=1698118036052280435251613298716990245820=axigen===" List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Weil Cc: qemu-devel@nongnu.org, "David S. Ahern" This is a MIME message. You may need a MIME compliant mail user agent. --===axigen=1698118036052280435251613298716990245820=axigen=== Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, Yes, this works, as does adding in "-vnc :0" (and then connection to this v= ia VNC) ... but in both cases I am not able to collect the console output t= hat exists during the boot. Any thoughts on that? Thanks! On Thu, Nov 11, 2010 03:17 PM, Stefan Weil wrote: > Am 11.11.2010 21:37, schrieb Russell Morris: > > Hi, > > > > Thanks for the pointer! I tried this, but I get an error message, as=20 > > follows ... > > *chardev: opening backent "stdio" failed* > > *qemu: could not open serial device 'stdio': Inappropriate ioctl for=20 > > device.* > > > > Thoughts?=20 >=20 > Hi, >=20 > I assume that you tried this (as it was suggested by an earlier mail): >=20 > qemu -serial stdio -nographic ... >=20 > This results in an error message for me, too: >=20 > chardev: opening backend "stdio" failed > qemu: could not open serial device 'stdio': No such file or directory >=20 > Try this variant (which works for me): >=20 > qemu -nographic ... >=20 > It will redirect the serial output (first serial port) of your guest os t= o > standard output, so you can write it to a file with the usual methods, > for example this one: >=20 > qemu -nographic ... | tee log.txt >=20 > Regards >=20 > Stefan Weil >=20 > --===axigen=1698118036052280435251613298716990245820=axigen=== Content-Type: text/html Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi,

Yes, this works, as does adding in "-vnc :0" (and then co= nnection to this via VNC) ... but in both cases I am not able to collect th= e console output that exists during the boot. Any thoughts on that?

= Thanks!



On Thu, Nov 11, 2010 03:17 =  PM, Stefan Weil <weil@mail.berlios.de> wrote:
Am = 11.11.2010 21:37, schrieb Russell Morris:
> Hi,
>
> Thank= s for the pointer! I tried this, but I get an error message, as
> fo= llows ...
> *chardev: opening backent "stdio" failed*
> *qemu: = could not open serial device 'stdio': Inappropriate ioctl for
> devi= ce.*
>
> Thoughts?

Hi,

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

qemu -serial stdio -no= graphic ...

This results in an error message for me, too:

cha= rdev: 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 writ= e it to a file with the usual methods,
for example this one:

qemu= -nographic ... | tee log.txt

Regards

Stefan Weil

--===axigen=1698118036052280435251613298716990245820=axigen===--