qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] qemu and qemu.git -> Migration + disk stress introduces


From: Anthony Liguori
Subject: Re: [Qemu-devel] qemu and qemu.git -> Migration + disk stress introduces qcow2 corruptions
Date: Sat, 12 Nov 2011 07:30:40 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.21) Gecko/20110831 Lightning/1.0b2 Thunderbird/3.1.13

On 11/12/2011 04:20 AM, Avi Kivity wrote:
On 11/10/2011 07:54 PM, Anthony Liguori wrote:
IMO, this should be a release blocker.  qemu 1.0 only supporting
migration on enterprise storage?


No, this is not going to block the release.

You can't dump patches on the ML during -rc for an issue that has been
understood for well over a year simply because it's release time.

If this was so important, it should have been fixed a year ago in the
proper way.

Nor can you yank support for migration this way.  Might as well put a
big sign on 1.0, "Do Not Use This Release".

You're joking, right?

Let's be very clear. Live migration works perfectly fine when you use raw images and coherent shared storage.

NFS is *not* fully coherent so in order to do live migration with NFS, you have to use cache=none.

Live migration does not work with image formats. There's not a simple way to make it support image files. So far, no one has put the work into making it support image files.


Making formal plans and sticking to them is great, but not to the point
of ignoring reality.

Why do you think this is an end of the world feature?

Regards,

Anthony Liguori




reply via email to

[Prev in Thread] Current Thread [Next in Thread]