From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=34677 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PGduR-0004fj-KQ for qemu-devel@nongnu.org; Thu, 11 Nov 2010 15:38:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PGduQ-0008FU-Eq for qemu-devel@nongnu.org; Thu, 11 Nov 2010 15:38:15 -0500 Received: from vms173001pub.verizon.net ([206.46.173.1]:35256) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PGduQ-0008FE-5o for qemu-devel@nongnu.org; Thu, 11 Nov 2010 15:38:14 -0500 Received: from server ([unknown] [71.170.86.183]) by vms173001.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LBQ00FTQMMJAB80@vms173001.mailsrvcs.net> for qemu-devel@nongnu.org; Thu, 11 Nov 2010 14:37:32 -0600 (CST) From: Russell Morris Date: Thu, 11 Nov 2010 14:37:25 -0600 Message-id: <1289507845918233500@rkmorris.us> In-reply-to: <4CDC2666.5000705@cisco.com> References: <1289454632425616500@rkmorris.us> <4CDC2666.5000705@cisco.com> Subject: Re: [Qemu-devel] Log Console Output to File MIME-version: 1.0 Content-type: multipart/alternative; boundary="===axigen=4487391027471540798639306530662019472985=axigen===" List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "David S. Ahern" Cc: qemu-devel@nongnu.org This is a MIME message. You may need a MIME compliant mail user agent. --===axigen=4487391027471540798639306530662019472985=axigen=== Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, =20 Thanks for the pointer! I tried this, but I get an error message, as follow= s ... chardev: opening backent "stdio" failed qemu: could not open serial device 'stdio': Inappropriate ioctl for device. =20 Thoughts? =20 Thanks again! On Thu, Nov 11, 2010 11:22 AM, "David S. Ahern" wrote: >=20 On 11/11/10 09:57, Mulyadi Santosa wrote: > > On Thu, Nov 11, 2010 at 12:50, wrote: > >> Hi, > >> > >> Is there a way to log / copy the console output (like the Linux boot i= nfo, if booting QEMU to Linux) to a file? > >=20 > > 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. > >=20 >=20 > 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=3DttyS0 kernel arg). >=20 > David > --===axigen=4487391027471540798639306530662019472985=axigen=== Content-Type: text/html Content-Transfer-Encoding: quoted-printable Content-Disposition: inline

Hi,

 

Thanks for the pointer! I tried this, but I get an error message, as fol= lows ...

chardev: opening backent "stdio" failed

qemu: could not open serial device 'stdio': Inappropriate ioctl = for device.

 

Thoughts?

 

Thanks again!



On Thu, Nov 11, 2010 11:22  AM, "D= avid S. Ahern" <daahern@cisco.com> wrote:

On 11/11/10 09:57, Mulya= di Santosa wrote:
> On Thu, Nov 11, 2010 at 12:50, <qemu@rkmorris.us> wrote:
&g= t;> 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 spi= lled
> right in your standart output. Then you can use your favourite= method
> to save the output...let's say using "script" command.
&= gt;

I use 'screen' and its logging capability (Ctrl-a H). Launch th= e VM with
'-serial stdio -nographic' and have the guest console directed= to ttyS0
(console=3DttyS0 kernel arg).

David
--===axigen=4487391027471540798639306530662019472985=axigen===--