From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target/i386: kvm: add VMX and SVM migration blockers
Date: Fri, 16 Nov 2018 16:56:22 +0000 [thread overview]
Message-ID: <20181116165622.GB2457@work-vm> (raw)
In-Reply-To: <20181116164806.26929-1-pbonzini@redhat.com>
* Paolo Bonzini (pbonzini@redhat.com) wrote:
> Nested VMX and SVM do not support live migration yet. Add a blocker
> until that is worked out.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> target/i386/kvm.c | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> index db1f4104b6..3b6fbd3f20 100644
> --- a/target/i386/kvm.c
> +++ b/target/i386/kvm.c
> @@ -860,6 +860,8 @@ static int hyperv_init_vcpu(X86CPU *cpu)
> }
>
> static Error *invtsc_mig_blocker;
> +static Error *vmx_mig_blocker;
> +static Error *svm_mig_blocker;
>
> #define KVM_MAX_CPUID_ENTRIES 100
>
> @@ -1250,6 +1252,29 @@ int kvm_arch_init_vcpu(CPUState *cs)
> if (c) {
> has_msr_feature_control = !!(c->ecx & CPUID_EXT_VMX) ||
> !!(c->ecx & CPUID_EXT_SMX);
> +
> + }
> +
> + if ((env->features[FEAT_1_ECX] & CPUID_EXT_VMX) && !vmx_mig_blocker) {
> + error_setg(&vmx_mig_blocker,
> + "Nested VMX virtualization does not support live migration yet");
> + r = migrate_add_blocker(vmx_mig_blocker, &local_err);
> + if (local_err) {
> + error_report_err(local_err);
> + error_free(vmx_mig_blocker);
> + return r;
> + }
> + }
> +
> + if ((env->features[FEAT_8000_0001_ECX] & CPUID_EXT3_SVM) && !svm_mig_blocker) {
> + error_setg(&svm_mig_blocker,
> + "Nested SVM virtualization does not support live migration yet");
> + r = migrate_add_blocker(svm_mig_blocker, &local_err);
> + if (local_err) {
> + error_report_err(local_err);
> + error_free(svm_mig_blocker);
> + return r;
> + }
I think that's OK from a migration point of view; my only worry is if
people have nesting enabled by default. On AMD isn't it common to have
it enabled by default in KVM? Especially if using -cpu host ?
Dave
> }
>
> if (env->mcg_cap & MCG_LMCE_P) {
> --
> 2.19.1
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2018-11-16 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 16:48 [Qemu-devel] [PATCH] target/i386: kvm: add VMX and SVM migration blockers Paolo Bonzini
2018-11-16 16:48 ` [Qemu-devel] [PATCH] migration: savevm: consult " Paolo Bonzini
2018-11-16 17:12 ` Dr. David Alan Gilbert
2018-11-19 18:20 ` Paolo Bonzini
2018-11-17 2:15 ` Wang, Wei W
2018-11-16 16:56 ` Dr. David Alan Gilbert [this message]
2018-11-19 18:21 ` [Qemu-devel] [PATCH] target/i386: kvm: add VMX and SVM " Paolo Bonzini
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=20181116165622.GB2457@work-vm \
--to=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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 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.