[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [migration] questions about removing the old block-migr
|
From: |
Stefan Hajnoczi |
|
Subject: |
Re: [Qemu-devel] [migration] questions about removing the old block-migration code |
|
Date: |
Tue, 5 Nov 2013 14:34:12 +0100 |
|
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Sun, Nov 03, 2013 at 04:01:36AM +0000, Zhanghaoyu (A) wrote:
> I read below words on the report of <KVM Live Migration: Weather forecast
> (May 29, 2013)>,
> We were going to remove the old block-migration code
> Then people fixed it
> Good: it works now
> Bad: We have to maintain both
> It uses the same port than migration
> You need to migrate all/none of block devices
>
> The old block-migration code said above is that in block-migration.c?
Yes.
> What are the reasons of removing the old block-migration code? Buggy
> implementation? Or need to migrate all/none of block devices?
Buggy and tightly coupled with the live migration code, making it hard
to modify either area independently.
> What's the substitutional method? drive_mirror?
drive_mirror over NBD is an alternative. There are security and
integration challenges with those approaches but libvirt has added
drive-mirror block migration support.
Stefan