From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:35180)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <s.priebe@profihost.ag>) id 1WBqyw-00060K-Bx
	for qemu-devel@nongnu.org; Fri, 07 Feb 2014 14:21:04 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <s.priebe@profihost.ag>) id 1WBqyq-000659-8r
	for qemu-devel@nongnu.org; Fri, 07 Feb 2014 14:20:58 -0500
Received: from mail-ph.de-nserver.de ([85.158.179.214]:38418)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <s.priebe@profihost.ag>) id 1WBqyp-00064z-UN
	for qemu-devel@nongnu.org; Fri, 07 Feb 2014 14:20:52 -0500
Message-ID: <52F5321C.4090605@profihost.ag>
Date: Fri, 07 Feb 2014 20:21:00 +0100
From: Stefan Priebe <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>	<20140207093159.GD2374@work-vm>	<52F4A952.6080007@profihost.ag>	<52F4CB3E.3030203@profihost.ag>	<20140207122157.GF2374@work-vm>	<52F4D1CA.6030501@profihost.ag>
	<52F4D523.9040809@redhat.com> <52F4D9E2.4010600@profihost.ag>
	<52F4DD77.7000209@redhat.com> <52F4E211.9080808@profihost.ag>
	<52F4E37D.4050204@profihost.ag>
In-Reply-To: <52F4E37D.4050204@profihost.ag>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Paolo Bonzini <pbonzini@redhat.com>, "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: m.gibula@beyond.pl, qemu-devel <qemu-devel@nongnu.org>, Alexandre DERUMIER <aderumier@odiso.com>

anything i could try or debug? to help to find the problem?

Stefan

Am 07.02.2014 14:45, schrieb Stefan Priebe - Profihost AG:
> it's always the same "pattern" there are too many 0 instead of X.
>
> only seen:
>
> read:0x0000000000000000 ... expected:0xffffffffffffffff
>
> or
>
> read:0xffffffff00000000 ... expected:0xffffffffffffffff
>
> or
>
> read:0x0000bf000000bf00 ... expected:0xffffbfffffffbfff
>
> or
>
> read:0x0000000000000000 ... expected:0xb5b5b5b5b5b5b5b5
>
> no idea if this helps.
>
> Stefan
>
> Am 07.02.2014 14:39, schrieb Stefan Priebe - Profihost AG:
>> Hi,
>> Am 07.02.2014 14:19, schrieb Paolo Bonzini:
>>> Il 07/02/2014 14:04, Stefan Priebe - Profihost AG ha scritto:
>>>> first of all i've now a memory image of a VM where i can reproduce it.
>>>
>>> You mean you start that VM with -incoming 'exec:cat /path/to/vm.img'?
>>> But google stress test doesn't report any error until you start
>>> migration _and_ it finishes?
>>
>> Sorry no i meant i have a VM where i saved the memory to disk - so i
>> don't need to wait hours until i can reproduce as it does not happen
>> with a fresh started VM. So it's a state file i think.
>>
>>> Another test:
>>>
>>> - start the VM with -S, migrate, do errors appear on the destination?
>>
>> I started with -S and the errors appear AFTER resuming/unpause the VM.
>> So it is fine until i resume it on the "new" host.
>>
>> Stefan
>>