From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58331) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WBhsN-0005wX-Iz for qemu-devel@nongnu.org; Fri, 07 Feb 2014 04:37:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WBhsH-00042F-Q3 for qemu-devel@nongnu.org; Fri, 07 Feb 2014 04:37:35 -0500 Received: from mail-ph.de-nserver.de ([85.158.179.214]:48174) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WBhsH-00042A-Ei for qemu-devel@nongnu.org; Fri, 07 Feb 2014 04:37:29 -0500 Message-ID: <52F4A952.6080007@profihost.ag> Date: Fri, 07 Feb 2014 10:37:22 +0100 From: Stefan Priebe - Profihost AG MIME-Version: 1.0 References: <50562927-0498-460b-8f29-98722e332149@mailpro> <52F496B4.5030505@profihost.ag> <20140207091513.GC2374@work-vm> <52F4A554.1080400@profihost.ag> <20140207093159.GD2374@work-vm> In-Reply-To: <20140207093159.GD2374@work-vm> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: "Dr. David Alan Gilbert" Cc: qemu-devel , Alexandre DERUMIER Am 07.02.2014 10:31, schrieb Dr. David Alan Gilbert: > * 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. Right that makes sense - sadly i still don't know how to reproduce? Any app ideas i can try? >> 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 >