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.
Bug 1329526 - seabios can not recognize virtio 1.0 virtual block
Summary: seabios can not recognize virtio 1.0 virtual block
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.3
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Gerd Hoffmann
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-22 07:41 UTC by yduan
Modified: 2016-11-07 21:05 UTC (History)
10 users (show)

Fixed In Version: qemu-2.6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-07 21:05:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2673 0 normal SHIPPED_LIVE qemu-kvm-rhev bug fix and enhancement update 2016-11-08 01:06:13 UTC

Description yduan 2016-04-22 07:41:23 UTC 
Description of problem:
seabios can not recognize virtio 1.0 virtual block

Version-Release number of selected component (if applicable):
Host:
  kernel: 3.10.0-382.el7.x86_64
  qemu-kvm-rhev: qemu-kvm-rhev-2.5.0-4.el7.x86_64
  seabios-1.9.1-2.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Install a VM with following commands:
 ...
 -drive file=/home/backup/rhel7.2released/RHEL-7.2-20151030.0-Server-x86_64-dvd1.iso,if=none,media=cdrom,id=drive_cd,readonly=on,format=raw \
 -device ide-cd,bus=ide.0,drive=drive_cd,id=device_cd \
 -drive file=test.qcow2,format=qcow2,id=drive_sysdisk,if=none,cache=none,aio=native,werror=stop,rerror=stop \
 -device virtio-blk-pci,bus=pci.0,disable-legacy=on,disable-modern=off,drive=drive_sysdisk,id=test \
 -boot order=dcn,once=d \
 ...

Actual results:
Before installation started, anaconda failed to find the hard disk. At this time, switch to console by 'Ctrl + Alt + F2', 'fdisk -l' didn't see the disk either.

Expected results:
Seabios should recognize the hard disk specified in qemu-kvm command line.

Additional info:
Not reproducible with seabios-1.7.5-11.el7.x86_64
Comment 3 Gerd Hoffmann 2016-04-28 08:21:55 UTC 
I guess that is the virtio reset issue, qemu commit:

75fd6f1 virtio-pci: call pci reset variant when guest requests reset.

Triggered by newer seabios because it supports virtio 1.0 and therefore
the device is in a different state when the linux kernel detects devices.
Comment 4 Yanan Fu 2016-05-16 09:30:10 UTC 
--------------------- reproduce ---------------------
kernel:kernel-3.10.0-396.el7.x86_64
qemu:qemu-kvm-rhev-2.5.0-4.el7.x86_64
seabios:seabios-1.9.1-2.el7.x86_64


1.install a vm with cmd:

...
-drive file=/root/rhel7-blk.qcow2,id=drive-blk-disk,media=disk,format=qcow2,cache=none,if=none \
-device virtio-blk-pci,drive=drive-blk-disk,bus=pci.0,addr=0x4,id=blk-disk,disable-legacy=on,disable-modern=off,bootindex=1 \
-drive file=/root/RHEL-7.2-20151027.3-Server-x86_64-dvd1.iso,if=none,id=drive-cd,media=cdrom,format=raw,cache=none \
-device virtio-blk-pci,drive=drive-cd,bus=pci.0,addr=0x6,id=cdrom,bootindex=0 \
...

2.In bootmenu, can see both cdrom(the first one) and disk(the second one), choose to install from cdrom.
3.Begin to install,anaconda failed to find the hard disk.
4.Switch to console by 'Ctrl + Alt + F2', '#fdisk -l' can not output the disk too. 


reproduce this bug successfully.


---------------------- verify -----------------------

version:
kernel:kernel-3.10.0-396.el7.x86_64
qemu:qemu-kvm-rhev-2.6.0-1.el7.x86_64
seabios:seabios-1.9.1-2.el7.x86_64

1.install a vm with cmd:

...
-drive file=/root/rhel7-blk.qcow2,id=drive-blk-disk,media=disk,format=qcow2,cache=none,if=none \
-device virtio-blk-pci,drive=drive-blk-disk,bus=pci.0,addr=0x4,id=blk-disk,disable-legacy=on,disable-modern=off,bootindex=1 \
-drive file=/root/RHEL-7.2-20151027.3-Server-x86_64-dvd1.iso,if=none,id=drive-cd,media=cdrom,format=raw,cache=none \
-device virtio-blk-pci,drive=drive-cd,bus=pci.0,addr=0x6,id=cdrom,bootindex=0 \
...

2.In bootmenu, can see both cdrom(the first one) and disk(the second one), choose to install from cdrom.
3.Begin to install,anaconda can find the hard disk.
4.Switch to console by 'Ctrl + Alt + F2', '#fdisk -l' can see the disk. 


As the test result above, with same kernel and seabios version, qemu-kvm-rhev-2.5.0-4.el7.x86_64 hit this issue, but qemu-kvm-rhev-2.6.0-1.el7.x86_64 is ok.so I think this bug has been fixed in qemu-kvm-rhev-2.6.0-1.el7.x86_64.
Comment 8 errata-xmlrpc 2016-11-07 21:05:18 UTC 
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/RHBA-2016-2673.html
Note You need to log in before you can comment on or make changes to this bug.