From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46419) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WBlN8-000082-6d for qemu-devel@nongnu.org; Fri, 07 Feb 2014 08:21:39 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WBlN2-0002TX-SR for qemu-devel@nongnu.org; Fri, 07 Feb 2014 08:21:34 -0500 Received: from mail-ph.de-nserver.de ([85.158.179.214]:59551) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WBlN2-0002TD-HZ for qemu-devel@nongnu.org; Fri, 07 Feb 2014 08:21:28 -0500 Message-ID: <52F4DDCF.2050002@profihost.ag> Date: Fri, 07 Feb 2014 14:21:19 +0100 From: Stefan Priebe - Profihost AG MIME-Version: 1.0 References: <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> <52F4DB4E.5040307@profihost.ag> <20140207131521.GH2374@work-vm> In-Reply-To: <20140207131521.GH2374@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: Paolo Bonzini , qemu-devel , Alexandre DERUMIER Hi, Am 07.02.2014 14:15, schrieb Dr. David Alan Gilbert: > * Stefan Priebe - Profihost AG (s.priebe@profihost.ag) wrote: >> Hi, >> >> Am 07.02.2014 14:08, schrieb Dr. David Alan Gilbert: >>> * Stefan Priebe - Profihost AG (s.priebe@profihost.ag) wrote: > >>>> 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. > > There's a heck of a lot of other stuff that goes on in migration, and that > downtime isn't quite the same. > > If it can be reproduced with just suspend/resume stuff then that's a different > place to start looking than if it's migration only. ah OK now i got it. No i can't reproduce with suspend resume. But while migrating it happens directly at the end when the switch from host a to b happens. > Dave > -- > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK >