qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "manish.mishra" <manish.mishra@nutanix.com>
To: Vitaly Kuznetsov <vkuznets@redhat.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" <juterry@microsoft.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: Expose support for HyperV features via QMP
Date: Fri, 10 Feb 2023 14:12:46 +0530	[thread overview]
Message-ID: <92f5f388-f635-a455-c48a-b604058cb09f@nutanix.com> (raw)
In-Reply-To: <87bkm27wj7.fsf@ovpn-194-92.brq.redhat.com>


On 09/02/23 7:47 pm, Vitaly Kuznetsov wrote:
> Alex Bennée <alex.bennee@linaro.org> writes:
>
>> "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 for Ccing me.
>
> Hyper-V features should appear in QMP since
>
> commit 071ce4b03becf9e2df6b758fde9609be8ddf56f1
> Author: Vitaly Kuznetsov <vkuznets@redhat.com>
> Date:   Tue Jun 8 14:08:13 2021 +0200
>
>      i386: expand Hyper-V features during CPU feature expansion time
>
> also, the support for Hypre-V feature discovery was just added to
> libvirt:
>
> 903ea9370d qemu_capabilities: Report Hyper-V Enlightenments in domcapabilities
> 10f4784864 qemu_capabilities: Query for Hyper-V Enlightenments
> ff8731680b qemuMonitorJSONGetCPUModelExpansion: Introduce @hv_passthrough argument
> 7c12eb2397 qemuMonitorJSONMakeCPUModel: Introduce @hv_passthrough argument
> 7c1ecfd512 domain_capabilities: Expose Hyper-V Enlightenments
> 179e45d237 virDomainCapsEnumFormat: Retrun void
> a7789d9324 virDomainCapsEnumFormat: Switch to virXMLFormatElement()
>
> in case this is not enough, could you please elaborate on the use-case
> you have in mind?
>

Thanks Vitaly, Alex,

Yes this should work. Sorry I checked qemu master code but not sure how i missed this :).

Thanks

Manish Mishra



      reply	other threads:[~2023-02-10  8:44 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
2023-02-09 14:17     ` Vitaly Kuznetsov
2023-02-10  8:42       ` manish.mishra [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=92f5f388-f635-a455-c48a-b604058cb09f@nutanix.com \
    --to=manish.mishra@nutanix.com \
    --cc=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=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).