On Mon, Dec 08, 2014 at 09:48:12AM +, Daniel P. Berrange wrote:
> 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
>
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 wa
On Fri, Dec 05, 2014 at 11:09:02PM +0100, Paolo Bonzini wrote:
> I think so. Should it reopen stdout/stderr too?
Thanks for the feedback I'm gald it's something that isn't a clearly terrible
idea.
I don't think that's required for my use case, but it's not all about me. If
that's something pe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/12/2014 22:35, 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.
>
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 b
