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.
Hi, vivian, I can't reproduce it, could you confirm if the PF is already in use by domain xp-sp3 and other domains? If it's in use, then it's the expected error.
hm, failed to reproduce it now . But now as you told me , when the pf is occupied by other process I'll meet the same error as the bug shows . So it is the right thing .
Close this bug as NOTABUG
Description of problem: Tried to hotplug the 82599 PF to XP guest, will get following prompt in host terminal , which tells the failure to hotplug . But in the guest , it already recognized there is the new hardware inserted . Version-Release number of selected component (if applicable): libvirt-0.8.7-17.el6.x86_64 kernel-2.6.32-132.el6.x86_64 qemu-kvm-0.12.1.2-2.158.el6.x86_64 How reproducible: Always Steps to Reproduce: 1.# virsh nodedev-list --tree | +- pci_0000_28_00_1 | | | | | +- net_eth0_00_1b_21_8e_b2_b9 | +- pci_0000_28_10_1 | | | | | +- net_eth6_42_66_b1_01_fa_fd | | | +- pci_0000_28_10_1 | | | +- net_eth7_ba_b4_dd_5c_5b_dd 2.# virsh nodedev-dumpxml pci_0000_28_00_1 <device> <name>pci_0000_28_00_1</name> <parent>pci_0000_00_07_0</parent> <driver> <name>ixgbe</name> </driver> <capability type='pci'> <domain>0</domain> <bus>40</bus> <slot>0</slot> <function>1</function> <product id='0x10fb'>82599EB 10-Gigabit SFI/SFP+ Network Connection</product> <vendor id='0x8086'>Intel Corporation</vendor> <capability type='virt_functions'> <address domain='0x0000' bus='0x28' slot='0x10' function='0x1'/> <address domain='0x0000' bus='0x28' slot='0x10' function='0x3'/> </capability> </capability> </device> 3.# cat pf.xml <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address bus='40' slot='0' function='1'/> </source> </hostdev> 4. # virsh attach-device xp-sp3 pf.xml error: Failed to attach device from pf.xml error: internal error Not detaching active device 0000:28:00.1 5.# virsh nodedev-list --tree | +- pci_0000_28_00_1 and no VF found under the tree for pci_0000_28_00_1 Actual results: Expected results: Additional info: