qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH] bdrv_flush error handling
Date: Wed, 20 Feb 2008 16:46:04 +0000	[thread overview]
Message-ID: <200802201646.05521.paul@codesourcery.com> (raw)
In-Reply-To: <18364.22321.98451.446676@mariner.uk.xensource.com>

> Write errors for non-raw formats can easily be caused by a disk full
> situation on the host.  Killing the guest hard is unfriendly for that
> situation.

Disk full is a fundamentally unfriendly situation to be in. There is no good 
answer. Reporting errors back to the host has its own set of problems. Many 
guest OS effectively just lock up when this occurs.

Paul

  reply	other threads:[~2008-02-20 16:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 15:53 [Qemu-devel] [PATCH] bdrv_flush error handling Ian Jackson
2008-02-20 16:04 ` Daniel P. Berrange
2008-02-20 16:13   ` Ian Jackson
2008-02-20 16:19   ` Paul Brook
2008-02-20 16:23     ` Avi Kivity
2008-02-20 16:37       ` Ian Jackson
2008-02-20 16:46         ` Paul Brook [this message]
2008-02-20 16:53           ` Ian Jackson
2008-02-20 16:31             ` Jamie Lokier
2008-02-20 18:17               ` Paul Brook
2008-02-20 16:38                 ` Jamie Lokier
2008-02-20 18:22               ` Daniel P. Berrange
2008-02-20 19:01                 ` Anthony Liguori
2008-02-20 19:55                   ` Rick Vernam
2008-02-21  7:10                     ` Thomas Irlet
2008-02-21 17:19   ` Ben Taylor
2008-02-21 17:24     ` Daniel P. Berrange
2008-02-21 17:28       ` risc
2008-02-21 18:24         ` Daniel P. Berrange
2008-03-28 17:19 ` [Qemu-devel] " Ian Jackson
2008-04-26 15:15   ` andrzej zaborowski
2008-04-29 16:27     ` Ian Jackson

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=200802201646.05521.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=Ian.Jackson@eu.citrix.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).