From: Jamie Lokier <jamie@shareable.org>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] [6388] Stop VM on ENOSPC error.
Date: Wed, 25 Feb 2009 18:51:48 +0000 [thread overview]
Message-ID: <20090225185148.GD16453@shareable.org> (raw)
In-Reply-To: <20090225172051.GT24969@redhat.com>
Daniel P. Berrange wrote:
> > Any objection to changing to default to enospc?
>
> >From a managment POV having QEMU change its state from running to
> paused behind our back is hard.
>From a management POV, the manager can just set the behaviour to
'report' if that's what you prefer :-)
> If we get async notifications available via the monitor, then making
> the default enospc is very sensible.
Async notifications are obviously best, but can QEMU's logging be
used? Can it log the ENOSPC event, and the management app watch the log?
-- Jamie
prev parent reply other threads:[~2009-02-25 18:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 18:59 [Qemu-devel] [6388] Stop VM on ENOSPC error Anthony Liguori
2009-02-25 16:55 ` Anthony Liguori
2009-02-25 17:04 ` Gleb Natapov
2009-02-25 17:25 ` Avi Kivity
2009-02-25 17:38 ` Jamie Lokier
2009-02-26 9:20 ` Avi Kivity
2009-02-26 9:24 ` Gleb Natapov
2009-02-25 17:34 ` Daniel P. Berrange
2009-02-25 18:31 ` Anthony Liguori
2009-02-25 18:48 ` Jamie Lokier
2009-02-25 19:29 ` Anthony Liguori
2009-02-25 18:36 ` Jamie Lokier
2009-02-25 17:11 ` Avi Kivity
2009-02-25 18:26 ` Anthony Liguori
2009-02-26 9:17 ` Avi Kivity
2009-02-25 17:20 ` Daniel P. Berrange
2009-02-25 18:08 ` [Qemu-devel] " Jan Kiszka
2009-02-25 18:27 ` [Qemu-devel] " Anthony Liguori
2009-02-25 18:51 ` Jamie Lokier [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=20090225185148.GD16453@shareable.org \
--to=jamie@shareable.org \
--cc=berrange@redhat.com \
--cc=gleb@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).