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.

Bug 720905

Summary: Unable to add another hadrware after adding PCI device for eth0 to a virt guest
Product: Red Hat Enterprise Linux 6 Reporter: Eduard Benes <ebenes>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: high    
Version: 6.1CC: mzhan, rwu
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-09-22 15:05:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eduard Benes 2011-07-13 08:11:25 UTC
Description of problem:
It is not possible to add a new hardware to a virt guest after PCI device for eth0 has been assigned already to a virt guest. The system is configure for PCI device assignement [1], so far untested on a system without active VT-d extensions.

Version-Release number of selected component (if applicable):
virt-manager-0.8.6-4.el6.noarch
libvirt-0.8.7-18.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. Configure system for PCI device assignement by enabling VT-d extensions [1]
2. Add PCI device for eth0 to a virt guest (details -> Add Hardware ...)
3. Try to add another hadware
  
Actual results:
Not able to "add hardware" to a virt guest.
Error messages in /var/log/messages:

Jul 12 08:58:03 dhcp-25-23 libvirtd: 08:58:03.346: 1935: error : interfaceGetXMLDesc:355 : internal error could not get interface XML description (netcf: NETLINK socket operation failed - couldn't find ifindex for interface `eth0`)

Expected results:
Able to "add hardware" to a virt guest.

Additional info:

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/Virtualization/index.html#chap-Virtualization-PCI_passthrough

Comment 1 Cole Robinson 2011-07-20 23:53:50 UTC
Are you seeing an explicit error message raised? If so please provide it.

Better yet, please provide the full output of virt-manager --debug when reproducing this issue. If the error is occuring when trying to start an existing VM, please provide the contents of /var/log/libvirt/qemu/$vmname.log

Comment 2 Cole Robinson 2011-09-22 15:05:46 UTC
No info for 2 months, closing as INSUFFICIENT_DATA. If you are still hitting this issue with latest packages, please reopen with the info requested in comment 1.