Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMarcel Apfelbaum
2016-02-21 16:20:40 UTC
Description of problem:
If a PCI device has no driver install on a Windows guest, it will not
be part of resource re-balancing algorithm if triggered.
If the device has some BARs , the firmware already assigned to them a resource range. This is not seen by Windows and on resource re-balancing the same range
can be assigned to other PCI device.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
#cat > t << EOF
pci_update_mappings_del
pci_update_mappings_add
EOF
#./x86_64-softmmu/qemu-system-x86_64 -snapshot -enable-kvm -snapshot \
-monitor unix:/tmp/m,server,nowait -device pci-bridge,chassis_nr=1 \
-boot menu=on -m 4G -trace events=t ws2012r2x64dc.img \
-device ivshmem,id=foo,size=2M,shm,bus=pci.1,addr=01
wait till OS boots, note BARs programmed for ivshmem
in my case it was
01:01.0 0,0xfe800000+0x100
then execute script and watch pci_update_mappings* trace events
# for i in $(seq 3 18); do printf -- "device_add e1000,bus=pci.1,addr=%x\n" $i | nc -U /tmp/m; sleep 5; done;
Actual results:
hotplugging e1000,bus=pci.1,addr=12 triggers rebalancing where
Windows unmaps all BARs of nics on bridge but doesn't touch ivshmem
and then programs new BARs, where:
pci_update_mappings_add d=0x7fa02ff0cf90 01:11.0 0,0xfe800000+0x20000
creates overlapping BAR with ivshmem
Expected results:
no overlapping BARs or the ivshmem BAR should be disabled.
Description of problem: If a PCI device has no driver install on a Windows guest, it will not be part of resource re-balancing algorithm if triggered. If the device has some BARs , the firmware already assigned to them a resource range. This is not seen by Windows and on resource re-balancing the same range can be assigned to other PCI device. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: #cat > t << EOF pci_update_mappings_del pci_update_mappings_add EOF #./x86_64-softmmu/qemu-system-x86_64 -snapshot -enable-kvm -snapshot \ -monitor unix:/tmp/m,server,nowait -device pci-bridge,chassis_nr=1 \ -boot menu=on -m 4G -trace events=t ws2012r2x64dc.img \ -device ivshmem,id=foo,size=2M,shm,bus=pci.1,addr=01 wait till OS boots, note BARs programmed for ivshmem in my case it was 01:01.0 0,0xfe800000+0x100 then execute script and watch pci_update_mappings* trace events # for i in $(seq 3 18); do printf -- "device_add e1000,bus=pci.1,addr=%x\n" $i | nc -U /tmp/m; sleep 5; done; Actual results: hotplugging e1000,bus=pci.1,addr=12 triggers rebalancing where Windows unmaps all BARs of nics on bridge but doesn't touch ivshmem and then programs new BARs, where: pci_update_mappings_add d=0x7fa02ff0cf90 01:11.0 0,0xfe800000+0x20000 creates overlapping BAR with ivshmem Expected results: no overlapping BARs or the ivshmem BAR should be disabled.