From: Jamie Lokier <jamie@shareable.org>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Stop VM on ENOSPC error
Date: Wed, 14 Jan 2009 16:46:17 +0000 [thread overview]
Message-ID: <20090114164617.GB6431@shareable.org> (raw)
In-Reply-To: <20090114121147.GI24995@redhat.com>
Daniel P. Berrange wrote:
> Thus I'd suggest we need an async notification of this event,
> and only enable this behaviour if the app controlling QEMU has
> explicitly enabled this notification / feature.
I think the behaviour should always be enabled (unless explicitly
disabled, but I'm not sure why you'd want to do that).
A corrupt VM with data loss sounds much worse than a stopped VM to me.
If the VM is in some critical server role, you probably have a
watchdog or something pinging it anyway, same as real hardware.
-- Jamie
next prev parent reply other threads:[~2009-01-14 16:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 12:03 [Qemu-devel] [PATCH] Stop VM on ENOSPC error Gleb Natapov
2009-01-14 12:11 ` Daniel P. Berrange
2009-01-14 12:20 ` Dor Laor
2009-01-14 13:52 ` Gleb Natapov
2009-01-14 14:28 ` Kevin Wolf
2009-01-14 16:46 ` Jamie Lokier [this message]
2009-01-14 17:30 ` Daniel P. Berrange
2009-01-14 18:29 ` Anthony Liguori
2009-01-14 18:37 ` Jamie Lokier
2009-01-14 16:47 ` Jamie Lokier
2009-01-14 17:01 ` Gleb Natapov
2009-01-14 18:39 ` Jamie Lokier
2009-01-14 19:24 ` Gleb Natapov
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=20090114164617.GB6431@shareable.org \
--to=jamie@shareable.org \
--cc=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).