Bug 1851247
Summary: | Interface for querying supported HyperV Enlightenments | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Eduardo Habkost <ehabkost> |
Component: | qemu-kvm | Assignee: | Vitaly Kuznetsov <vkuznets> |
qemu-kvm sub component: | CPU Models | QA Contact: | menli <menli> |
Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
Severity: | unspecified | ||
Priority: | unspecified | CC: | ailan, blc, jinzhao, juzhang, qizhu, ribarry, virt-maint, vkuznets, yuhuang |
Version: | unspecified | Keywords: | FutureFeature, Triaged |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-12-25 07:26:57 UTC | Type: | Feature Request |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1997408 | ||
Bug Blocks: | 1624786, 1717611 |
Description
Eduardo Habkost
2020-06-25 21:54:22 UTC
This is supposed to work, but doesn't seem to work today: query-cpu-model-expansion type=full model={"name":"host","props":{"hv-passthrough":true}} Probably because hv_cpuid_check_and_set() isn't called at feature expansion time. Rick - this seems like something Vitaly would handle - although perhaps the component/sub-subcomponent/pool would need to be adjusted. Upstream work started. KVM patches suggested: https://lore.kernel.org/kvm/20200807083946.377654-1-vkuznets@redhat.com/ QEMU patches suggested: https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg02017.html We have all the required bits upstream but the series is quite big and I was wondering if it would make sense to try to backport this for 8.5 or not. Eduardo, are you aware of any particular users of this new interface? In particular, do you know if libvirt is working on a related feature? (In reply to Vitaly Kuznetsov from comment #9) > We have all the required bits upstream but the series is quite big and I was > wondering if it would make sense to try to backport this for 8.5 or not. > > Eduardo, are you aware of any particular users of this new interface? In > particular, do you know if libvirt is working on a related feature? I don't think we need it in 8.5. We were not planning to use this interface in 8.5 because we thought the hyperv=on boolean (bug 1877467) would work for us. The libvirt side of this feature is being tracked at bug 1717611. (In reply to Eduardo Habkost from comment #10) > > I don't think we need it in 8.5. We were not planning to use this interface > in 8.5 because we thought the hyperv=on boolean (bug 1877467) would work for > us. OK, I'm not backporting patches then, we'll get them with the next rebase. Thanks! Bulk update: Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release. Hi Vitaly, Whether we could move this bug to modify status, as it already works on qemu 6.1. or still wait for other related patch? details: qemp command: { "execute":"query-cpu-model-expansion","arguments":{"type":"full","model":{"name":"host","props":{"hv-passthrough":true}}}} test on qemu-kvm-6.1.0-1.module+el8.6.0+12721+8d053ff2.x86_64 before, the result is like: '.."hv-relaxed": true, "avx512-fp16": false, "hv-crash": true,..' also try it on qemu-kvm-4.2.0-59.module+el8.5.0+12817+cb650d43.x86_64 , the result is like: '.."hv-relaxed": false, "hv-crash": false..' Thanks Menghuan (In reply to menli from comment #13) > Hi Vitaly, > > Whether we could move this bug to modify status, as it already works on qemu > 6.1. Yes, let's make this TestOnly dependent on QEMU rebase to 6.1 BZ and move to ON_QA. Base on comment 13 and comment 15, change status to verified. After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. |