Bug 2224472
Summary: | [RFE] Request to expose pcie-root-port's mem-reserve option | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Yanghang Liu <yanghliu> |
Component: | libvirt | Assignee: | Virtualization Maintenance <virt-maint> |
libvirt sub component: | General | QA Contact: | Meina Li <meili> |
Status: | CLOSED MIGRATED | Docs Contact: | |
Severity: | medium | ||
Priority: | unspecified | CC: | chayang, imammedo, kraxel, lmen, meili, mprivozn, virt-maint, xuwei, yalzhang, yanqzhan, yuma |
Version: | 9.3 | Keywords: | FutureFeature, MigratedToJIRA, Triaged |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-09-22 17:20:37 UTC | Type: | Story |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Yanghang Liu
2023-07-21 03:53:10 UTC
Adding the knob should be fairly trivial. But what I am wondering about is how users know the value to pass, or - whether there is an automated way for libvirt to select the correct value automagically, without user intervention (which then might create a problem on its own, e.g. during migration because I bet this knob is part of guest ABI). Gerd? Igor? (In reply to Michal Privoznik from comment #2) > Adding the knob should be fairly trivial. But what I am wondering about is > how users know the value to pass, or - whether there is an automated way for > libvirt to select the correct value automagically, without user intervention > (which then might create a problem on its own, e.g. during migration because > I bet this knob is part of guest ABI). Gerd? Igor? I don't think there is an easy way to do this automatically. This is needed for hotplugging devices with large mmio bars (large memory bars are essentially solved with the dynamic mmio window changes). So you have to look at the device you want eventually hotplug into the guest to figure the size needed. Coldplugged devices are no problem, for those the firmware can adjust the bridge windows as needed automatically. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |