All of lore.kernel.org
 help / color / mirror / Atom feed
From: Reeted <reeted@shiftmail.org>
To: qemu-devel@nongnu.org, libvir-list@redhat.com
Subject: [Qemu-devel] Virtual serial logging server?
Date: Sun, 06 Nov 2011 17:21:39 +0100	[thread overview]
Message-ID: <4EB6B413.8000002@shiftmail.org> (raw)

Dear all,
please excuse the almost-OT question,

I see various possibilities in quemu-kvm and libvirt for sending virtual 
serial port data to files, sockets, pipes, etc on the host.
In particular, the TCP socket seems interesting.

Can you suggest a server application to receive all such TCP connections 
and log serial data for many virtual machines at once?

In particular I would be interested in something with quotas, i.e. 
something that deletes old lines from the logs of a certain VM when the 
filesystem space occupied by the serial logs of such VM gets over a 
certain amount of space. So that the log space for other VMs is not 
starved in case one of them loops.

Thank you
R.

             reply	other threads:[~2011-11-06 16:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-06 16:21 Reeted [this message]
2011-11-06 17:07 ` [Qemu-devel] Virtual serial logging server? Mulyadi Santosa

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=4EB6B413.8000002@shiftmail.org \
    --to=reeted@shiftmail.org \
    --cc=libvir-list@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 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.