From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49879) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y1Blw-0001LT-0D for qemu-devel@nongnu.org; Wed, 17 Dec 2014 05:24:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y1Blo-0002CN-AY for qemu-devel@nongnu.org; Wed, 17 Dec 2014 05:23:59 -0500 Message-ID: <549159B6.6000006@suse.de> Date: Wed, 17 Dec 2014 11:23:50 +0100 From: Alexander Graf MIME-Version: 1.0 References: <54915835.6030508@ilande.co.uk> In-Reply-To: <54915835.6030508@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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mark Cave-Ayland , "qemu-ppc@nongnu.org" , qemu-devel On 17.12.14 11:17, Mark Cave-Ayland wrote: > Hi all, > > Whilst trying to debug a regression, I've found that I can't > successfully execute a savevm/restart/loadvm sequence in qemu-system-ppc > -M g3beige. The loadvm command succeeds after the restart, however the > keyboard remains unresponsive making it impossible to continue from > where I left off. > > Steps to reproduce: > > 1) Launch qemu-system-ppc as follows: > > qemu-system-ppc -M g3beige -hda tmp.qcow2 -prom-env 'auto-boot?=false' > > 2) Switch to the monitor in order to pause the VM and save > > (qemu) stop > (qemu) savevm test > (qemu) c > > 3) Switch back to the VGA display and confirm the keyboard works > > 4) Close qemu-system-ppc > > 5) Restart qemu-system-ppc with -loadvm options > > qemu-system-ppc -M g3beige -prom-env 'auto-boot?=false' -loadvm test > > > 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! :) Alex