qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: David Hildenbrand <david@redhat.com>, Cornelia Huck <cohuck@redhat.com>
Cc: Richard Henderson <rth@twiddle.net>,
	Alexander Graf <agraf@suse.de>,
	Yi Min Zhao <zyimin@linux.vnet.ibm.com>,
	Halil Pasic <pasic@linux.vnet.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Jason J . Herne" <jjherne@linux.vnet.ibm.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 2/2] s390x/ais: disable ais for compat machines
Date: Wed, 27 Sep 2017 10:03:31 +0200	[thread overview]
Message-ID: <2f3eb94e-c07f-8752-059c-de5900859fff@de.ibm.com> (raw)
In-Reply-To: <5770bcf6-3608-11e7-7f4e-a91f5046c8c1@de.ibm.com>



On 09/27/2017 09:12 AM, Christian Borntraeger wrote:
> 
> 
> On 09/26/2017 03:51 PM, David Hildenbrand wrote:
>> On 26.09.2017 15:36, Christian Borntraeger wrote:
>>> With newer kernels that do support the ais feature (4.13) a qemu 2.11
>>> will not only enable the ais feature for the 2.11 machine, but also
>>> for a <=2.10 compat machine. As this feature is not available in
>>> QEMU <=2.9 (and QEMU 2.10.1), this guest will fail to migrate
>>> back to an older qemu like 2.9 with:
>>>
>>> _snip_
>>> error while loading state for instance 0x0 of device 's390-flic'
>>> _snip_
>>>
>>> making the whole compat machine dis-functional. As a permanent fix, we
>>> need to fence the ais feature for machines <= 2.10
>>>
>>> Due to ais being enabled on 2.10.0 (fixed in 2.10.1) this will prevent
>>> migration of ais-enabled guests from 2.10.0 with
>>>
>>> _snip_
>>> qemu-system-s390x: Failed to load s390-flic/ais:tmp
>>> qemu-system-s390x: error while loading state for instance 0x0 of device 's390-flic'
>>> qemu-system-s390x: load of migration failed: Function not implemented
>>> _snip_
>>>
>>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>>> Cc: Yi Min Zhao <zyimin@linux.vnet.ibm.com>
>>> Cc: Dr. David Alan Gilbert <dgilbert@redhat.com>
>>> ---
>>>  hw/intc/s390_flic_kvm.c            |  4 +++-
>>
>>
>> As discussed, I think we should use cpu_model_allowed() instead.
> I think I still prefer the explicit check for ais-enabled to make managedsave
> (on the same system) continue to work if the user does not specify a cpu model 
> at all (which will then fallback to the host model). We already fence other
> things (like guarded storage) and yes it will grow over time but the 
> *_allowed things seem to be the smallest maintenance issue in this area.

Hmm, on the other hand this fails only when we migrate to an older qemu during
managedsave. So yes, maybe this is just an "will not work anyway"

      reply	other threads:[~2017-09-27  8:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-26 13:36 [Qemu-devel] [PATCH v2 0/2] ais fixups for 2.11 Christian Borntraeger
2017-09-26 13:36 ` [Qemu-devel] [PATCH v2 1/2] s390x/ais: enable ais when migration is available Christian Borntraeger
2017-09-26 13:43   ` David Hildenbrand
2017-09-26 14:06     ` Christian Borntraeger
2017-09-26 14:08       ` David Hildenbrand
2017-09-27  4:35       ` Yi Min Zhao
2017-09-27  5:45   ` Yi Min Zhao
2017-09-27  7:02     ` Christian Borntraeger
2017-09-26 13:36 ` [Qemu-devel] [PATCH v2 2/2] s390x/ais: disable ais for compat machines Christian Borntraeger
2017-09-26 13:51   ` David Hildenbrand
2017-09-27  7:12     ` Christian Borntraeger
2017-09-27  8:03       ` Christian Borntraeger [this message]

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=2f3eb94e-c07f-8752-059c-de5900859fff@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=jjherne@linux.vnet.ibm.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=zyimin@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).