From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38488) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UjRHP-000257-CM for qemu-devel@nongnu.org; Mon, 03 Jun 2013 05:42:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UjRHK-0006Cs-I9 for qemu-devel@nongnu.org; Mon, 03 Jun 2013 05:42:19 -0400 Message-ID: <51AC64E3.4060205@redhat.com> Date: Mon, 03 Jun 2013 11:41:55 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1367545092-19980-1-git-send-email-david@gibson.dropbear.id.au> <1367545092-19980-8-git-send-email-david@gibson.dropbear.id.au> <51875DA7.4090308@redhat.com> <51A301AC.8070101@ozlabs.ru> <51A30528.9020708@redhat.com> <51A83C18.2030102@ozlabs.ru> <1369994875.3928.137.camel@pasglop> <51A87AAA.6080306@ozlabs.ru> <51A87E5B.1030100@redhat.com> <51AC2D98.8000404@ozlabs.ru> <1370246855.3766.60.camel@pasglop> <51AC63E0.4030105@ozlabs.ru> In-Reply-To: <51AC63E0.4030105@ozlabs.ru> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 7/8] pseries: savevm support for PAPR virtual SCSI List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexey Kardashevskiy Cc: quintela@redhat.com, agraf@suse.de, qemu-devel@nongnu.org, qemu-ppc@nongnu.org, David Gibson Il 03/06/2013 11:37, Alexey Kardashevskiy ha scritto: > On 06/03/2013 06:07 PM, Benjamin Herrenschmidt wrote: >> On Mon, 2013-06-03 at 15:46 +1000, Alexey Kardashevskiy wrote: >>> Ok. I implemented {save|load}_request for IBMVSCSI, started testing - >>> the >>> destination system behaves very unstable, sometime it is a fault in >>> _raw_spin_lock or it looks okay but any attempt to read the filesystem >>> leads to 100% cpu load in qemu process and no response from the guest. >>> >>> I tried virtio-scsi as well (as it was referred as a good example), it >>> fails in exactly the same way. So I started wondering - when did you >>> try it >>> last time? :) >> >> Did you try virtio-blk or even a ramdisk ? IE, Make sure the problem >> isn't some kind of generic migration issue unrelated to storage ? > > > False alarm. During multiple switches between different git branches, I > just lost my own patch which disables "bulk" migration (which we want to > revert anyway, just waiting for the author to do that himself) :) > > At least my test does not fail any more. Sorry for confusing. Good, I was surprised. That area doesn't see much testing, but it hasn't seen much change either. Paolo