From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49707) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YvgRa-0000w4-LT for qemu-devel@nongnu.org; Fri, 22 May 2015 02:28:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YvgRW-0007oI-H7 for qemu-devel@nongnu.org; Fri, 22 May 2015 02:28:30 -0400 Received: from szxga03-in.huawei.com ([119.145.14.66]:21903) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YvgRV-0007o1-K7 for qemu-devel@nongnu.org; Fri, 22 May 2015 02:28:26 -0400 Message-ID: <555ECC26.9050607@huawei.com> Date: Fri, 22 May 2015 14:26:46 +0800 From: zhanghailiang MIME-Version: 1.0 References: <1432196001-10352-1-git-send-email-zhang.zhanghailiang@huawei.com> <20150521113007.GH2129@work-vm> In-Reply-To: <20150521113007.GH2129@work-vm> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH COLO-Frame v5 00/29] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Dr. David Alan Gilbert" Cc: lizhijian@cn.fujitsu.com, quintela@redhat.com, yunhong.jiang@intel.com, eddie.dong@intel.com, peter.huangpeng@huawei.com, qemu-devel@nongnu.org, arei.gonglei@huawei.com, netfilter-devel@vger.kernel.org, amit.shah@redhat.com, david@gibson.dropbear.id.au On 2015/5/21 19:30, Dr. David Alan Gilbert wrote: > * zhanghailiang (zhang.zhanghailiang@huawei.com) wrote: >> This is the 5th version of COLO, here is only COLO frame part, include: VM checkpoint, >> failover, proxy API, block replication API, not include block replication. >> The block part has been sent by wencongyang: >> "[Qemu-devel] [PATCH COLO-Block v5 00/15] Block replication for continuous checkpoints" >> >> we have finished some new features and optimization on COLO (As a development branch in github), >> but for easy of review, it is better to keep it simple now, so we will not add too much new >> codes into this frame patch set before it been totally reviewed. >> >> You can get the latest integrated qemu colo patches from github (Include Block part): >> https://github.com/coloft/qemu/commits/colo-v1.2-basic >> https://github.com/coloft/qemu/commits/colo-v1.2-developing (more features) >> >> Please NOTE the difference between these two branch. >> colo-v1.2-basic is exactly same with this patch series, which has basic features of COLO. >> Compared with colo-v1.2-basic, colo-v1.2-developing has some optimization in the >> process of checkpoint, including: >> 1) separate ram and device save/load process to reduce size of extra memory >> used during checkpoint >> 2) live migrate part of dirty pages to slave during sleep time. >> Besides, we add some statistic info in colo-v1.2-developing, which you can get these stat >> info by using command 'info migrate'. >> >> You can test any branch of the above, >> about how to test COLO, Please reference to the follow link. >> http://wiki.qemu.org/Features/COLO. > > Thanks, I'll try these out over the next few days. > It would be good to use some tags on the colo-proxy git; > it would be a bit confusing for people trying to use your previous > qemu patches if they fetched todays colo-proxy tree. > Hi Dave, I have put tags on the colo-proxy in github, thanks for your suggestion. And one more thing, to test this new version, you have to rebuild your kernel and iptables, since there are some modification :) Thanks, zhanghailiang > >> >> COLO is still in early stage, >> your comments and feedback are warmly welcomed. >> >> Cc: netfilter-devel@vger.kernel.org >> >> TODO: >> 1. Strengthen failover >> 2. COLO function switch on/off >> 2. Optimize proxy part, include proxy script. >> 1) Remove the limitation of forward network link. >> 2) Reuse the nfqueue_entry and NF_STOLEN to enqueue skb >> 3. The capability of continuous FT >> >> v5: >> - Replace the previous communication way between proxy and qemu with nfnetlink >> - Remove the 'forward device'parameter of xt_PMYCOLO, and now we use iptables command >> to set the 'forward device' >> - Turn DPRINTF into trace_ calls as Dave's suggestion >> >> v4: >> - New block replication scheme (use image-fleecing for sencondary side) >> - Adress some comments from Eric Blake and Dave >> - Add commmand colo-set-checkpoint-period to set the time of periodic checkpoint >> - Add a delay (100ms) between continuous checkpoint requests to ensure VM >> run 100ms at least since last pause. >> v3: >> - use proxy instead of colo agent to compare network packets >> - add block replication >> - Optimize failover disposal >> - handle shutdown >> >> v2: >> - use QEMUSizedBuffer/QEMUFile as COLO buffer >> - colo support is enabled by default >> - add nic replication support >> - addressed comments from Eric Blake and Dr. David Alan Gilbert >> >> v1: >> - implement the frame of colo >> >> Wen Congyang (1): >> COLO: Add block replication into colo process >> >> zhanghailiang (28): >> configure: Add parameter for configure to enable/disable COLO support >> migration: Introduce capability 'colo' to migration >> COLO: migrate colo related info to slave >> migration: Integrate COLO checkpoint process into migration >> migration: Integrate COLO checkpoint process into loadvm >> COLO: Implement colo checkpoint protocol >> COLO: Add a new RunState RUN_STATE_COLO >> QEMUSizedBuffer: Introduce two help functions for qsb >> COLO: Save VM state to slave when do checkpoint >> COLO RAM: Load PVM's dirty page into SVM's RAM cache temporarily >> COLO VMstate: Load VM state into qsb before restore it >> arch_init: Start to trace dirty pages of SVM >> COLO RAM: Flush cached RAM into SVM's memory >> COLO failover: Introduce a new command to trigger a failover >> COLO failover: Implement COLO master/slave failover work >> COLO failover: Don't do failover during loading VM's state >> COLO: Add new command parameter 'colo_nicname' 'colo_script' for net >> COLO NIC: Init/remove colo nic devices when add/cleanup tap devices >> COLO NIC: Implement colo nic device interface configure() >> COLO NIC : Implement colo nic init/destroy function >> COLO NIC: Some init work related with proxy module >> COLO: Handle nfnetlink message from proxy module >> COLO: Do checkpoint according to the result of packets comparation >> COLO: Improve checkpoint efficiency by do additional periodic >> checkpoint >> COLO: Add colo-set-checkpoint-period command >> COLO NIC: Implement NIC checkpoint and failover >> COLO: Disable qdev hotplug when VM is in COLO mode >> COLO: Implement shutdown checkpoint >> >> arch_init.c | 243 +++++++++- >> configure | 36 +- >> hmp-commands.hx | 30 ++ >> hmp.c | 14 + >> hmp.h | 2 + >> include/exec/cpu-all.h | 1 + >> include/migration/migration-colo.h | 57 +++ >> include/migration/migration-failover.h | 22 + >> include/migration/migration.h | 3 + >> include/migration/qemu-file.h | 3 +- >> include/net/colo-nic.h | 27 ++ >> include/net/net.h | 3 + >> include/sysemu/sysemu.h | 3 + >> migration/Makefile.objs | 2 + >> migration/colo-comm.c | 68 +++ >> migration/colo-failover.c | 48 ++ >> migration/colo.c | 836 +++++++++++++++++++++++++++++++++ >> migration/migration.c | 60 ++- >> migration/qemu-file-buf.c | 58 +++ >> net/Makefile.objs | 1 + >> net/colo-nic.c | 420 +++++++++++++++++ >> net/tap.c | 45 +- >> qapi-schema.json | 42 +- >> qemu-options.hx | 10 +- >> qmp-commands.hx | 41 ++ >> savevm.c | 2 +- >> scripts/colo-proxy-script.sh | 88 ++++ >> stubs/Makefile.objs | 1 + >> stubs/migration-colo.c | 58 +++ >> trace-events | 11 + >> vl.c | 39 +- >> 31 files changed, 2235 insertions(+), 39 deletions(-) >> create mode 100644 include/migration/migration-colo.h >> create mode 100644 include/migration/migration-failover.h >> create mode 100644 include/net/colo-nic.h >> create mode 100644 migration/colo-comm.c >> create mode 100644 migration/colo-failover.c >> create mode 100644 migration/colo.c >> create mode 100644 net/colo-nic.c >> create mode 100755 scripts/colo-proxy-script.sh >> create mode 100644 stubs/migration-colo.c >> >> -- >> 1.7.12.4 >> >> > -- > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK > > . >