Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1095645 - vectors of virtio-scsi-pci will be 0 when set vectors>=129
vectors of virtio-scsi-pci will be 0 when set vectors>=129
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm (Show other bugs)
7.0
x86_64 Linux
low Severity low
: rc
: ---
Assigned To: Fam Zheng
Virtualization Bugs
:
: 1099277 (view as bug list)
Depends On:
Blocks: 1143825
  Show dependency treegraph
 
Reported: 2014-05-08 05:28 EDT by Jun Li
Modified: 2015-03-05 03:06 EST (History)
8 users (show)

See Also:
Fixed In Version: qemu-kvm-1.5.3-67.el7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1143825 (view as bug list)
Environment:
Last Closed: 2015-03-05 03:06:59 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0349 normal SHIPPED_LIVE Important: qemu-kvm security, bug fix, and enhancement update 2015-03-05 07:27:34 EST

  None (edit)
Description Jun Li 2014-05-08 05:28:16 EDT
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:
Comment 2 Amos Kong 2014-08-04 02:52:34 EDT
*** Bug 1099277 has been marked as a duplicate of this bug. ***
Comment 3 Jeff Nelson 2014-08-08 12:55:04 EDT
Fix included in qemu-kvm-1.5.3-67.el7
Comment 5 Chao Yang 2014-10-27 05:52:17 EDT
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.
Comment 8 errata-xmlrpc 2015-03-05 03:06:59 EST
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

Note You need to log in before you can comment on or make changes to this bug.