Bug 2044162
| Summary: | [RHEL9.1] Enable virtio-mem as tech-preview on ARM64 QEMU | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Guowen Shan <gshan> |
| Component: | qemu-kvm | Assignee: | Guowen Shan <gshan> |
| qemu-kvm sub component: | General | QA Contact: | Zhenyu Zhang <zhenyzha> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | david, eric.auger, jherrman, lijin, mrezanin, virt-maint, yihyu, zhenyzha |
| Version: | 9.1 | Keywords: | FutureFeature, Reopened, Triaged |
| Target Milestone: | rc | Flags: | gshan:
needinfo-
gshan: needinfo- pm-rhel: mirror+ |
| Target Release: | 9.1 | ||
| Hardware: | aarch64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | qemu-kvm-7.0.0-2.el9 | Doc Type: | If docs needed, set a value |
| Doc Text: |
See https://bugzilla.redhat.com/show_bug.cgi?id=2014487
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-11-15 09:53:29 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: | 2044155 | ||
| Bug Blocks: | 1924294, 2044172, 2047797 | ||
|
Description
Guowen Shan
2022-01-24 07:20:06 UTC
The QEMU patches have been merged to upstream. https://www.mail-archive.com/qemu-devel@nongnu.org/msg861122.html b1b87327a9 hw/arm/virt: Support for virtio-mem-pci 1263615efe virtio-mem: Correct default THP size for ARM64 This depends on the work to enable virtio-mem in kernel, which is tracked by bug 2044155 Zhenyu, virtio-mem device is available now from the following package. I also tried the 'qemu-kvm' binary and virtio-mem works as expected. https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=44837626 Thanks, Gavin Removed Fixed in version as this BZ require additional changes. Testing, will update the results later. Hello Gavin, According to comment11-14 I think virtio-mem verification is complete, Since this patch has been merged into downstream so I want to set the bug as closed currentrelease. What do you think? Hello Miroslav, Sorry to bother you. Although this bug has actually been verified, but according to Workflow QE needs to wait for the bug to become ON_QA before setting verify. So I reverted the bug to the previous MODIFIED state and set Verified: tested Please help to change the bug status. (In reply to Zhenyu Zhang from comment #18) > Hello Miroslav, > > Sorry to bother you. > Although this bug has actually been verified, but according to Workflow QE > needs to wait for the bug to become ON_QA before setting verify. > So I reverted the bug to the previous MODIFIED state and set Verified: tested > Please help to change the bug status. Thanks for info, Zhenyu. I'll take care of the BZ. 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: qemu-kvm 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:7967 |