qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: "manish.mishra" <manish.mishra@nutanix.com>
Cc: John Levon <john.levon@nutanix.com>,
	Florian Schmidt <flosch@nutanix.com>,
	carl.waldspurger@nutanix.com,
	Prerna Saxena <prerna.saxena@nutanix.com>,
	Aravind Retnakaran <aravind.retnakaran@nutanix.com>,
	rohit.kumar3@nutanix.com,
	"Daniel P . Berrange" <berrange@redhat.com>,
	qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>,
	Dr. David Alan Gilbert <dgilbert@redhat.com>,
	Maciej S. Szmigiero <maciej.szmigiero@oracle.com>,
	Sunil Muthuswamy <sunilmut@microsoft.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Justin Terry (VM) <juterry@microsoft.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>
Subject: Re: Expose support for HyperV features via QMP
Date: Thu, 09 Feb 2023 13:58:01 +0000	[thread overview]
Message-ID: <87r0uzlyql.fsf@linaro.org> (raw)
In-Reply-To: <18bea7dd-c776-6328-2c6b-71c88838db72@nutanix.com>


"manish.mishra" <manish.mishra@nutanix.com> writes:

> Hi Everyone,
>
> Checking if there is any feedback on this.

I've expanded the CC list to some relevant maintainers and people who
have touched that code in case this was missed.

> Thanks
>
> Manish Mishra
>
> On 31/01/23 8:17 pm, manish.mishra wrote:
>
>  Hi Everyone,
>  I hope everyone is doing great. We wanted to check why we do not expose support for HyperV features in
>  Qemu similar to what we do for normal CPU features via query-cpu-defs or cpu-model-expansion QMP
>  commands. This support is required for live migration with HyperV features as hyperv passthrough is not
>  an option. If users had knowledge of what features are supported by source and destination, VM can be
>  started with an intersection of features supported by both source and destination.
>  If there is no specific reason for not doing this, does it make sense to add a new QMP which expose
>  support (internally also validating with KVM or KVM_GET_SUPPORTED_HV_CPUID ioctl) for HyperV
>  features.
>  Apologies in advance if i misunderstood something.
>
>  Thanks
>
>  Manish Mishra


-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  reply	other threads:[~2023-02-09 14:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 14:47 Expose support for HyperV features via QMP manish.mishra
2023-02-01 10:42 ` manish.mishra
2023-02-09 10:50 ` manish.mishra
2023-02-09 13:58   ` Alex Bennée [this message]
2023-02-09 14:17     ` Vitaly Kuznetsov
2023-02-10  8:42       ` manish.mishra

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=87r0uzlyql.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=aravind.retnakaran@nutanix.com \
    --cc=berrange@redhat.com \
    --cc=carl.waldspurger@nutanix.com \
    --cc=dgilbert@redhat.com \
    --cc=flosch@nutanix.com \
    --cc=john.levon@nutanix.com \
    --cc=juterry@microsoft.com \
    --cc=maciej.szmigiero@oracle.com \
    --cc=manish.mishra@nutanix.com \
    --cc=pbonzini@redhat.com \
    --cc=prerna.saxena@nutanix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=rohit.kumar3@nutanix.com \
    --cc=sunilmut@microsoft.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 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).