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:
boot a rhel9 guest with q35 and 192 virtio-blk-pci disk, only 154 virtio-blk-pci disk in guest.
It is found that dmesg has failed information as follows:
[ 52.085410] virtio_blk: probe of virtio155 failed with error -28
...
[ 52.154213] virtio_blk: probe of virtio192 failed with error -28
[ 52.377887] ahci: probe of 0000:00:1f.2 failed with error -28
[ 63.998924] i801_smbus 0000:00:1f.3: Failed to allocate irq 16: -28
Version-Release number of selected component (if applicable):
host version:
kernel-5.14.0-45.el9.x86_64
qemu-kvm-6.2.0-4.el9.x86_64
seabios-1.15.0-1.el9.x86_64
guest: rhel900-64-virtio-scsi.qcow2
How reproducible:
100%
Steps to Reproduce:
1. Boot up with qemu command line [1]
2. Check disks in guest
# fdisk -l | grep /dev/vd | wc -l
154
Actual results:
After step 2, Disk number is incorrect in guest.
Expected results:
After step 2, Disk number should be equal to 192 and dmesg has no fail message.
Additional info:
[1] command line:
#!/bin/sh
MACHINE=q35
SMP=4,cores=2,threads=2,sockets=1
MEM=10G
GUEST_IMG=/home/kvm_autotest_root/images/rhel900-64-virtio-scsi.qcow2
IMG_FORMAT=qcow2
CLI="/usr/libexec/qemu-kvm -enable-kvm -M $MACHINE -nodefaults -smp $SMP -m $MEM -name vm1 -vga std -device virtio-scsi-pci,id=scsi0,bus=pcie.0 -blockdev node-name=file_image1,driver=file,auto-read-only=on,discard=unmap,aio=threads,filename=$GUEST_IMG,cache.direct=on,cache.no-flush=off -blockdev node-name=drive_image1,driver=$IMG_FORMAT,read-only=off,cache.direct=on,cache.no-flush=off,file=file_image1 -device scsi-hd,id=sysdisk,drive=drive_image1,bus=scsi0.0,bootindex=0 -vnc :1 -monitor stdio -boot menu=on,reboot-timeout=8,strict=on -serial unix:/tmp/console,server,nowait "
declare -i f=1
for((i=4;i<=6;i++))
do
k=`printf "%x\n" $i`
for ((j=0;j<=7;j++))
do
CLI="$CLI -device pcie-root-port,bus=pcie.0,id=root.$i.$j,slot=$f,chassis=$f,multifunction=on,addr=0x$k.$j"
for((z=0;z<=7;z++))
do
qemu-img create -f qcow2 /home/disk/disk.$i.$j.$z 1G
if [ "$k.$j" == "1f.3" ]
then
continue
fi
CLI="$CLI -blockdev driver=qcow2,node-name=disk.$i.$j.$z,file.driver=file,file.filename=/home/disk/disk.$i.$j.$z"
CLI="$CLI -device virtio-blk-pci,scsi=off,drive=disk.$i.$j.$z,id=virtio-blk$i.$j.$z,bus=root.$i.$j,multifunction=on,addr=0x0.$z"
done
f=$f+1
done
done
$CLI
Hit this bug with rhel8.7.0 guest on rhel8.7.0 host
host version:
kernel-4.18.0-393.el8.x86_64
qemu-kvm-6.2.0-14.module+el8.7.0+15289+26b4351e.x86_64
seabios-1.16.0-1.module+el8.7.0+15006+42c9ed21.x86_64
guest: rhel8.7.0
Hit this bug with rhel9.2.0 guest on rhel9.2.0 host
host version:
kernel-5.14.0-265.el9.x86_64
qemu-kvm-7.2.0-8.el9.x86_64
edk2-ovmf-20221207gitfff6d81270b5-5.el9.noarch
guest: rhel9.2.0
Looks like the same problem as in bug 1949813.
E.g. bumping into IRQ limit. Since virtio interrupts are not shared, there's not much we can do here.
A workaround would be to limit number of IRQs per block device:
-global virtio-blk-pci.vectors=4
or
<qemu:commandline>
<qemu:arg value='-global'/>
<qemu:arg value='virtio-blk-pci.vectors=4'/>
</qemu:commandline>
*** This bug has been marked as a duplicate of bug 1949813 ***
Description of problem: boot a rhel9 guest with q35 and 192 virtio-blk-pci disk, only 154 virtio-blk-pci disk in guest. It is found that dmesg has failed information as follows: [ 52.085410] virtio_blk: probe of virtio155 failed with error -28 ... [ 52.154213] virtio_blk: probe of virtio192 failed with error -28 [ 52.377887] ahci: probe of 0000:00:1f.2 failed with error -28 [ 63.998924] i801_smbus 0000:00:1f.3: Failed to allocate irq 16: -28 Version-Release number of selected component (if applicable): host version: kernel-5.14.0-45.el9.x86_64 qemu-kvm-6.2.0-4.el9.x86_64 seabios-1.15.0-1.el9.x86_64 guest: rhel900-64-virtio-scsi.qcow2 How reproducible: 100% Steps to Reproduce: 1. Boot up with qemu command line [1] 2. Check disks in guest # fdisk -l | grep /dev/vd | wc -l 154 Actual results: After step 2, Disk number is incorrect in guest. Expected results: After step 2, Disk number should be equal to 192 and dmesg has no fail message. Additional info: [1] command line: #!/bin/sh MACHINE=q35 SMP=4,cores=2,threads=2,sockets=1 MEM=10G GUEST_IMG=/home/kvm_autotest_root/images/rhel900-64-virtio-scsi.qcow2 IMG_FORMAT=qcow2 CLI="/usr/libexec/qemu-kvm -enable-kvm -M $MACHINE -nodefaults -smp $SMP -m $MEM -name vm1 -vga std -device virtio-scsi-pci,id=scsi0,bus=pcie.0 -blockdev node-name=file_image1,driver=file,auto-read-only=on,discard=unmap,aio=threads,filename=$GUEST_IMG,cache.direct=on,cache.no-flush=off -blockdev node-name=drive_image1,driver=$IMG_FORMAT,read-only=off,cache.direct=on,cache.no-flush=off,file=file_image1 -device scsi-hd,id=sysdisk,drive=drive_image1,bus=scsi0.0,bootindex=0 -vnc :1 -monitor stdio -boot menu=on,reboot-timeout=8,strict=on -serial unix:/tmp/console,server,nowait " declare -i f=1 for((i=4;i<=6;i++)) do k=`printf "%x\n" $i` for ((j=0;j<=7;j++)) do CLI="$CLI -device pcie-root-port,bus=pcie.0,id=root.$i.$j,slot=$f,chassis=$f,multifunction=on,addr=0x$k.$j" for((z=0;z<=7;z++)) do qemu-img create -f qcow2 /home/disk/disk.$i.$j.$z 1G if [ "$k.$j" == "1f.3" ] then continue fi CLI="$CLI -blockdev driver=qcow2,node-name=disk.$i.$j.$z,file.driver=file,file.filename=/home/disk/disk.$i.$j.$z" CLI="$CLI -device virtio-blk-pci,scsi=off,drive=disk.$i.$j.$z,id=virtio-blk$i.$j.$z,bus=root.$i.$j,multifunction=on,addr=0x0.$z" done f=$f+1 done done $CLI