Re: [Qemu-devel] [PATCH v3] Stop VM on ENOSPC error.

[Vincent Hanquez <tab@snarc.org>]

On Mon, Jan 19, 2009 at 05:22:04PM +0000, Ian Jackson wrote:
> The theoretical reason is that a guest is in a better postion to deal
> with the situation because it knows its access patterns.  Often the
> response to a failing write in a mission-critical system will be some
> kind a fallback behaviour, which is likely to work.  Stopping the VM
> unconditionally is not something that the guest can cope with.

The guest isn't in a better position to do something here.
In a first place, the guest see a "hardware" disk of size X, that the
host is providing. the host need to do what is necessary to provide it
(or at least try to). the guest has absolutely no idea about the fact
this harddisk isn't a true harddisk or that it should be treated
specially (expecting ENOSPC at any point).

> 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.

That's *your* opinion. as long as there's a mechanism to notify the
management part, so that it can try to do something, pausing the VM
seems sensible to me.

-- 
Vincent