Bug 2080095
| Summary: | [ESXi][RHEL8.7]Bring VMCI up to date with upstream | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | ldu <ldu> |
| Component: | kernel | Assignee: | Cathy Avery <cavery> |
| kernel sub component: | ESXi | QA Contact: | Bo Yang <boyang> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | aadam, boyang, bryantan, cavery, eterrell, gchua, jsavanyo, jwolfe, ldu, vdasa, yacao, yanjin, zackr |
| Version: | 8.6 | Keywords: | OtherQA, Triaged |
| Target Milestone: | rc | ||
| Target Release: | 8.7 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | kernel-4.18.0-401.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 2079153 | Environment: | |
| Last Closed: | 2022-11-08 10:30:32 UTC | Type: | Bug |
| 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: | 2079153 | ||
| Bug Blocks: | |||
|
Description
ldu
2022-04-29 01:48:21 UTC
Similar to 2079153, could we also please back port the following patch?
13. ba03a9bbd17b149c373c0ea44017f35fc2cd0f28 ("VMCI: Release resource if the work is already queued")
As this feature requires an unreleased hardware version of VMware VM, would it be possible to provide us rpms which we can use to test and report back? It would be great if that is possible. Thanks again! Vishnu (In reply to vdasa from comment #5) > As this feature requires an unreleased hardware version of VMware VM, would > it be > possible to provide us rpms which we can use to test and report back? It > would > be great if that is possible. > > Thanks again! > Vishnu Here, https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=45361396 provides the RPMs for your testing. Currently, we will not be supporting ARM on 8.7, please test them with X86_64 RPMs ONLY by installing an appropriate RHEL firstly and upgrading them. If you can't access above link, will provide http://people.redhat.com/ to share later. Hi Vishnu, Please get the kernel build from this link: https://people.redhat.com/ldu/kernel/bz2080095/ Thanks, Lili Du (In reply to ldu from comment #8) > Hi Vishnu, > Please get the kernel build from this link: > https://people.redhat.com/ldu/kernel/bz2080095/ > > Thanks, > Lili Du Thank you @ldu! We have done some testing and it looks good on x86. Having the source rpm will allow us to do some additional testing. Is that something you can share with us? We will use that to compile a test driver kernel module. Thanks, Vishnu (In reply to vdasa from comment #9) > (In reply to ldu from comment #8) > > Hi Vishnu, > > Please get the kernel build from this link: > > https://people.redhat.com/ldu/kernel/bz2080095/ > > > > Thanks, > > Lili Du > > Thank you @ldu! We have done some testing and it looks good on x86. Having > the > source rpm will allow us to do some additional testing. Is that something > you can > share with us? We will use that to compile a test driver kernel module. > > Thanks, > Vishnu Vishnu, Thanks for you update! I have upload the source rpm, please check and download. Thanks, Lili Du (In reply to ldu from comment #10) > Vishnu, > Thanks for you update! > I have upload the source rpm, please check and download. > > Thanks, > Lili Du Thank you, Lili! We have completed our vmci/vsock testing for this version of RHEL and it looks good from our perspective. Thanks, Vishnu Lili or Bo could you set the ITM. Thanks Verified this issue in 4.18.0-400.el8.mr2918_220613_1140.g9ca7 with regression test.
ENV:
Host: VMware ESXi, 6.5.0, 19092475
Guest: RHEL with 4.18.0-400.el8.mr2918_220613_1140.g9ca7
Steps to Verify:
1. Upgrades to above target Guest.
2. Runs and passes vsock_v2 and vmci_doorbell_test_v3.
if you have specific cases or steps to check or try, let me know.
Verified this issue in 4.18.0-402.el8.x86_64 with regression test.
ENV:
Host: VMware ESXi, 7.0.3, 19482537
Guest: RHEL with 4.18.0-402.el8.x86_64
Steps to Verify:
1. Upgrades to above target Guest.
2. Checks below steps:
-------------
[root@bootp-73-199-135 ~]# uname -r
4.18.0-402.el8.x86_64
[root@bootp-73-199-135 ~]# lsmod | grep vmci
vmw_vsock_vmci_transport 32768 1
vsock 49152 5 vmw_vsock_virtio_transport_common,vsock_loopback,vmw_vsock_vmci_transport
vmw_vmci 86016 2 vmw_balloon,vmw_vsock_vmci_transport
-------------
3. Launches and passes "vsock_v2" test suites in Guest (client / server mode) and ESXi Server (server / client mode).
if you have specific cases or steps to check OR vmware team needs to retest it with 4.18.0-402.el8.x86_64, please let me know.
Thank you, Bo. No retesting required from our side. Regards, Vishnu UPDATE: Updated parts of incorrect information in Comment 19: Verified this issue in kernel-4.18.0-402.el8 with regression test. ENV: Host: VMware ESXi, 6.5.0, 19092475 / Intel(R) Xeon(R) Gold 5218 CPU @ 2.30GHz Guest: RHEL with kernel-4.18.0-402.el8 Steps to Verify: 1. Upgraded to above target Guest. 2. Checked below steps: ------------- [root@bootp-73-199-135 ~]# uname -r 4.18.0-402.el8.x86_64 [root@bootp-73-199-135 ~]# lsmod | grep vmci vmw_vsock_vmci_transport 32768 1 vsock 49152 5 vmw_vsock_virtio_transport_common,vsock_loopback,vmw_vsock_vmci_transport vmw_vmci 86016 2 vmw_balloon,vmw_vsock_vmci_transport ------------- 3. Launches and passes "vsock_v2" test suites in Guest (client / server mode) and ESXi Server (server / client mode). Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: kernel security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:7683 |