From: "Daniel P. Berrange" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC] qemu-char: add logfile facility to socket backend
Date: Thu, 17 Dec 2015 12:51:13 +0000 [thread overview]
Message-ID: <20151217125113.GG16238@redhat.com> (raw)
In-Reply-To: <5672AF5C.9080803@redhat.com>
On Thu, Dec 17, 2015 at 01:49:32PM +0100, Paolo Bonzini wrote:
>
>
> On 17/12/2015 13:02, Daniel P. Berrange wrote:
> >>> > >
> >>> > > $QEMU -chardev socket,host=localhost,port=9000,\
> >>> > > server=on,nowait,id-charserial0,\
> >>> > > logfile=/var/log/libvirt/qemu/test-serial0.log
> >>> > > -device isa-serial,chardev=charserial0,id=serial0
> >> >
> >> > Why for socket only? It would be very useful for stdio and especially vc.
> > This is just an "RFC" so didn't want to spend the time to wire
> > up all of them until I got positive feedback on the idea :-)
>
> Yes, I think it's fine. I guess one could do weird things with it such
> as connecting it to a named pipe, but we shouldn't waste time preventing it.
Great, I'll work on a properly complete patch for this then.
> > If its acceptable, then I think it could make sense to just
> > support optional "logfile" on every single backend, except "file"
>
> Yeah, I'd even wire it in qemu_chr_fe_write, and only prevent it for
> "file" at option parsing time. Or just allow it for all of them.
Yeah, doing it above the backend driver layer sounds like a nice
simple approach to making it work universally.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
prev parent reply other threads:[~2015-12-17 12:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 11:55 [Qemu-devel] [PATCH RFC] qemu-char: add logfile facility to socket backend Daniel P. Berrange
2015-12-17 12:00 ` Paolo Bonzini
2015-12-17 12:02 ` Daniel P. Berrange
2015-12-17 12:49 ` Paolo Bonzini
2015-12-17 12:51 ` Daniel P. Berrange [this message]
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=20151217125113.GG16238@redhat.com \
--to=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).