From: "manish.mishra" <manish.mishra@nutanix.com>
To: qemu-devel <qemu-devel@nongnu.org>
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>
Subject: Expose support for HyperV features via QMP
Date: Tue, 31 Jan 2023 20:17:35 +0530 [thread overview]
Message-ID: <cfa1e51f-c74b-c1d1-d6ea-a25a5a5f6c4b@nutanix.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1127 bytes --]
next reply other threads:[~2023-01-31 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 14:47 manish.mishra [this message]
2023-02-01 10:42 ` Expose support for HyperV features via QMP 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
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=cfa1e51f-c74b-c1d1-d6ea-a25a5a5f6c4b@nutanix.com \
--to=manish.mishra@nutanix.com \
--cc=aravind.retnakaran@nutanix.com \
--cc=berrange@redhat.com \
--cc=carl.waldspurger@nutanix.com \
--cc=flosch@nutanix.com \
--cc=john.levon@nutanix.com \
--cc=prerna.saxena@nutanix.com \
--cc=qemu-devel@nongnu.org \
--cc=rohit.kumar3@nutanix.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).