From: Gleb Natapov <gleb@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] Stop VM on ENOSPC error.
Date: Mon, 19 Jan 2009 20:41:56 +0200 [thread overview]
Message-ID: <20090119184156.GA30712@redhat.com> (raw)
In-Reply-To: <18804.46780.936806.748045@mariner.uk.xensource.com>
On Mon, Jan 19, 2009 at 05:22:04PM +0000, Ian Jackson wrote:
> But in the Xen context, a Xen VM is not a `task' in the same way.
> (Xen users make much less use of the built-in cow formats for this
> reason, often preferring LVM snapshots or even deeper storage magic.)
> We expect the VM to be up and stay up and if it can't continue it
> needs to fail or crash.
>
Even if you can add storage space dynamically with LVM you prefer VM to
crash on ENOSPC?
--
Gleb.
next prev parent reply other threads:[~2009-01-19 18:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 11:05 [Qemu-devel] [PATCH v3] Stop VM on ENOSPC error Gleb Natapov
2009-01-19 11:56 ` Ian Jackson
2009-01-19 12:16 ` Gleb Natapov
2009-01-19 16:15 ` Anthony Liguori
2009-01-19 17:22 ` Ian Jackson
2009-01-19 18:38 ` Avi Kivity
2009-01-19 18:41 ` Gleb Natapov [this message]
2009-01-20 9:25 ` Gerd Hoffmann
2009-01-20 9:35 ` Gleb Natapov
2009-01-20 10:44 ` Carl-Daniel Hailfinger
2009-01-20 11:05 ` Gleb Natapov
2009-01-20 11:35 ` Vincent Hanquez
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=20090119184156.GA30712@redhat.com \
--to=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 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.