From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:57173)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <s.priebe@profihost.ag>) id 1WBhlz-0003je-Gt
	for qemu-devel@nongnu.org; Fri, 07 Feb 2014 04:31:05 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <s.priebe@profihost.ag>) id 1WBhlt-0002P7-As
	for qemu-devel@nongnu.org; Fri, 07 Feb 2014 04:30:59 -0500
Received: from mail-ph.de-nserver.de ([85.158.179.214]:50724)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <s.priebe@profihost.ag>) id 1WBhlt-0002P1-0y
	for qemu-devel@nongnu.org; Fri, 07 Feb 2014 04:30:53 -0500
Message-ID: <52F4A7C5.2070403@profihost.ag>
Date: Fri, 07 Feb 2014 10:30:45 +0100
From: Stefan Priebe - Profihost AG <s.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>
	<52F4A78C.8000305@beyond.pl>
In-Reply-To: <52F4A78C.8000305@beyond.pl>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [Qemu-devel] [pve-devel] QEMU LIve Migration - swap_free: Bad
 swap file entry
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: =?UTF-8?B?TWFyY2luIEdpYnXFgmE=?= <m.gibula@beyond.pl>, "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Alexandre DERUMIER <aderumier@odiso.com>

Hi,
Am 07.02.2014 10:29, schrieb Marcin Gibuła:
>>>>> 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 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 ;-(
> 
> Have you tried to let test VM run idle for some time before migrating?
> (like 18-24 hours)
> 
> Having the same (or very similar) problem, I had bigger luck with
> reproducing it by not using freshly started VMs.

no i haven't tried this will do so soon.

Stefan