qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: lvivier@redhat.com, qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block: Fix -incoming with snapshot=on
Date: Mon, 22 Feb 2016 10:11:20 +0100	[thread overview]
Message-ID: <20160222091120.GB5387@noname.str.redhat.com> (raw)
In-Reply-To: <56C73EE9.1040909@redhat.com>

Am 19.02.2016 um 17:12 hat Paolo Bonzini geschrieben:
> 
> 
> On 19/02/2016 16:52, Kevin Wolf wrote:
> > The BDRV_O_INACTIVE flag should only be set for images explicitly opened
> > by the user. snapshot=on needs to create a new qcow2 image and write
> > some metadata to it. This is not a problem because it can't come from
> > the source, so there's no reason to mark it as BDRV_O_INACTIVE, even
> > though it is opened while waiting for the migration to complete.
> > 
> > This fixes an assertion failure when -incoming and snapshot=on are
> > combined.
> > 
> > Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> 
> Does this also fix "migrate -b"?

No, that still fails for me. I think 'migrate -b' needs to clear
BDRV_O_INACTIVE before it starts using the image on the destination. I
wonder how it ever worked without this, it should have thrown all of the
metadata caches away instead of writing them to the image.

Kevin

      reply	other threads:[~2016-02-22  9:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19 15:52 [Qemu-devel] [PATCH] block: Fix -incoming with snapshot=on Kevin Wolf
2016-02-19 16:12 ` Paolo Bonzini
2016-02-22  9:11   ` Kevin Wolf [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=20160222091120.GB5387@noname.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).