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.
Bug 2152130 - hotplug i40e: Cannot map registers, bar size 0x0 too small, aborting
Summary: hotplug i40e: Cannot map registers, bar size 0x0 too small, aborting
Keywords:
Status: CLOSED DUPLICATE of bug 2055123
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: qemu-kvm
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Yanghang Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-09 11:45 UTC by Dr. David Alan Gilbert
Modified: 2023-03-14 18:08 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-12 09:46:59 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-141767 0 None None None 2022-12-09 11:45:59 UTC

Description Dr. David Alan Gilbert 2022-12-09 11:45:30 UTC 
Description of problem:
I've got a 1.2T VM on an AMD box, if I hot plug one of the hosts intel i40e's into the guest, the guest shows:

[  442.520852] i40e: Intel(R) Ethernet Connection XL710 Network Driver
[  442.523054] i40e: Copyright (c) 2013 - 2019 Intel Corporation.
[  442.525247] i40e 0000:07:00.0: enabling device (0000 -> 0002)
[  442.528236] i40e 0000:07:00.0: Cannot map registers, bar size 0x0 too small, aborting
[  442.530089] i40e: probe of 0000:07:00.0 failed with error -12

it's fine if I then reboot the guest or boot it from cold

Version-Release number of selected component (if applicable):
Guest is RHEL 9.1 5.14.0-162.6.1.el9_1.x86_64
Host is 9.2:
  kernel 5.14.0-205.el9.x86_64
  qemu  qemu-kvm-common-7.2.0-0.rc4.el9.preview.x86_64

From the host:
63:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GBASE-T (rev 02)
	DeviceName: Integrated NIC 1 Port 1-1
	Subsystem: Intel Corporation Ethernet 10G 2P X710-T2L-t OCP
	Flags: fast devsel, IRQ 182, NUMA node 0, IOMMU group 57
	Memory at e0000000 (64-bit, prefetchable) [size=16M]
	Memory at e1808000 (64-bit, prefetchable) [size=32K]
	Expansion ROM at e1b00000 [disabled] [size=512K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
	Capabilities: [70] MSI-X: Enable- Count=129 Masked-
	Capabilities: [a0] Express Endpoint, MSI 00
	Capabilities: [e0] Vital Product Data
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 50-b5-f5-ff-ff-91-96-b4
	Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
	Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
	Capabilities: [1a0] Transaction Processing Hints
	Capabilities: [1b0] Access Control Services
	Capabilities: [1d0] Secondary PCI Express
	Kernel driver in use: vfio-pci
	Kernel modules: i40e

How reproducible:
2 of 2

Steps to Reproduce:
1. Create and start the VM with the attached XML
2. Hotplug the ether controller
3. wait for the memory to be locked

Actual results:
[  442.528236] i40e 0000:07:00.0: Cannot map registers, bar size 0x0 too small, aborting


Expected results:
A happy happy NIC

Additional info:
Not sure if it's actually AMD or VM size specific
Comment 3 John Ferlan 2022-12-09 16:44:33 UTC 
I see the message in KVM, "drivers/net/ethernet/intel/i40e/i40e_main.c" and it was added during with commit 'fefa9cfddf'

Jason can you please take a look and provide some feedback / thoughts? (or pass the needinfo to someone else on the kvm/networking side)
Comment 4 Yanghang Liu 2022-12-11 06:12:54 UTC 
Hi David,

It seems to me that this should be a duplicated bug of Bug 2055123 - [Q35] Failed to hot-plug a device whose membar > 2M into the vm.

Other similar bugs:
[1] Bug 2024818 - [Windows_vm][Q35+ OVMF] Some hot-plugged PF/VF can not find enough free resources that it can use
[2] Bug 2084533 - [RFE] qemu should communicate available physical address space to the guest (firmware). 

Please check and have a look.
Comment 5 Dr. David Alan Gilbert 2022-12-12 09:46:59 UTC 
(In reply to Yanghang Liu from comment #4)
> Hi David,
> 
> It seems to me that this should be a duplicated bug of Bug 2055123 - [Q35]
> Failed to hot-plug a device whose membar > 2M into the vm.

Oh yes, that seems to match the error in comment 1; I hadn't spotted the 'no space for'
and 'failed to assign' in my dmesg (they're mixed in with the timeout).

> 
> Other similar bugs:
> [1] Bug 2024818 - [Windows_vm][Q35+ OVMF] Some hot-plugged PF/VF can not
> find enough free resources that it can use

> [2] Bug 2084533 - [RFE] qemu should communicate available physical address
> space to the guest (firmware). 

I don't think it's that since it's fine except hotplug.
 
> Please check and have a look.

*** This bug has been marked as a duplicate of bug 2055123 ***
Note You need to log in before you can comment on or make changes to this bug.