From: Jeff Cody <jcody@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] iotest 194 fails on vhdx
Date: Fri, 3 Nov 2017 08:38:40 -0400 [thread overview]
Message-ID: <20171103123840.GA5399@localhost.localdomain> (raw)
In-Reply-To: <0c64b45d-3f42-7866-ffa8-b2d0a32dddb0@ozlabs.ru>
On Thu, Nov 02, 2017 at 12:19:00PM +1100, Alexey Kardashevskiy wrote:
> On 28/10/17 19:25, Paolo Bonzini wrote:
> > On 28/10/2017 08:57, Alexey Kardashevskiy wrote:
> >> On 27/10/17 18:12, Jeff Cody wrote:
> >>> VHDX does not support migration (VMDK fails the same way).
> >>
> >> Probably a very ignorant question but how can an image format not support
> >> migration at all? Is not it simple writing blocks, one-by-one? Thanks.
> >
> > VHDX does not implement bdrv_invalidate_cache. If you add that
> > callback, it can support migration.
>
>
> I could give it a try but is there a demand for it really?
>
I don't think there is much demand for it, which is why we use the
migration-blocker for it still. VHDX is a compatibility format, and as such
I don't imagine many people using it as a primary format during runtime.
prev parent reply other threads:[~2017-11-03 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 4:29 [Qemu-devel] iotest 194 fails on vhdx Alexey Kardashevskiy
2017-10-25 6:06 ` Alexey Kardashevskiy
2017-10-27 7:12 ` Jeff Cody
2017-10-28 6:57 ` Alexey Kardashevskiy
2017-10-28 8:25 ` Paolo Bonzini
2017-11-02 1:19 ` Alexey Kardashevskiy
2017-11-03 12:38 ` Jeff Cody [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=20171103123840.GA5399@localhost.localdomain \
--to=jcody@redhat.com \
--cc=aik@ozlabs.ru \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@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.