From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42923)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <s.priebe@profihost.ag>) id 1WBlCm-0002R6-7Q
	for qemu-devel@nongnu.org; Fri, 07 Feb 2014 08:10:57 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <s.priebe@profihost.ag>) id 1WBlCh-0007NP-7Z
	for qemu-devel@nongnu.org; Fri, 07 Feb 2014 08:10:52 -0500
Received: from mail-ph.de-nserver.de ([85.158.179.214]:54223)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <s.priebe@profihost.ag>) id 1WBlCg-0007MP-Oj
	for qemu-devel@nongnu.org; Fri, 07 Feb 2014 08:10:46 -0500
Message-ID: <52F4DB4E.5040307@profihost.ag>
Date: Fri, 07 Feb 2014 14:10:38 +0100
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
MIME-Version: 1.0
References: <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>
	<20140207130823.GG2374@work-vm>
In-Reply-To: <20140207130823.GG2374@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: <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: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>, Alexandre DERUMIER <aderumier@odiso.com>

Hi,

Am 07.02.2014 14:08, schrieb Dr. David Alan Gilbert:
> * Stefan Priebe - Profihost AG (s.priebe@profihost.ag) wrote:
>> Hi,
>>
>> Am 07.02.2014 13:44, schrieb Paolo Bonzini:
>>> Il 07/02/2014 13:30, Stefan Priebe - Profihost AG ha scritto:
>>>>>>> i was able to reproduce with a longer running test VM running the
>>>>> google
>>>>>>> stress test.
>>>>>
>>>>> Hmm that's quite a fun set of differences; I think I'd like
>>>>> to understand whether the pattern is related to the pattern of what
>>>>> the test is doing.
>>>
>>> Stefan, can you try to reproduce it:
>>
>> first of all i've now a memory image of a VM where i can reproduce it.
>> reproducing does NOT work if i boot the VM freshly i need to let it run
>> for some hours.
>>
>> Then just when the migration finishes there is a short time frame where
>> the google stress app reports memory errors than when the migration
>> finishes it runs fine again.
>>
>> It seems to me it is related to pause and unpause/resume?
> 
> But do you have to pause/resume it to cause the error? Have you got cases
> where you boot it and then leave it running for a few hours and then it 
> fails if you migrate it?

Yes but isn't migration always a pause / unpause at the end? I thought
migration_downtime is the value a very small pause unpause is allowed.

Stefan