Bug 1299194

Summary:	guest didn't resume after iscsi server recover with iozone tool running in the guest
Product:	Red Hat Enterprise Linux 6	Reporter:	jingzhao <jinzhao>
Component:	qemu-kvm	Assignee:	Fam Zheng <famz>
Status:	CLOSED NOTABUG	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.8	CC:	ailan, chayang, juzhang, kwolf, mkenneth, rbalakri, virt-maint, xfu, yama
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1301814 (view as bug list)		Environment:
Last Closed:	2016-02-01 04:37:47 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:
Bug Depends On:
Bug Blocks:	1301814

Description jingzhao 2016-01-17 08:05:19 UTC

Description of problem:
guest didn't resume after iscsi server recover with iozone tool running in the guest, and hmp prompt error message "block I/O error in device 'drive-virtio-scsi': Read-only file system (30)"

Version-Release number of selected component (if applicable):
kernel-2.6.32-599.el6.x86_64
qemu-kvm-0.12.1.2-2.483.el6.x86_64

How reproducible:
3/3
Steps to Reproduce:

pre: prepare the iscsi server, mount the iscsi server disk as local disk
# iscsi client:iscsiadm -m discovery -t sendtargets -p IPaddress
# iscsi client: iscsiadm --mode node --targetname targetname --portal IPaddress:3260 --login
# iscsi client: mount /dev/sd* /media

1.Boot the guest with following cli:

/usr/libexec/qemu-kvm \
-name rhel6.6.0 \
-machine rhel6.6.0,accel=kvm \
-realtime mlock=off \
-cpu Westmere \
-m 4G   \
-smp 4,cores=2,threads=1,sockets=2  \
-uuid 49a3438a-70a3-4ba8-92ce-3a05e0934608 \
-nodefaults \
-rtc base=utc,driftfix=slew \
-monitor unix:/tmp/monitor-unix,server,nowait \
-global kvm-pit.lost_tick_policy=discard \
-global PIIX4_PM.disable_s3=1 \
-global PIIX4_PM.disable_s4=1 \
-boot order=c,menu=on,strict=on \
-device virtio-scsi-pci,id=scsi \
-drive file=/media/win10blk.raw,if=none,format=raw,id=drive-virtio-scsi,werror=stop,rerror=stop \
-device scsi-hd,drive=drive-virtio-scsi,id=virtio-scsi,bus=scsi.0 \
-drive file=/mnt/test1.qcow2,if=none,id=disk1,format=qcow2,aio=threads,cache=none \
-device scsi-hd,bus=scsi.0,drive=disk1,id=virtio-scsi-disk \
-drive file=/usr/share/virtio-win/virtio-win-1.7.5.iso,if=none,media=cdrom,id=drive-ide1,format=raw \
-device ide-drive,bus=ide.0,unit=1,drive=drive-ide1,id=ide1 \
-cdrom en_windows_10_enterprise_x64_dvd_6851151.iso \
-netdev tap,id=hostnet1  \
-device e1000,netdev=hostnet1,id=virtio-net-pci1,mac=b6:2f:a8:85:72:6c,bus=pci.0,multifunction=off \
-monitor stdio \
-qmp tcp:0:4469,server,nowait -serial unix:/tmp/ttym,server,nowait \
-vga qxl \
-spice port=5913,addr=0.0.0.0,disable-ticketing,seamless-migration=on \
-k en-us \

2. running iozone tools in the guest

3. service iscsi stop

4. check the guest status in the hmp
(qemu) info status
VM status: paused (io-error)

5. service iscsi start and resume the guest in the monitor 

Actual results:
guest didn't resume 

(qemu) info status
VM status: paused (io-error)
(qemu) cont
(qemu) block I/O error in device 'drive-virtio-scsi': Read-only file system (30)
block I/O error in device 'drive-virtio-scsi': Read-only file system (30)


Expected results:
guest can resume successfully and no error occurs

Additional info:

Comment 2 jingzhao 2016-01-25 08:33:57 UTC

Reproduced with kernel-2.6.32-573.19.1.el6.x86_64 and qemu-kvm-0.12.1.2-2.479.el6_7.2.x86_64 (guest: rhel6) , so i think it's not a regression issue.

Comment 3 Fam Zheng 2016-02-01 04:37:47 UTC

The iscsi lun is marked read only after iscsi server stop. You need to remount it read-write again.