Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1452603 - can't bootup from image when attached multi-virtio-scsi disks with multi-luns
can't bootup from image when attached multi-virtio-scsi disks with multi-luns
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: seabios (Show other bugs)
7.4
Unspecified Unspecified
high Severity medium
: rc
: ---
Assigned To: Paolo Bonzini
FuXiangChun
: Regression, Reopened, ZStream
Depends On:
Blocks: 1497066 1497071
  Show dependency treegraph
 
Reported: 2017-05-19 06:16 EDT by Xueqiang Wei
Modified: 2018-04-10 10:28 EDT (History)
13 users (show)

See Also:
Fixed In Version: seabios-1.10.2-5.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1497066 1497071 (view as bug list)
Environment:
Last Closed: 2018-04-10 10:26:48 EDT
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)
cmd file (51.64 KB, text/plain)
2017-05-19 06:16 EDT, Xueqiang Wei
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0814 None None None 2018-04-10 10:28 EDT

  None (edit)
Description Xueqiang Wei 2017-05-19 06:16:10 EDT
Created attachment 1280366 [details]
cmd file

Description of problem:

can't bootup from image when attached multi-virtio-scsi disks with multi-luns


Version-Release number of selected component (if applicable):
host:
kernel-3.10.0-666.el7.x86_64
qemu-kvm-rhev-2.9.0-5.el7

guest: 
kernel-3.10.0-666.el7.x86_64


How reproducible:
100%


Steps to Reproduce:
1. run test.sh (refer to the attachment)

Actual results:
can't bootup from image


Expected results:
bootup normally


Additional info:
Not hit this issue on RHEL.7.3:
kernel-3.10.0-514.16.1.el7.x86_64
qemu-kvm-rhev-2.6.0-28.el7_3.9

Not hit this issue:
qemu-kvm-rhev-2.9.0-3.el7
qemu-kvm-rhev-2.9.0-4.el7
Comment 2 Karen Noel 2017-05-22 07:33:46 EDT
Please provide qemu-kvm command line used. Thanks.
Comment 3 Fam Zheng 2017-05-22 08:00:03 EDT
Please, attach the boot image as LUN 0. In your command it is pointing to stg0.qcow2.
Comment 4 Xueqiang Wei 2017-06-13 04:53:51 EDT
set lun=0 for boot image also can not bootup normally.

It is seabios issue:
Not hit this issue on below version:
seabios-1.10.2-2.el7.x86_64.rpm
seabios-bin-1.10.2-2.el7.noarch.rpm
seavgabios-bin-1.10.2-2.el7.noarch.rpm


Hit this issue on:
seabios-1.10.2-3.el7.x86_64.rpm
seabios-bin-1.10.2-3.el7.noarch.rpm
seavgabios-bin-1.10.2-3.el7.noarch.rpm
Comment 11 Paolo Bonzini 2017-07-07 10:12:51 EDT
These patches were rejected upstream:
https://www.mail-archive.com/seabios@seabios.org/msg10086.html

The suggestion is to allocate virtqueue info in high memory, which would allow virtio drivers to support more drives.  However, I'm not sure that it would support the full amount used in this testcase (it could still go out of memory).
Comment 12 Paolo Bonzini 2017-09-27 11:01:15 EDT
The upstream maintainer developed an alternative patchset that works with ~900 disks and can be backported easily to RHEL.
Comment 14 Miroslav Rezanina 2017-10-20 06:41:57 EDT
Fix included in seabios-1.10.2-5.el7
Comment 16 FuXiangChun 2017-11-28 04:01:16 EST
Reproduced this bug with seabios-1.10.2-4.el7.x86_64 & seabios-1.10.2-3.el7.x86_64 & qemu-kvm-rhev-2.10.0-7.el7.x86_64 

steps:

use script test.sh in attachment

result:

can't bootup from image

Verified bug with seabios-1.10.2-7.el7.x86_64 & qemu-kvm-rhev-2.10.0-7.el7.x86_64 

Result:

All disks can be found inside guest. and guest works well
Comment 17 FuXiangChun 2017-11-28 04:03:13 EST
According to comment16. This bug is fixed. And set this bug as verified.
Comment 20 errata-xmlrpc 2018-04-10 10:26:48 EDT
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://access.redhat.com/errata/RHBA-2018:0814

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