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:
vectors of virtio-scsi-pci will be 0 when set vectors>=129.
Version-Release number of selected component (if applicable):
3.10.0-123.el7.x86_64
qemu-kvm-1.5.3-60.el7_0.2.x86_64
How reproducible:
100%
Steps to Reproduce:
1.boot qemu-kvm with following cli:
# /usr/libexec/qemu-kvm -device virtio-scsi-pci,id=scsi0,vectors=129 -monitor stdio -nodefaults
2.using "info qtree" to check the value of vectors of virtio-scsi-pci.
(qemu)info qtree
3.
Actual results:
vector of virtio-scsi-pci will be 0.
Expected results:
If vectors need <=128, when boot qemu-kvm with vectors >=129, could give some hints. Just like when set vectors with 10000000000, qemu-kvm will give hints like followings:
# /usr/libexec/qemu-kvm -device virtio-scsi-pci,id=scsi0,vectors=10000000000 -monitor stdio -nodefaults
QEMU 1.5.3 monitor - type 'help' for more information
(qemu) qemu-kvm: -device virtio-scsi-pci,id=scsi0,vectors=10000000000: Parameter 'vectors' expects uint32_t
Additional info:
Reproduced with qemu-kvm-1.5.3-60.el7.x86_64.rpm. Same step as reporter.
Actual Result:
# /usr/libexec/qemu-kvm -device virtio-scsi-pci,id=scsi0,vectors=129 -monitor stdio -nodefaults
QEMU 1.5.3 monitor - type 'help' for more information
(qemu) VNC server running on `::1:5900'
(qemu) info qtree
bus: main-system-bus
type System
dev: kvm-ioapic, id ""
gpio-in 24
gsi_base = 0
irq 0
mmio 00000000fec00000/0000000000001000
dev: i440FX-pcihost, id ""
pci-hole64-size = 16777216.000T
irq 0
bus: pci.0
type PCI
dev: virtio-scsi-pci, id "scsi0"
ioeventfd = on
vectors = 0
^^^
Verified pass with qemu-kvm-1.5.3-77.el7.x86_64.rpm. It complaint failure to initialize NO. of vectors greater than 128.
Actual Result:
# /usr/libexec/qemu-kvm -device virtio-scsi-pci,id=scsi0,vectors=129 -monitor stdio -nodefaults
QEMU 1.5.3 monitor - type 'help' for more information
(qemu) qemu-kvm: -device virtio-scsi-pci,id=scsi0,vectors=129: unable to init
^^^^^^^^^^^^^^
msix vectors to 129
^^^^^^^^^^^^^^^^^^^
VNC server running on `::1:5900'
(qemu) info qtree
bus: main-system-bus
type System
dev: kvm-ioapic, id ""
gpio-in 24
gsi_base = 0
irq 0
mmio 00000000fec00000/0000000000001000
dev: i440FX-pcihost, id ""
pci-hole64-size = 16777216.000T
irq 0
bus: pci.0
type PCI
dev: virtio-scsi-pci, id "scsi0"
ioeventfd = on
vectors = 0
As per above, this issue has fixed correctly.
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-2015-0349.html