On Tue, Jan 26, 2016 at 02:17:08PM +0800, Wen Congyang wrote: > On 01/26/2016 02:41 AM, Konrad Rzeszutek Wilk wrote: > > On Thu, Dec 17, 2015 at 03:48:12PM +0800, Wen Congyang wrote: > >> From: Yang Hongyang <hongyang.y...@easystack.cn> > >> > >> In normal migration, the qemu state was passed to qemu as a parameter. > > > > /was/is/ > > > >> With COLO, Secondary vm is running. So we will do the following steps > >> at every checkpoint: > >> 1. suspend both primary vm and secondary vm > >> 2. sync the state > >> 3. resume both primary vm and secondary vm > >> Primary will send qemu's state in step2, and > >> Secondary's qemu should read it and restore the state before it > > > > s/Secondary/secondary/ > >> is resumed. We can not pass the state to qemu as a parameter because > >> Secondary QEMU already started at this point, so we introduce > > > > s/Secondary/secondary/ > >> libxl__domain_restore_device_model() to do it. > >> This API should be called before resuming secondary vm. > > > > s/before/MUST/ > > s/should/MUST/?
<sigh> Yes. Thank you! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
