Bug 1461676
Summary: | nvdimm hot-unplug support - libvirt | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux Advanced Virtualization | Reporter: | chhu | |
Component: | libvirt | Assignee: | Virtualization Maintenance <virt-maint> | |
Status: | CLOSED WONTFIX | QA Contact: | Jing Qi <jinqi> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | --- | CC: | dyuan, hpopal, jsuchane, kanderso, knoel, lhuang, mtessun, rbalakri, xuzhang, yalzhang | |
Target Milestone: | rc | Keywords: | FutureFeature, Triaged | |
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1499124 (view as bug list) | Environment: | ||
Last Closed: | 2021-01-15 07:38:11 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: | 1499124 | |||
Bug Blocks: | 1473046 |
Description
chhu
2017-06-15 07:14:22 UTC
So there are two problems here: Firstly, libvirt needs to start qemu with '-M nvdimm=on' otherwise nvdimm hotplug is not possible. However, libvirt can't know in advance if users will want to hotplug a nvdimm some time in the future. I guess we can't just add nvdimm=on unconditionally (well, for those qemus which support it) as it might change guest ABI, right? BTW, in my testing I successfully migrated from no nvdimm to nvdimm=on; but my testing might be limited. Secondly, in my testing, after I patched libvirt to enable nvdimm unconditionally I was able to hotplug a NVDIMM module but was unable to detach it afterwards: error: internal error: unable to execute QEMU command 'device_del': nvdimm device hot unplug is not supported yet. Looks like hotunplug is not implemented yet. I'll create a separate bug for that. There's some discussion happening on the upstream list: https://www.redhat.com/archives/libvir-list/2017-September/msg00328.html 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. |