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.
Descriptionyalzhang@redhat.com
2020-05-07 11:59:58 UTC
Description of problem:
Hot-plug interface into the pcie-downstream-port controller will disappear after a while
Version-Release number of selected component (if applicable):
# rpm -q libvirt qemu-kvm
libvirt-6.0.0-18.module+el8.2.1+6456+a6d62e4e.x86_64
qemu-kvm-4.2.0-20.module+el8.2.1+6467+49dc3278.x86_64
It can also be reproduced on rhel8.2.0 av:
# rpm -q libvirt-libs qemu-kvm
libvirt-libs-6.0.0-17.module+el8.2.0+6257+0d066c28.x86_64
qemu-kvm-4.2.0-19.module+el8.2.0+6296+6b821950.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Prepare an vm with pcie-switch-upstream-port and pcie-switch-downstream-port controller:
# virsh dumpxml vm2
...
<controller type='pci' index='0' model='pcie-root'/>
...
<controller type='pci' index='7' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='7' port='0x16'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/>
</controller>
<controller type='pci' index='8' model='pcie-switch-upstream-port'>
<model name='x3130-upstream'/>
<address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
</controller>
<controller type='pci' index='9' model='pcie-switch-downstream-port'>
<model name='xio3130-downstream'/>
<target chassis='9' port='0x0'/>
<address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
</controller>
...
2. Start the vm, hotplug interface to the downstream port:
# virsh start vm2
# cat net.xml
<interface type='network'>
<mac address='52:54:11:22:33:44'/>
<source network='default'/>
<model type='virtio'/>
<address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/>
</interface>
# virsh domiflist vm2
Interface Type Source Model MAC
-------------------------------------------------------------
vnet0 network default virtio 52:54:00:86:f7:83
# virsh attach-device vm2 net.xml ; virsh domiflist vm2 ; sleep 5; echo "after sleep 5"; virsh domiflist vm2
Device attached successfully
Interface Type Source Model MAC
-------------------------------------------------------------
vnet0 network default virtio 52:54:00:86:f7:83
vnet1 network default virtio 52:54:11:22:33:44
after sleep 5
Interface Type Source Model MAC
-------------------------------------------------------------
vnet0 network default virtio 52:54:00:86:f7:83
3. check on guest, there are error prompted:
[root@localhost ~]# [ 740.394901] pcieport 0000:08:00.0: Slot(0-7): Attention button pressed
[ 740.399225] pcieport 0000:08:00.0: Slot(0-7) Powering on due to button press
[ 740.403163] pcieport 0000:08:00.0: Slot(0-7): Card present
[ 740.405830] pcieport 0000:08:00.0: Slot(0-7): Link Up
[ 741.536309] pcieport 0000:08:00.0: link training error: status 0x2000
[ 741.539890] pcieport 0000:08:00.0: Failed to check link status
Actual results:
In step2, the interface disappeared after hotplug successfully
Expected results:
The interface should not disappear on the guest. If the hotplug is not supported, it should report error during hotplug
Additional info:
I'm pretty sure this behavior was reported in a previous BZ - basically the pcie-downstream-port is for some reason unplugged by the Linux kernel some time after the guest OS boots. I don't know if this is a problem with the emulated controller in qemu, or with the guest kernel (seems more likely the former).
Description of problem: Hot-plug interface into the pcie-downstream-port controller will disappear after a while Version-Release number of selected component (if applicable): # rpm -q libvirt qemu-kvm libvirt-6.0.0-18.module+el8.2.1+6456+a6d62e4e.x86_64 qemu-kvm-4.2.0-20.module+el8.2.1+6467+49dc3278.x86_64 It can also be reproduced on rhel8.2.0 av: # rpm -q libvirt-libs qemu-kvm libvirt-libs-6.0.0-17.module+el8.2.0+6257+0d066c28.x86_64 qemu-kvm-4.2.0-19.module+el8.2.0+6296+6b821950.x86_64 How reproducible: 100% Steps to Reproduce: 1. Prepare an vm with pcie-switch-upstream-port and pcie-switch-downstream-port controller: # virsh dumpxml vm2 ... <controller type='pci' index='0' model='pcie-root'/> ... <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0x16'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/> </controller> <controller type='pci' index='8' model='pcie-switch-upstream-port'> <model name='x3130-upstream'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='9' model='pcie-switch-downstream-port'> <model name='xio3130-downstream'/> <target chassis='9' port='0x0'/> <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </controller> ... 2. Start the vm, hotplug interface to the downstream port: # virsh start vm2 # cat net.xml <interface type='network'> <mac address='52:54:11:22:33:44'/> <source network='default'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </interface> # virsh domiflist vm2 Interface Type Source Model MAC ------------------------------------------------------------- vnet0 network default virtio 52:54:00:86:f7:83 # virsh attach-device vm2 net.xml ; virsh domiflist vm2 ; sleep 5; echo "after sleep 5"; virsh domiflist vm2 Device attached successfully Interface Type Source Model MAC ------------------------------------------------------------- vnet0 network default virtio 52:54:00:86:f7:83 vnet1 network default virtio 52:54:11:22:33:44 after sleep 5 Interface Type Source Model MAC ------------------------------------------------------------- vnet0 network default virtio 52:54:00:86:f7:83 3. check on guest, there are error prompted: [root@localhost ~]# [ 740.394901] pcieport 0000:08:00.0: Slot(0-7): Attention button pressed [ 740.399225] pcieport 0000:08:00.0: Slot(0-7) Powering on due to button press [ 740.403163] pcieport 0000:08:00.0: Slot(0-7): Card present [ 740.405830] pcieport 0000:08:00.0: Slot(0-7): Link Up [ 741.536309] pcieport 0000:08:00.0: link training error: status 0x2000 [ 741.539890] pcieport 0000:08:00.0: Failed to check link status Actual results: In step2, the interface disappeared after hotplug successfully Expected results: The interface should not disappear on the guest. If the hotplug is not supported, it should report error during hotplug Additional info: