From: David Hildenbrand <david@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cohuck@redhat.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Janosch Frank" <frankja@linux.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
"Halil Pasic" <pasic@linux.ibm.com>,
qemu-s390x <qemu-s390x@nongnu.org>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [PATCH] s390x/cpu_model: disallow unpack for --only-migratable
Date: Mon, 25 Jan 2021 14:04:08 +0100 [thread overview]
Message-ID: <97eae34e-5568-0150-fee1-ffdc438948e0@redhat.com> (raw)
In-Reply-To: <90bb436e-bbf2-6d77-587a-0fb5b22d13cd@de.ibm.com>
On 25.01.21 13:59, Christian Borntraeger wrote:
>
>
> On 25.01.21 13:57, David Hildenbrand wrote:
>> On 25.01.21 13:53, Christian Borntraeger wrote:
>>> secure execution (aka protected virtualization) guests cannot be
>>> migrated at the moment. Disallow the unpack facility if the user
>>> specifies --only-migratable.
>>>
>>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>>> ---
>>> target/s390x/cpu_models.c | 6 ++++++
>>> 1 file changed, 6 insertions(+)
>>>
>>> diff --git a/target/s390x/cpu_models.c b/target/s390x/cpu_models.c
>>> index 35179f9dc7ba..0fa082ae2546 100644
>>> --- a/target/s390x/cpu_models.c
>>> +++ b/target/s390x/cpu_models.c
>>> @@ -26,6 +26,7 @@
>>> #include "qapi/qmp/qdict.h"
>>> #ifndef CONFIG_USER_ONLY
>>> #include "sysemu/arch_init.h"
>>> +#include "sysemu/sysemu.h"
>>> #include "hw/pci/pci.h"
>>> #endif
>>> #include "qapi/qapi-commands-machine-target.h"
>>> @@ -878,6 +879,11 @@ static void check_compatibility(const S390CPUModel *max_model,
>>> return;
>>> }
>>>
>>> + if (only_migratable && test_bit(S390_FEAT_UNPACK, model->features)) {
>>> + error_setg(errp, "The unpack facility is not compatible with "
>>> + "the --only-migratable option");
>>
>> return; ?
>
> of course.
>
>>
>>
>> This implies that a VM with "-cpu host" might not start anymore, right?
>
> Only if --only-migratable is set.
>
Right, that's what I meant
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2021-01-25 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 12:53 [PATCH] s390x/cpu_model: disallow unpack for --only-migratable Christian Borntraeger
2021-01-25 12:57 ` David Hildenbrand
2021-01-25 12:59 ` Christian Borntraeger
2021-01-25 13:04 ` David Hildenbrand [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=97eae34e-5568-0150-fee1-ffdc438948e0@redhat.com \
--to=david@redhat.com \
--cc=berrange@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=dgilbert@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.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).