From: Eduardo Habkost <ehabkost@redhat.com>
To: Roman Kagan <rkagan@virtuozzo.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-2.12 2/2] i386/hyperv: error out if features requested but unsupported
Date: Fri, 23 Mar 2018 16:56:21 -0300 [thread overview]
Message-ID: <20180323195621.GN3417@localhost.localdomain> (raw)
In-Reply-To: <20180323125808.4479-3-rkagan@virtuozzo.com>
On Fri, Mar 23, 2018 at 03:58:08PM +0300, Roman Kagan wrote:
> In order to guarantee compatibility on migration, QEMU should have
> complete control over the features it announces to the guest via CPUID.
>
> However, for a number of Hyper-V-related cpu properties, if the
> corresponding feature is not supported by the underlying KVM, the
> propery is silently ignored and the feature is not announced to the
> guest.
>
> Refuse to start with an error instead.
>
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Roman Kagan <rkagan@virtuozzo.com>
I wonder if we should make these just warnings on -stable, and
make them fatal errors only on 2.12. I wouldn't want to make
existing running VMs not runnable on a stable update.
> ---
> target/i386/kvm.c | 25 +++++++++++++++++++++----
> 1 file changed, 21 insertions(+), 4 deletions(-)
>
> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> index fb20ff18c2..c9c359241c 100644
> --- a/target/i386/kvm.c
> +++ b/target/i386/kvm.c
> @@ -658,17 +658,34 @@ static int hyperv_handle_properties(CPUState *cs)
> env->features[FEAT_HYPERV_EAX] |= HV_ACCESS_FREQUENCY_MSRS;
> env->features[FEAT_HYPERV_EDX] |= HV_FREQUENCY_MSRS_AVAILABLE;
> }
> - if (cpu->hyperv_crash && has_msr_hv_crash) {
> + if (cpu->hyperv_crash) {
> + if (!has_msr_hv_crash) {
> + fprintf(stderr,
> + "Hyper-V crash MSRs are not supported by kernel\n");
I would mention the corresponding "hv-..." -cpu option
explicitly, for clarity.
> + return -ENOSYS;
> + }
> env->features[FEAT_HYPERV_EDX] |= HV_GUEST_CRASH_MSR_AVAILABLE;
> }
> env->features[FEAT_HYPERV_EDX] |= HV_CPU_DYNAMIC_PARTITIONING_AVAILABLE;
> - if (cpu->hyperv_reset && has_msr_hv_reset) {
> + if (cpu->hyperv_reset) {
> + if (!has_msr_hv_reset) {
> + fprintf(stderr, "Hyper-V reset MSR is not supported by kernel\n");
> + return -ENOSYS;
> + }
> env->features[FEAT_HYPERV_EAX] |= HV_RESET_AVAILABLE;
> }
> - if (cpu->hyperv_vpindex && has_msr_hv_vpindex) {
> + if (cpu->hyperv_vpindex) {
> + if (!has_msr_hv_vpindex) {
> + fprintf(stderr, "Hyper-V VP_INDEX is not supported by kernel\n");
> + return -ENOSYS;
> + }
> env->features[FEAT_HYPERV_EAX] |= HV_VP_INDEX_AVAILABLE;
> }
> - if (cpu->hyperv_runtime && has_msr_hv_runtime) {
> + if (cpu->hyperv_runtime) {
> + if (!has_msr_hv_runtime) {
> + fprintf(stderr, "Hyper-V VP_INDEX is not supported by kernel\n");
> + return -ENOSYS;
> + }
> env->features[FEAT_HYPERV_EAX] |= HV_VP_RUNTIME_AVAILABLE;
> }
> if (cpu->hyperv_synic) {
> --
> 2.14.3
>
--
Eduardo
next prev parent reply other threads:[~2018-03-23 19:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 12:58 [Qemu-devel] [PATCH for-2.12 0/2] i386/hyperv: fully control Hyper-V features in CPUID Roman Kagan
2018-03-23 12:58 ` [Qemu-devel] [PATCH for-2.12 1/2] i386/hyperv: add hv-frequencies cpu property Roman Kagan
2018-03-23 19:41 ` Eduardo Habkost
2018-03-23 12:58 ` [Qemu-devel] [PATCH for-2.12 2/2] i386/hyperv: error out if features requested but unsupported Roman Kagan
2018-03-23 19:56 ` Eduardo Habkost [this message]
2018-03-26 15:06 ` Roman Kagan
2018-03-28 14:18 ` Eduardo Habkost
2018-03-23 14:02 ` [Qemu-devel] [PATCH for-2.12 0/2] i386/hyperv: fully control Hyper-V features in CPUID no-reply
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=20180323195621.GN3417@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=rkagan@virtuozzo.com \
--cc=vkuznets@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.