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.

Bug 981723

Summary: RHEL guest( sata disk ) can not boot up
Product: Red Hat Enterprise Linux 7 Reporter: langfang <flang>
Component: qemu-kvmAssignee: Fam Zheng <famz>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: urgent    
Version: 7.0CC: acathrow, calestyo, dyuan, flang, hhuang, juzhang, lcui, mrezanin, qiguo, qzhang, sluo, tzheng, virt-maint, xwei
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qemu-kvm-1.5.2-2.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 11:09:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
the entire log
none
the entire log for boot rhel6 guest none

Description langfang 2013-07-05 15:15:34 UTC 
Description of problem:

Fail to boot up guest(sata disk).

Version-Release number of selected component (if applicable):

Host:
# uname -r 
3.10.0-0.rc7.64.el7.x86_64
# rpm -q qemu-kvm
qemu-kvm-1.5.1-2.el7.x86_64

Guest:
3.10.0-0.rc7.64.el7.x86_64

How reproducible:

100%

Steps to Reproduce:
1.Boot up guest
 /usr/libexec/qemu-kvm  -M  q35 -cpu SandyBridge -enable-kvm -m 4096 -smp 4,sockets=2,cores=2,threads=1 -no-kvm-pit-reinjection -name flang -uuid `uuidgen` -rtc base=localtime,clock=host,driftfix=slew -drive file=/root/flang/RHEL-7.0-20130628.0-Server-x86_64.qcow3,format=qcow2,if=none,id=drive-ide0-0-0,format=qcow2,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0  -k en-us  -serial unix:/tmp/ttyS0,server,nowait -spice port=5800,disable-ticketing -vga std -monitor stdio


Actual results:
#nc -U /tmp/ttyS0
...
[   95.363291] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[   95.363291] sd 0:0:0:0: [sda] CDB: 
[   95.363293] Read(10): 28 00 01 90 3c 98 00 00 08 00
[   95.363302] sd 0:0:0:0: [sda] Unhandled error code
[   95.363302] sd 0:0:0:0: [sda]  
[   95.363302] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[   95.363303] sd 0:0:0:0: [sda] CDB: 
[   95.363305] Read(10): 28 00 01 90 3c a0 00 00 08 00
[   95.363313] sd 0:0:0:0: [sda] Unhandled error code
[   95.363313] sd 0:0:0:0: [sda]  
[   95.363314] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[   95.363314] sd 0:0:0:0: [sda] CDB: 
[   95.363316] Read(10): 28 00 01 90 3c a8 00 00 08 00
[   95.363324] sd 0:0:0:0: [sda] Unhandled error code
[   95.363324] sd 0:0:0:0: [sda]  
[   95.363325] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[   95.363325] sd 0:0:0:0: [sda] CDB: 
[   95.363327] Read(10): 28 00 01 90 3c b0 00 00 08 00
[   95.363337] sd 0:0:0:0: [sda] Unhandled error code
[   95.363338] sd 0:0:0:0: [sda]  
[   95.363338] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[   95.363339] sd 0:0:0:0: [sda] CDB: 
[   95.363340] Read(10): 28 00 01 90 3c b8 00 00 08 00
[   95.363349] sd 0:0:0:0: [sda] Unhandled error code
[   95.363350] sd 0:0:0:0: [sda]  

...
[  125.188618] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[  125.190231] sd 0:0:0:0: [sda] CDB: 
[  125.191359] Read(10): 28 00 00 91 49 a0 00 00 08 00
[  125.193818] blk_update_request: 234 callbacks suppressed
[  125.195209] end_request: I/O error, dev sda, sector 9521568
[  125.196664] EXT4-fs warning (device dm-1): __ext4_read_dirblock:1375: error reading directory block (ino 131075, block 1)


Expected results:

Guest boot up successfully.

Additional info:
1) The entire log see attachment
2)If boot guest use scsi_hd disk and virtio-blk not see the problem
Comment 1 langfang 2013-07-05 15:20:54 UTC 
Created attachment 769287 [details]
the entire log
Comment 3 langfang 2013-07-08 02:21:15 UTC 
Created attachment 770232 [details]
the entire log for boot rhel6 guest
Comment 4 langfang 2013-07-08 05:28:38 UTC 
If install a new guest use sata disk,can not install.

Version:
Host:
# uname -r 
3.10.0-0.rc7.64.el7.x86_64
# rpm -q qemu-kvm
qemu-kvm-1.5.1-2.el7.x86_64

1.Boot guest with 

..-M q35 -drive file=/root/flang/rhel6.4-newinstall,format=qcow2,if=none,id=drive-ide0-0-0,format=qcow2,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2...


Error: NO usable disks have been found.


addtional info : Also can not install rhel7
Comment 5 langfang 2013-07-08 06:15:55 UTC 
Test this bug on qemu-kvm-1.5.1-0.el7.x86_64 and  qemu-kvm-1.5.1-1.el7.x86_64

Host:

3.10.0-0.rc6.63.el7.x86_64

qemu-kvm:

qemu-kvm-1.5.0-2.el7.x86_64--->pass
 
qemu-kvm-1.5.1-1.el7.x86_64--->fail,hit the same problem

qemu-kvm-1.5.1-2.el7.x86_64--->fail

   So this is a regression bug . qemu-kvm-1.5.1-1.el7.x86_64  version bring the regression.
Comment 6 juzhang 2013-07-08 06:18:12 UTC 
According to comment5, add "Regression" keywords.
Comment 8 Hai Huang 2013-07-09 18:54:41 UTC 
Regression introduced in qemu 1.5.1.  Not clear if regression was due to 
a code change in the block layer in 1.5.1, or introduced with the rebase.
Comment 9 Fam Zheng 2013-07-10 09:36:51 UTC 
This should be an upstream bug that is introduced with rebase:

http://lists.nongnu.org/archive/html/qemu-devel/2013-07/msg00690.html

commit 0565700d7859bca6cb0e74c3c98f5fd1201559b5
ide: Set BSY bit during FLUSH

    The implementation of the ATA FLUSH command invokes a flush at the block
    layer, which may on raw files on POSIX entail a synchronous fdatasync().
    This may in some cases take so long that the SLES 11 SP1 guest driver
    reports I/O errors and filesystems get corrupted or remounted read-only.

    Avoid this by setting BUSY_STAT, so that the guest is made aware we are
    in the middle of an operation and no ATA commands are attempted to be
    processed concurrently.

    (cherry picked from commit f68ec8379e88502b4841a110c070e9b118d3151c)
Comment 10 Christoph Anton Mitterer 2013-07-25 12:48:56 UTC 
Hi.

Is this the same as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717724

?
Comment 11 Miroslav Rezanina 2013-07-31 12:02:44 UTC 
Fix included in qemu-kvm-1.5.2-2.el7
Comment 12 Miroslav Rezanina 2013-07-31 12:08:55 UTC 
Fix included in qemu-kvm-1.5.2-2.el7
Comment 13 Ademar Reis 2013-08-26 13:55:18 UTC 
*** Bug 985741 has been marked as a duplicate of this bug. ***
Comment 17 Ludek Smid 2014-06-13 11:09:17 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.