From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47976) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZKjKU-0000eH-F2 for qemu-devel@nongnu.org; Thu, 30 Jul 2015 04:36:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZKjKQ-00068R-E6 for qemu-devel@nongnu.org; Thu, 30 Jul 2015 04:36:42 -0400 Received: from mx1.redhat.com ([209.132.183.28]:43433) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZKjKQ-00068L-8L for qemu-devel@nongnu.org; Thu, 30 Jul 2015 04:36:38 -0400 Message-ID: <55B9DD38.2030706@redhat.com> Date: Thu, 30 Jul 2015 16:15:52 +0800 From: Jason Wang MIME-Version: 1.0 References: <55AC9859.3050100@cn.fujitsu.com> <55B9A6C6.6010008@redhat.com> <55B9CF3F.2060202@huawei.com> <20150730080339.GA2250@work-vm> In-Reply-To: <20150730080339.GA2250@work-vm> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [POC] colo-proxy in qemu List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Dr. David Alan Gilbert" , "Dong, Eddie" Cc: zhanghailiang , Li Zhijian , "jan.kiszka@siemens.com" , "qemu-devel@nongnu.org" , "peter.huangpeng" , Gonglei , "stefanha@redhat.com" , Yang Hongyang On 07/30/2015 04:03 PM, Dr. David Alan Gilbert wrote: > * Dong, Eddie (eddie.dong@intel.com) wrote: >>>> A question here, the packet comparing may be very tricky. For example, >>>> some protocol use random data to generate unpredictable id or >>>> something else. One example is ipv6_select_ident() in Linux. So COLO >>>> needs a mechanism to make sure PVM and SVM can generate same random >>> data? >>> Good question, the random data connection is a big problem for COLO. At >>> present, it will trigger checkpoint processing because of the different random >>> data. >>> I don't think any mechanisms can assure two different machines generate the >>> same random data. If you have any ideas, pls tell us :) >>> >>> Frequent checkpoint can handle this scenario, but maybe will cause the >>> performance poor. :( >>> >> The assumption is that, after VM checkpoint, SVM and PVM have identical internal state, so the pattern used to generate random data has high possibility to generate identical data at short time, at least... > They do diverge pretty quickly though; I have simple examples which > reliably cause a checkpoint because of simple randomness in applications. > > Dave > And it will become even worse if hwrng is used in guest.