Re: [Qemu-devel] [PATCH v4] qemu-char: add logfile facility to all chardev backends

2016-01-15 Thread Paolo Bonzini
On 15/01/2016 10:15, Daniel P. Berrange wrote: > On Thu, Jan 14, 2016 at 09:05:03PM -0700, Eric Blake wrote: >> On 01/11/2016 05:44 AM, Daniel P. Berrange wrote: >>> Typically a UNIX guest OS will log boot messages to a serial >>> port in addition to any graphical console. An admin user >>> may a

Re: [Qemu-devel] [PATCH v4] qemu-char: add logfile facility to all chardev backends

2016-01-15 Thread Daniel P. Berrange
On Thu, Jan 14, 2016 at 09:05:03PM -0700, Eric Blake wrote: > On 01/11/2016 05:44 AM, Daniel P. Berrange wrote: > > Typically a UNIX guest OS will log boot messages to a serial > > port in addition to any graphical console. An admin user > > may also wish to use the serial port for an interactive >

Re: [Qemu-devel] [PATCH v4] qemu-char: add logfile facility to all chardev backends

2016-01-14 Thread Eric Blake
On 01/11/2016 05:44 AM, Daniel P. Berrange wrote: > Typically a UNIX guest OS will log boot messages to a serial > port in addition to any graphical console. An admin user > may also wish to use the serial port for an interactive > console. A virtualization management system may wish to > collect s

[Qemu-devel] [PATCH v4] qemu-char: add logfile facility to all chardev backends

2016-01-11 Thread Daniel P. Berrange
Typically a UNIX guest OS will log boot messages to a serial port in addition to any graphical console. An admin user may also wish to use the serial port for an interactive console. A virtualization management system may wish to collect system boot messages by logging the serial port, but also wis