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.
After upgrade to Redhat 6.2 libvirt-0.9.4-23.el6_2.1.x86_64
libvirt fails to start any guest:
# virsh start mock5
error: Failed to start domain mock5
error: internal error unable to reserve PCI address 0:0:2.0
had to revert back to libvirt-0.8.7-18.el6.x86_64 to resolve the issue
Can you please provide the daemon logs and mock5 XML?
That error message you are getting means that PCI address was already taken/reserved for other device.
To get logs, in /etc/libvirt/libvirtd.conf
log_level=1
MAY set log_filters="3:remote 4:event"
log_outputs="1:file:/var/log/libvirtd.log"
Vadym,
your problem is related to https://bugzilla.redhat.com/show_bug.cgi?id=692355
In the fix for that bug, we had to unconditionally reserve PCI address 0:0:2.0 for a graphic card (even if there is currently none). See that bug.
To solve your problem you need to change PCI address of interface. So either edit <address> element and change slot to say '0x05' or remove the whole element and libvirt will generate it for you.
However, I am setting needinfo flag, so you can confirm it is working for you.
Yes, it did help, thank you.
I created a new VM just to compare configuration files and I see where slot 0x2 was added:
<video>
<model type='cirrus' vram='9216' heads='1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</video>
Since this issue is resolved, I am closing this. I agree that behavior during upgrade is not user friendly. However, it should be documented in errata for 692355 that PCI address 0:0:2.0 is reserved.