Bug 1261859

Summary: disable-legacy=on option cause guest can not read the boot disk
Product: Red Hat Enterprise Linux 7 Reporter: Yiqian Wei <yiwei>
Component: qemu-kvm-rhevAssignee: jason wang <jasowang>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: medium    
Version: 7.2CC: chayang, juzhang, knoel, michen, qiguo, qzhang, virt-maint, yiwei
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-09-16 03:19:16 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
guest screen none

Description Yiqian Wei 2015-09-10 10:30:42 UTC 
Description of problem:
Boot guest with virtio-blk-pci or virtio-scsi-pci and disable-legacy=on. guest can not read the boot disk. If set disable-legacy=off, then guest works well.

Version-Release number of selected component (if applicable):
host kernel:3.10.0-314.el7.x86_64
qemu version: qemu-kvm-rhev-2.3.0-22.el7.x86_64
seabios :seabios-1.7.5-11.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1./usr/libexec/qemu-kvm -M pc-i440fx-rhel7.2.0 -cpu SandyBridge \
-enable-kvm -m 2G -smp 4 -name rhel7.2 \

-rtc base=localtime,clock=host,driftfix=slew -uuid 6afa5f93-2d4f-420f-81c6-e5fdddbd1c83 -spice disable-ticketing,port=5931 -monitor stdio \

-drive file=/home/rhel7.2-new.qcow2,if=none,id=drive-scsi-disk,format=qcow2,cache=none,werror=stop,rerror=stop  -device virtio-blk-pci,disable-legacy=off,drive=drive-scsi-disk \

-vnc :11

2.vncviewer 10.66.10.61:11


Actual results:
guest boot fail. can not read boot disk

Expected results:
works

Additional info:
Comment 1 Yiqian Wei 2015-09-10 10:34:19 UTC 
Created attachment 1072082 [details]
guest screen
Comment 4 jason wang 2015-09-16 03:19:16 UTC 
Looks a duplicated to me.

*** This bug has been marked as a duplicate of bug 1243364 ***