Bug 1963845
| Summary: | QEMU quit if set nvdimm memory backend option readonly=on | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Yumei Huang <yuhuang> |
| Component: | qemu-kvm | Assignee: | Julia Suvorova <jusual> |
| qemu-kvm sub component: | Devices | QA Contact: | Mario Casquero <mcasquer> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | chayang, dyuan, jinzhao, jusual, juzhang, lcong, mrezanin, virt-maint, yuhuang |
| Version: | unspecified | Keywords: | Triaged |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | qemu-kvm-7.2.0-1.el9 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-05-09 07:19:27 UTC | Type: | --- |
| 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: | 2135806 | ||
| Bug Blocks: | |||
|
Description
Yumei Huang
2021-05-24 07:52:22 UTC
Assigned to Amnon for initial triage per bz process and age of bug created or assigned to virt-maint without triage. BTW, if set unarmed=on, guest can boot up without error. Bulk update: Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release. Reproduced with qemu-kvm-6.1.0-1.el9. AFAIU, the logic is correct, but the error message is not, e.g. 'unarmed' property must be on when memdev is read-only. I've posted a patch upstream to fix it: [PATCH] hw/mem/nvdimm: fix error message for 'unarmed' flag I see the upstream patch from comment 5 posted as https://lists.nongnu.org/archive/html/qemu-devel/2022-05/msg06222.html with a follow-up Reviewed-by from Stefan Hajnoczi, but then the thread moves into June with Igor's https://lists.nongnu.org/archive/html/qemu-devel/2022-06/msg02474.html and a lot of subsequent discussion about transferring ownership of the component to David Hildenbrand. Perhaps just a ping to David can help get this merged... Julia - I left a needinfo on you for this... It is merged upstream now. Updating status. Manual test passed on: dell-per750-24.lab.eng.pek2.redhat.com qemu-kvm-7.2.0-1.el9.x86_64 5.14.0-212.el9.x86_64 With the following options in the qemu-kvm cmd line: -object memory-backend-file,size=1G,mem-path=/tmp/nvdimm0,share=yes,readonly=on,id=mem-mem1 \ -device nvdimm,unarmed=off,id=dimm-mem1,memdev=mem-mem1 \ Now qemu quits with the appropiate error: (qemu) qemu-kvm: -device nvdimm,unarmed=off,id=dimm-mem1,memdev=mem-mem1: 'unarmed' property must be 'on' since memdev mem-mem1 is read-only If setting 'unarmed' to 'on' then qemu works as expected NVDIMM readonly + unarmed tests passed: dell-per750-24.lab.eng.pek2.redhat.com qemu-kvm-7.2.0-1.el9.x86_64 5.14.0-212.el9.x86_64 With the following options in the qemu-kvm cmd line: -object memory-backend-file,size=1G,mem-path=/tmp/nvdimm0,share=yes,readonly=on,id=mem-mem1 \ -device nvdimm,unarmed=off,id=dimm-mem1,memdev=mem-mem1 \ Qemu quits with the appropiate error: (qemu) qemu-kvm: -device nvdimm,unarmed=off,id=dimm-mem1,memdev=mem-mem1: 'unarmed' property must be 'on' since memdev mem-mem1 is read-only If setting 'unarmed' to 'on' then qemu works as expected. 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-2023:2162 |