From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:59784)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <agraf@suse.de>) id 1Y1CWN-00066p-Gf
	for qemu-devel@nongnu.org; Wed, 17 Dec 2014 06:12:06 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <agraf@suse.de>) id 1Y1CWF-000473-WB
	for qemu-devel@nongnu.org; Wed, 17 Dec 2014 06:11:59 -0500
Message-ID: <549164F5.5080902@suse.de>
Date: Wed, 17 Dec 2014 12:11:49 +0100
From: Alexander Graf <agraf@suse.de>
MIME-Version: 1.0
References: <54915835.6030508@ilande.co.uk> <549159B6.6000006@suse.de>
	<54915F28.1090001@ilande.co.uk>
In-Reply-To: <54915F28.1090001@ilande.co.uk>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [Qemu-ppc] Unable to loadvm on qemu-system-ppc -M
 g3beige (keyboard freeze)
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: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>, "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>, qemu-devel <qemu-devel@nongnu.org>



On 17.12.14 11:47, Mark Cave-Ayland wrote:
> On 17/12/14 10:23, Alexander Graf wrote:
> 
>>> After the restart the keyboard is frozen and unresponsive. Some
>>> preliminary poking with gdb before and after seems to indicate that the
>>> cuda_receive_packet() functions aren't being called after the restart
>>> indicating that likely some state is missing from the savevm image and
>>> not being restored correctly. Anyone have any ideas as to what might be
>>> going wrong?
>>
>> I don't think anyone has test the migration code on non-papr ppc for
>> quite a while. In fact, I'm surprised it's only the keyboard not working :).
>>
>> You're more than invited to send patches to fix it! :)
> 
> How did I know that would be the response ;) I don't suppose anyone has
> a vague memory of the timeframe/QEMU version when a savevm/loadvm was
> last working for -M g3beige as a starting point?!

Phew - 0.7.0 maybe? If you say that only CUDA is broken, I don't think
it'd be too hard to fix :). Check that there are VMSTATEs for everything
and maybe retrigger interrupts after migration.


Alex