From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Providing a mechanism to reopen() file based chardevs
Date: Mon, 8 Dec 2014 09:48:12 +0000 [thread overview]
Message-ID: <20141208094812.GA29159@redhat.com> (raw)
In-Reply-To: <20141205213518.GD84915@thor.bakeyournoodle.com>
On Sat, Dec 06, 2014 at 08:35:19AM +1100, Tony Breeds wrote:
> Hi All,
> Openstcak (Nova) has had an issue for a longish time where a running
> instance (qemu via libvirt) which has a file based console can fill the disk of
> the hypervisor causing all guests to stall.
>
> I'm looking at ways to fix this. Clearly it can be done in openstack wothout
> changing qemu but it seems to be that a better idea would be to teach qemu to
> reopen() these files when it recieves a sighup and/or something in the monitor.
My long term desired approach to deal with this problem in OpenStack (and
other libvirt based mgmt apps) is to have a separate log daemon in libvirt
eg a virtlogd daemon. Take QEMU out of the business of writing to files
entirely and instead it would always just be a given a pipe FD which is
connected to the daemon. This avoidis the need to give QEMU permission to
open files at all, which is inline with our general security strategy for
host resources QEMU accesses.
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 :|
next prev parent reply other threads:[~2014-12-08 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 21:35 [Qemu-devel] Providing a mechanism to reopen() file based chardevs Tony Breeds
2014-12-05 22:09 ` Paolo Bonzini
2014-12-06 4:32 ` Tony Breeds
2014-12-08 9:48 ` Daniel P. Berrange [this message]
2014-12-09 1:30 ` Tony Breeds
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=20141208094812.GA29159@redhat.com \
--to=berrange@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).