qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] Unable to loadvm on qemu-system-ppc -M g3beige (keyboard freeze)
Date: Wed, 17 Dec 2014 11:23:50 +0100	[thread overview]
Message-ID: <549159B6.6000006@suse.de> (raw)
In-Reply-To: <54915835.6030508@ilande.co.uk>



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

  reply	other threads:[~2014-12-17 10:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17 10:17 [Qemu-devel] Unable to loadvm on qemu-system-ppc -M g3beige (keyboard freeze) Mark Cave-Ayland
2014-12-17 10:23 ` Alexander Graf [this message]
2014-12-17 10:47   ` [Qemu-devel] [Qemu-ppc] " Mark Cave-Ayland
2014-12-17 11:11     ` Alexander Graf
2014-12-17 11:23       ` Peter Maydell
2014-12-18 13:54         ` Mark Cave-Ayland
2014-12-18 14:46           ` Alexander Graf
2014-12-18 15:13             ` Peter Maydell
2014-12-18 21:36               ` Mark Cave-Ayland
2014-12-18 23:01                 ` Alexander Graf
2014-12-19 10:53                   ` Mark Cave-Ayland
2014-12-19 12:29                     ` Peter Maydell
2014-12-19 14:12                       ` Mark Cave-Ayland
2014-12-19 14:29                         ` Peter Maydell
2014-12-19 16:15                           ` Mark Cave-Ayland
2014-12-19 16:35                             ` Peter Maydell
2014-12-19 16:51                               ` Mark Cave-Ayland
2014-12-19 17:16                                 ` Alexander Graf
2014-12-19 17:29                                   ` Paolo Bonzini
2014-12-19 17:45                                     ` Alexander Graf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=549159B6.6000006@suse.de \
    --to=agraf@suse.de \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).