All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qcow2: make cache=unsafe usable
Date: Wed, 07 Sep 2011 13:07:41 +0300	[thread overview]
Message-ID: <4E67426D.1040702@redhat.com> (raw)
In-Reply-To: <4E673FC6.60007@redhat.com>

On 09/07/2011 12:56 PM, Kevin Wolf wrote:
> Am 07.09.2011 11:24, schrieb Avi Kivity:
> >  Currently cache=unsafe is unsafe to the point of unusability - the
> >  caches are never written to disk except on exit so anything except
> >  an orderly exit -- including live migration -- leaves the disk image
> >  corrupted.
> >
> >  Fix by interpreting flush requests and doing everything except flushing
> >  the underlying file.  The contents of the metadata cache are transferred
> >  to the host pagecache, so that qemu aborts keep the disk in a consistent
> >  state, and live migration (on the same host, or if using a coherent
> >  filesystem) works.
> >
> >  Signed-off-by: Avi Kivity<avi@redhat.com>
> >  ---
> >
> >  Untested - is this the right approach?
>
> Hm, could work, even though I don't like it very much. The alternative
> approach would be something like this

I think that your version is better - it fixes all the layered format 
drivers at once (even though qcow2 is the only one that needs fixing).

-- 
error compiling committee.c: too many arguments to function

      reply	other threads:[~2011-09-07 10:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-07  9:24 [Qemu-devel] [PATCH] qcow2: make cache=unsafe usable Avi Kivity
2011-09-07  9:47 ` Alexander Graf
2011-09-07  9:56 ` Kevin Wolf
2011-09-07 10:07   ` Avi Kivity [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=4E67426D.1040702@redhat.com \
    --to=avi@redhat.com \
    --cc=kwolf@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.