Bug 869116

Summary:	[virtio-win][block]The guest does hibernate and hits 9F BSOD issue while guest is undergoing pressure of crystal and iozone.
Product:	Red Hat Enterprise Linux 6	Reporter:	Min Deng <mdeng>
Component:	virtio-win	Assignee:	Vadim Rozenfeld <vrozenfe>
Status:	CLOSED NEXTRELEASE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.4	CC:	acathrow, bcao, bsarathy, ghammer, juzhang, mdeng, michen, rhod, virt-bugs
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-08-01 08:59:11 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:
Bug Depends On:
Bug Blocks:	896495

Description Min Deng 2012-10-23 05:33:28 UTC

Description of problem:
The guest will hit BSOD(9F) while guest is undergoing crystal disk mark and iozone testing.

Version-Release number of selected component (if applicable):
virtio-win-prewhql-0.1-41

How reproducible:
3 times /1 reproduced

Steps to Reproduce:
1.boot up guest with the following CLI -
  /usr/libexec/qemu-kvm -m 2G -smp 2 -cpu host,+x2apic -usb -device usb-tablet -drive file=win2k8-R2.qcow2,format=qcow2,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none -device virtio-blk-pci,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device e1000,netdev=hostnet0,mac=10:10:1a:75:59:03,bus=pci.0,addr=0x4 -uuid `uuidgen` -rtc base=localtime -no-kvm-pit-reinjection -monitor stdio -name win2k8-64-fun -device virtio-balloon-pci,addr=0x6,bus=pci.0,id=balloon1 -chardev socket,id=111a,path=/tmp/monitor-win2k8-64-balloon-30,server,nowait -mon chardev=111a,mode=readline -cdrom /home/en_windows_server_2008_r2_standard_enterprise_datacenter_and_web_with_sp1_x64_dvd_617601.iso -drive file=disk1.qcow2,format=qcow2,if=none,id=drive-virtio1,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio1,id=virtio-blk-pci1 -drive file=disk2.qcow2,format=qcow2,if=none,id=drive-virtio2,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio2,id=virtio-blk-pci2 -drive file=disk3.qcow2,format=qcow2,if=none,id=drive-virtio3,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio3,id=virtio-blk-pci3 -drive file=disk4.qcow2,format=qcow2,if=none,id=drive-virtio4,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio4,id=virtio-blk-pci4 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -spice disable-ticketing,port=5931 -vga qxl
2.install crystal disk mark and iozone and testing driver via the two third-party software in the guest.
3.do S3 for the guest (need installing qxl for the guest)
Notes,
Running two crystal disk mark for at least 2 disks at the same time.
Actual results:
The guest can hibernate&resume successfully.

Expected results:
It take much time for the guest to hibernate,and at last the guest got an BSOD error(9F).

Additional info:
QE will put dump files to win-team share folder after a while.

Comment 3 Min Deng 2012-10-23 08:59:02 UTC

cache=none/writeback/writethrough can reproduce the bug.

Comment 5 Gal Hammer 2013-03-14 15:02:11 UTC

Taking the risk of repeating myself :-).

Is it possible that the crash occurs even without the running the crystal disk mark and iozone testing? A simpler scenario which check if the disks are accessible after suspend/hibernate.

And does the SeaBIOS fix from bug 912561 fix the problem?

Comment 6 Ronen Hod 2013-03-14 17:10:51 UTC

I think that Vadim said that it does not reproduce with upstream SeaBIOS.
Vadim, is it true?

Comment 7 Vadim Rozenfeld 2013-03-15 08:51:02 UTC

(In reply to comment #6)
> I think that Vadim said that it does not reproduce with upstream SeaBIOS.
> Vadim, is it true?

I believe that is was mentioned several times before, the problem is not related to the crystal disk mark. Start->hibernate->resume->hibernate sequence without any additional manipulations in between should be enough to bring the system down. The problem is easily reproducible on a system with two virtio-scsi drives
(one system, one non-system). the problem also can be reproduced on virtio-blk,
but they need to be operating in IRQ mode. It is not reproducible in MSI mode.

And, yes. I tried both of them - scsi and block. With upstream BIOS they work good.

Comment 8 Mike Cao 2013-03-15 08:54:22 UTC

dawu ,

pls re-test this issue on the seabios attached in Bug 912561

Comment 9 Mike Cao 2013-03-18 07:56:13 UTC

(In reply to comment #8)
> dawu ,
> 
> pls re-test this issue on the seabios attached in Bug 912561

Since https://bugzilla.redhat.com/show_bug.cgi?id=912561 cause lots of driver BOSD ,We could like to keep this one open and reverify it after Bug 912561 fixed .

Comment 10 Mike Cao 2013-07-19 03:29:51 UTC

dengmin ,pls retest it on the latest virtio-win/ qemu-kvm-rhev/seabios package

Comment 12 Ronen Hod 2013-07-29 09:22:04 UTC

QE,
We suspect that it is a regression that is already reported in several other bugs.
Can you please try the new BIOS and 6.4 drivers.
Thanks.

Comment 13 Mike Cao 2013-07-31 06:46:15 UTC

(In reply to Ronen Hod from comment #12)
> QE,
> We suspect that it is a regression that is already reported in several other
> bugs.
> Can you please try the new BIOS and 6.4 drivers.
> Thanks.

Dengmin ,Pls retest w/ virtio-win-1.6.5_5 & seabios-28

Comment 14 Min Deng 2013-08-01 08:47:38 UTC

(In reply to Mike Cao from comment #13)
> (In reply to Ronen Hod from comment #12)
> > QE,
> > We suspect that it is a regression that is already reported in several other
> > bugs.
> > Can you please try the new BIOS and 6.4 drivers.
> > Thanks.
> 
> Dengmin ,Pls retest w/ virtio-win-1.6.5_5 & seabios-28

Hi Mike,
  Re-test the build via w/ virtio-win-1.6.5_6 & seabios-28,I cannot reproduce the issue.The guest works well from my opinions.
Thanks,
Min