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.
Description of problem:
libvirt limits chassisNr for pci bridge to between 0 and 255,
however, qemu does not support chassis_nr=0
Version-Release number of selected component (if applicable):
libvirt-1.3.4-1.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. edit xml and set chassisNr for pci bridge to -1
# virsh edit vm1
<controller type='pci' index='1' model='pci-bridge'>
<model name='pci-bridge'/>
<target chassisNr='-1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
</controller>
error: XML document failed to validate against schema: Unable to validate doc against /usr/share/libvirt/schemas/domain.rng
Extra element devices in interleave
Element domain failed to validate content
error: XML error: PCI controller chassisNr '-1' out of range - must be 0-255
Failed. Try again? [y,n,i,f,?]:
2. edit xml and set chassisNr for pci bridge to 0
# virsh edit vm1
<controller type='pci' index='1' model='pci-bridge'>
<model name='pci-bridge'/>
<target chassisNr='0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
</controller>
Domain vm1 XML configuration edited.
# virsh start vm1
error: Failed to start domain vm1
error: internal error: early end of file from monitor, possible problem: warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6]
warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6]
warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6]
warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6]
2016-06-06T08:26:59.778510Z qemu-kvm: -device pci-bridge,chassis_nr=0,id=pci.1,bus=pci.0,addr=0x8: Bridge chassis not specified. Each bridge is required to be assigned a unique chassis id > 0.
2016-06-06T08:26:59.779116Z qemu-kvm: -device pci-bridge,chassis_nr=0,id=pci.1,bus=pci.0,addr=0x8: Device initialization fa
Actual results:
chassis id is numbered in [1,255]
Expected results:
libvirt limits chassisNr for pci bridge to between 1 and 255, and
modify the doc
Additional info:
Pushed upstream, will be in the 2.0.0 release:
commit df2fb9bfff7906296d191de3431384b2e0729257
Author: Laine Stump <laine>
Date: Mon Jun 20 14:24:35 2016 -0400
conf: limit chassisNr, and busNr to a minimum value of 1, not 0
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2016-2577.html
Description of problem: libvirt limits chassisNr for pci bridge to between 0 and 255, however, qemu does not support chassis_nr=0 Version-Release number of selected component (if applicable): libvirt-1.3.4-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. edit xml and set chassisNr for pci bridge to -1 # virsh edit vm1 <controller type='pci' index='1' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='-1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </controller> error: XML document failed to validate against schema: Unable to validate doc against /usr/share/libvirt/schemas/domain.rng Extra element devices in interleave Element domain failed to validate content error: XML error: PCI controller chassisNr '-1' out of range - must be 0-255 Failed. Try again? [y,n,i,f,?]: 2. edit xml and set chassisNr for pci bridge to 0 # virsh edit vm1 <controller type='pci' index='1' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </controller> Domain vm1 XML configuration edited. # virsh start vm1 error: Failed to start domain vm1 error: internal error: early end of file from monitor, possible problem: warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5] warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6] warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5] warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6] warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5] warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6] warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5] warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6] 2016-06-06T08:26:59.778510Z qemu-kvm: -device pci-bridge,chassis_nr=0,id=pci.1,bus=pci.0,addr=0x8: Bridge chassis not specified. Each bridge is required to be assigned a unique chassis id > 0. 2016-06-06T08:26:59.779116Z qemu-kvm: -device pci-bridge,chassis_nr=0,id=pci.1,bus=pci.0,addr=0x8: Device initialization fa Actual results: chassis id is numbered in [1,255] Expected results: libvirt limits chassisNr for pci bridge to between 1 and 255, and modify the doc Additional info: