qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>,
	Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	agraf@suse.de, qemu-devel <qemu-devel@nongnu.org>,
	qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] ppc64 not resuming with v2.3.0-rc3
Date: Thu, 16 Apr 2015 23:53:24 +0200	[thread overview]
Message-ID: <55302F54.3030204@redhat.com> (raw)
In-Reply-To: <553028A6.2060500@linux.vnet.ibm.com>



On 16/04/2015 23:24, Stefan Berger wrote:
> On 04/16/2015 04:53 PM, Mark Cave-Ayland wrote:
>> On 16/04/15 20:49, Stefan Berger wrote:
>>>> Hmmmm the fix is correct in that internal MSR variables need to be
>>>> updated post-restore (as noted in the message above it was the
>>>> exception
>>>> prefix variables that weren't updated by having MSR_EP set).
>>>>
>>>> Maybe on ppc64 there is another bit similar to MSR_TGPR that needs
>>>> to be
>>>> excluded? Alex, any thoughts?
>>> I want to add that I am running QEMU for ppc64 in emulation mode on a
>>> x86_64 host. The suspend/resume problem, while in SLOF, did not exist in
>>> QEMU v2.2, so I anticipate that this is a regression would also be
>>> visible on QEMU on kvm, though a simple test on such a machine may show
>>> different...
>>>
>>> Removing the patch solves the problem while in SLOF. Once booting into
>>> Linux suspend/resume does not work - with qemu-system-ppc64 on x86_64
>>> host. Timestamps shown by Linux actually make a jump backwards and
>>> ultimately Linux hangs.
>> Just to clarify the terminology here, when you say suspend/resume are
>> you talking about a hardware suspend/resume or issuing a savevm/loadvm
>> sequence in the QEMU monitor? Are you able to provide further detail to
>> reproduce your test case?
> 
> I am using 'virsh save' to suspend the VM, 'virsh restore' to resume it,
> so I am doing this on libvirt level.

Ok, that's the equivalent of "migrate exec:cat>foo.save" and "-incoming
'exec:cat<foo.save'"

Paolo

> 
> This is the XML to just test suspend / resume while it is in SLOF. No
> disk needed.
> 
> <domain type='qemu'>
>   <name>ppc-test</name>
>   <uuid>3e17dcdb-4a22-49ed-b8f9-4df523d04bb3</uuid>
>   <memory unit='KiB'>1310720</memory>
>   <currentMemory unit='KiB'>1310720</currentMemory>
>   <vcpu placement='static'>1</vcpu>
>   <resource>
>     <partition>/machine</partition>
>   </resource>
>   <os>
>     <type arch='ppc64' machine='pseries-2.2'>hvm</type>
>     <boot dev='hd'/>
>     <boot dev='cdrom'/>
>   </os>
>   <clock offset='utc'/>
>   <on_poweroff>destroy</on_poweroff>
>   <on_reboot>restart</on_reboot>
>   <on_crash>restart</on_crash>
>   <devices>
>     <emulator>/usr/bin/qemu-system-ppc64</emulator>
>     <controller type='usb' index='0'>
>       <address type='pci' domain='0x0000' bus='0x00' slot='0x01'
> function='0x0'/>
>     </controller>
>     <controller type='pci' index='0' model='pci-root'/>
>     <input type='keyboard' bus='usb'/>
>     <input type='mouse' bus='usb'/>
>     <graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0'>
>       <listen type='address' address='0.0.0.0'/>
>     </graphics>
>     <video>
>       <model type='vga' vram='16384' heads='1'/>
>       <address type='pci' domain='0x0000' bus='0x00' slot='0x05'
> function='0x0'/>
>     </video>
>     <memballoon model='virtio'>
>       <address type='pci' domain='0x0000' bus='0x00' slot='0x02'
> function='0x0'/>
>     </memballoon>
>   </devices>
>   <seclabel type='dynamic' model='selinux' relabel='yes'/>
> </domain>
> 
> 
>     Stefan
> 
> 
>>
>> ATB,
>>
>> Mark.
>>
> 
> 
> 

  reply	other threads:[~2015-04-16 21:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 16:43 [Qemu-devel] ppc64 not resuming with v2.3.0-rc3 Stefan Berger
2015-04-16 19:42 ` Mark Cave-Ayland
2015-04-16 19:49   ` Stefan Berger
2015-04-16 20:53     ` Mark Cave-Ayland
2015-04-16 21:24       ` Stefan Berger
2015-04-16 21:53         ` Paolo Bonzini [this message]
2015-04-16 22:23           ` Mark Cave-Ayland

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=55302F54.3030204@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=agraf@suse.de \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=stefanb@linux.vnet.ibm.com \
    /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).