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:
Can't boot from the system img when boot guest with 38 virtio-blk-pci disks via pci-bridge, if boot with 18,35,36,37 virtio-blk-pci disks via pci-bridge work well
Preparation:
Exist system IMG:/home/RHEL-Server-7.0-64.qcow2
#for((i=1;i<40;i++));do qemu-img create -f qcow2 /home/disk$i 100M;done
Version-Release number of selected component (if applicable):
Host:
]# uname -r
3.10.0-86.el7.x86_64
# rpm -q qemu-kvm
qemu-kvm-1.5.3-48.el7.x86_64
# rpm -q seabios
seabios-1.7.2.2-11.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Boot guest with shell script max_bridge_device.sh.
#sh max_bridge_device.sh 38
...
# cat max_bridge_device.sh
#!/bin/sh
MACHINE=pc-i440fx-rhel7.0.0
MEM=4G
IMG=/home/RHEL-Server-7.0-64.qcow2
CLI="/usr/libexec/qemu-kvm -vga none -net none -M $MACHINE -smp 4,core=2,thread=2,socket=1 -m $MEM -name vm1 -vnc :1 -vga qxl -monitor stdio -device pci-bridge,chassis_nr=1,id=bridge0,addr=0x08 -drive file=$IMG,if=none,id=hd,format=qcow2,werror=stop,rerror=stop -device virtio-blk-pci,scsi=off,drive=hd,id=os-disk,bus=bridge0,addr=0x01,bootindex=1 -serial unix:/tmp/bridge-con,server,nowait -boot menu=on,reboot-timeout=10 -monitor stdio"
while [ ${i:=1} -lt ${1:-0} ]
do
createBr=$((i%31))
bridgeId=$((i/31))
slotId=$((i%31+1))
if [ $createBr -eq 0 ]
then
CLI="$CLI -device pci-bridge,chassis_nr=$((bridgeId+1)),id=bridge$bridgeId,addr=0x$(printf "%02x" $((bridgeId+2)))"
fi
CLI="$CLI -drive file=/home/disk/disk$i,if=none,id=disk$i"
CLI="$CLI -device virtio-blk-pci,bus=bridge$bridgeId,drive=disk$i,id=blk$i,addr=0x$(printf "%02x" $slotId)"
((i++))
done
$CLI
2.Press F12,will show 7 virtio disks on the seabios boot menu, this is correct(see bug1034072 C#9)--->see attachment
3.Press 1,try to boot the guest
Actual results:
Can't boot from the system IMG. will show
"Boot failed:not a bootable disk"
Expected results:
Can boot from the system IMG
Additional info:
(In reply to Gerd Hoffmann from comment #4)
> please retest with 1.7.5 seabios builds:
> http://people.redhat.com/ghoffman/bz1101500/
Still hit this issue again with above private build.
host info:
3.10.0-128.el7.x86_64
qemu-kvm-rhev-1.5.3-60.el7ev.x86_64
seabios-1.7.5-1.el7_0.bz1101500.3.x86_64
Best Regards,
sluo
(In reply to Gerd Hoffmann from comment #6)
> Guess seabios simply runs out of memory then. Can I can a seabios log
> please?
Hi Sluo,
Can you add comment?
Best Regards,
Junyi
(In reply to Ronen Hod from comment #7)
> Gerd, in any case there will be a limitation due to seabios memory. Maybe we
> just need to document it.
We did this already ;)
*** This bug has been marked as a duplicate of bug 1034072 ***
Description of problem: Can't boot from the system img when boot guest with 38 virtio-blk-pci disks via pci-bridge, if boot with 18,35,36,37 virtio-blk-pci disks via pci-bridge work well Preparation: Exist system IMG:/home/RHEL-Server-7.0-64.qcow2 #for((i=1;i<40;i++));do qemu-img create -f qcow2 /home/disk$i 100M;done Version-Release number of selected component (if applicable): Host: ]# uname -r 3.10.0-86.el7.x86_64 # rpm -q qemu-kvm qemu-kvm-1.5.3-48.el7.x86_64 # rpm -q seabios seabios-1.7.2.2-11.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.Boot guest with shell script max_bridge_device.sh. #sh max_bridge_device.sh 38 ... # cat max_bridge_device.sh #!/bin/sh MACHINE=pc-i440fx-rhel7.0.0 MEM=4G IMG=/home/RHEL-Server-7.0-64.qcow2 CLI="/usr/libexec/qemu-kvm -vga none -net none -M $MACHINE -smp 4,core=2,thread=2,socket=1 -m $MEM -name vm1 -vnc :1 -vga qxl -monitor stdio -device pci-bridge,chassis_nr=1,id=bridge0,addr=0x08 -drive file=$IMG,if=none,id=hd,format=qcow2,werror=stop,rerror=stop -device virtio-blk-pci,scsi=off,drive=hd,id=os-disk,bus=bridge0,addr=0x01,bootindex=1 -serial unix:/tmp/bridge-con,server,nowait -boot menu=on,reboot-timeout=10 -monitor stdio" while [ ${i:=1} -lt ${1:-0} ] do createBr=$((i%31)) bridgeId=$((i/31)) slotId=$((i%31+1)) if [ $createBr -eq 0 ] then CLI="$CLI -device pci-bridge,chassis_nr=$((bridgeId+1)),id=bridge$bridgeId,addr=0x$(printf "%02x" $((bridgeId+2)))" fi CLI="$CLI -drive file=/home/disk/disk$i,if=none,id=disk$i" CLI="$CLI -device virtio-blk-pci,bus=bridge$bridgeId,drive=disk$i,id=blk$i,addr=0x$(printf "%02x" $slotId)" ((i++)) done $CLI 2.Press F12,will show 7 virtio disks on the seabios boot menu, this is correct(see bug1034072 C#9)--->see attachment 3.Press 1,try to boot the guest Actual results: Can't boot from the system IMG. will show "Boot failed:not a bootable disk" Expected results: Can boot from the system IMG Additional info: