From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57425) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WBhn9-0004jD-R0 for qemu-devel@nongnu.org; Fri, 07 Feb 2014 04:32:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WBhn3-0002g4-Uq for qemu-devel@nongnu.org; Fri, 07 Feb 2014 04:32:11 -0500 Received: from mx1.redhat.com ([209.132.183.28]:44106) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WBhn3-0002el-Nh for qemu-devel@nongnu.org; Fri, 07 Feb 2014 04:32:05 -0500 Date: Fri, 7 Feb 2014 09:31:59 +0000 From: "Dr. David Alan Gilbert" Message-ID: <20140207093159.GD2374@work-vm> References: <50562927-0498-460b-8f29-98722e332149@mailpro> <52F496B4.5030505@profihost.ag> <20140207091513.GC2374@work-vm> <52F4A554.1080400@profihost.ag> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52F4A554.1080400@profihost.ag> Subject: Re: [Qemu-devel] [pve-devel] QEMU LIve Migration - swap_free: Bad swap file entry List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Priebe - Profihost AG Cc: qemu-devel , Alexandre DERUMIER * Stefan Priebe - Profihost AG (s.priebe@profihost.ag) wrote: > > Am 07.02.2014 10:15, schrieb Dr. David Alan Gilbert: > > * Stefan Priebe - Profihost AG (s.priebe@profihost.ag) wrote: > >> Am 07.02.2014 09:15, schrieb Alexandre DERUMIER: > >>> > >>> do you use xbzrle for live migration ? > >> > >> no - i'm really stucked right now with this. Biggest problem i can't > >> reproduce with test machines ;-( > > > > Only being able to test on your production VMs isn't fun; > > is it possible or you to run an extra program on these VMs - e.g. > > if we came up with a simple (userland) memory test? > > You mean to reproduce? I'm more interested in seeing what type of corruption is happening; if you've got a test VM that corrupts memory and we can run a program in that vm that writes a known pattern into memory and checks it then see what changed after migration, it might give a clue. But obviously this would only be of any use if run on the VM that actually fails. > I already tried https://code.google.com/p/stressapptest/ while migrating > on a test VM but this works fine. > > I also tried running mysql bench while migrating on a test vm and this > works too ;-( Dave -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK