Bug 720566 - [WHQL][viostor]Common Scenarios Stress With DiskIO always failed[windows2k3]
Summary: [WHQL][viostor]Common Scenarios Stress With DiskIO always failed[windows2k3]
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virtio-win
Version: 6.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Vadim Rozenfeld
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-12 04:33 UTC by Min Deng
Modified: 2014-07-11 06:51 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-08 10:22:30 UTC
Target Upstream Version:

Attachments (Terms of Use)
successful run log (165.36 KB, text/plain)
2011-07-13 03:10 UTC, Min Deng 		no flags Details
Failure info (575.19 KB, application/zip)
2011-11-04 05:27 UTC, Min Deng 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Comment 2 Min Deng 2011-07-12 05:51:51 UTC 
Created attachment 512335 [details]
Logs from DTM
Comment 3 Min Deng 2011-07-12 05:53:27 UTC 
Provide command line for the guest
/usr/libexec/qemu-kvm -m 2G -smp 2 -cpu cpu64-rhel6,+x2apic -usbdevice tablet -drive file=win2k8-32-blk.raw,if=none,id=drive-virtio0,boot=on,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio0,id=virtio-blk-pci0 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device e1000,netdev=hostnet0,mac=00:11:1c:13:49:22,bus=pci.0,addr=0x4 -boot c -uuid e79de7ac-8d00-42c0-8f79-649906ad3147 -rtc-td-hack -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-w2k8-32-blk,server,nowait -mon chardev=111a,mode=readline -name win2k8-32-blk -vnc :1 -drive file=disk1.raw,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.raw,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.raw,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.raw,if=none,id=drive-virtio4,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio4,id=virtio-blk-pci4
Comment 4 Vadim Rozenfeld 2011-07-12 11:55:36 UTC 
(In reply to comment #2)
> Created attachment 512335 [details]
> Logs from DTM

Can I see the same DTM report acquired from
a successful run?

Best regards,
Vadim.
Comment 5 Min Deng 2011-07-13 03:10:45 UTC 
Created attachment 512553 [details]
successful run log

Attached DTM logs of a successful run,any issue please let me know.thanks.
Comment 6 Ronen Hod 2011-07-13 06:03:52 UTC 
Trying to prioritize.
Since it fails sometimes, can we pass WHQL without fixing it?
Comment 7 Min Deng 2011-07-13 07:22:25 UTC 
   Even if some guests passed this job we had better fix the issue now.Because this issue will block some guests.For example,on window 2k8-32 guest,tester execute 4 times but job still failed and window2k8-R2 had the same issue.
   In order to make our virtio-win driver more stronger and our WHQL testing more smoothly,would you please double check this issue.Any issues please let me know,thanks in advance.

Best Regards
Min Deng
Comment 8 Vadim Rozenfeld 2011-07-13 08:02:33 UTC 
(In reply to comment #7)
>    Even if some guests passed this job we had better fix the issue now.Because
> this issue will block some guests.For example,on window 2k8-32 guest,tester
> execute 4 times but job still failed and window2k8-R2 had the same issue.
>    In order to make our virtio-win driver more stronger and our WHQL testing
> more smoothly,would you please double check this issue.Any issues please let me
> know,thanks in advance.
> 
> Best Regards
> Min Deng

Thank you, Min Deng.
It was very useful. Seems like, in some cases, on resume after hibernate, the system time goes backward. Asked Gled to look into the problem.
Best regards,
Vadim.
Comment 9 Mike Cao 2011-07-29 05:25:29 UTC 
Add testblocker keyword since it is 100% reprociable .
Comment 10 Mike Cao 2011-07-29 05:31:39 UTC 
Created attachment 515827 [details]
DTM log tested on RHEL5u5 host

Hi,

The log attached is doing this job on RHEL5.5 host.
anything need I do pls let me know 

Thanks,
Mike
Comment 12 Vadim Rozenfeld 2011-07-29 07:30:06 UTC 
Hi Mike,

Please install device driver for the following device 
'PCI\VEN_1B36&DEV_0105&SUBSYS_11001AF4&REV_01'
 
Best regards,
Vadim.
Comment 13 Vadim Rozenfeld 2011-08-11 06:56:52 UTC 
Hi Mike,
Did you try it with the VDI Port driver installed?

Cheers,
Vadim.
Comment 14 Min Deng 2011-08-25 07:26:03 UTC 
(In reply to comment #13)
> Hi Mike,
> Did you try it with the VDI Port driver installed?
> 
> Cheers,
> Vadim.

Hi Vadim,

   To be honest,QE didn't hit the issue with driver virtio-win-prewhql-0.1-15.And could you please tell me how to have VDI Port driver installed ? 

Thanks,
Min
Comment 15 Vadim Rozenfeld 2011-08-25 08:43:47 UTC 
(In reply to comment #14)
> (In reply to comment #13)
> > Hi Mike,
> > Did you try it with the VDI Port driver installed?
> > 
> > Cheers,
> > Vadim.
> 
> Hi Vadim,
> 
>    To be honest,QE didn't hit the issue with driver
> virtio-win-prewhql-0.1-15.And could you please tell me how to have VDI Port
> driver installed ? 
> 
> Thanks,
> Min

Hi Min,

VDI Port was a part of SPICE host-to-guest communication solution. In 5.5 vdi port and qxl drivers should go together. It's deprecated now and replaced by one of virtio-serial channels. You shouldn't see it on 6.0 and higher, and according to comment #10, the problem happened  on 5.5

Best regards,
Vadim.
Comment 16 Vadim Rozenfeld 2011-09-12 08:59:54 UTC 
(In reply to comment #14)
> (In reply to comment #13)
> > Hi Mike,
> > Did you try it with the VDI Port driver installed?
> > 
> > Cheers,
> > Vadim.
> 
> Hi Vadim,
> 
>    To be honest,QE didn't hit the issue with driver
> virtio-win-prewhql-0.1-15.

Hi Min,
Can we close this bug?
Best regards,
Vadim.

And could you please tell me how to have VDI Port
> driver installed ? 
> 
> Thanks,
> Min
Comment 17 Min Deng 2011-09-15 02:54:21 UTC 
(In reply to comment #16)
> (In reply to comment #14)
> > (In reply to comment #13)
> > > Hi Mike,
> > > Did you try it with the VDI Port driver installed?
> > > 
> > > Cheers,
> > > Vadim.
> > 
> > Hi Vadim,
> > 
> >    To be honest,QE didn't hit the issue with driver
> > virtio-win-prewhql-0.1-15.
> 
> Hi Min,
> Can we close this bug?
> Best regards,
> Vadim.
> 
> And could you please tell me how to have VDI Port
> > driver installed ? 
> > 
> > Thanks,
> > Min

Hi Vadim,

   As the new driver comes we had better test the bug via the virtio-win-prewhql-0.1-16.

Thanks
Min Deng
Comment 18 dawu 2011-09-30 02:50:20 UTC 
Actually this issue still reproduce on virtio-win-prewhql-0.1-16 some times, but not always, so remove "TestBlocker" and reassign this bug for keep tracking.

Best Regards,
Dawn
Comment 19 Dor Laor 2011-10-02 13:55:07 UTC 
So we did manage to pass WHQL although it failed some of the times?
In this case, I'll move it to 6.3
Comment 20 Mike Cao 2011-10-09 07:20:45 UTC 
(In reply to comment #19)
> So we did manage to pass WHQL although it failed some of the times?
Yes .
> In this case, I'll move it to 6.3
Comment 21 Vadim Rozenfeld 2011-10-09 07:44:57 UTC 
Hi Mike,

may I see the most recent cpk and setupapi.dev.log files?

Best,
Vadim.
Comment 22 Mike Cao 2011-10-09 08:17:09 UTC 
(In reply to comment #21)
> Hi Mike,
> 
> may I see the most recent cpk and setupapi.dev.log files?
Hi, Vadim

since we are more focusing on passing whql last week ,we delete all the failed jobs ,QE will reproduce it and supply some debuginfo

BTW ,where does setupapi.dev.log located ?
> 
> Best,
> Vadim.
Comment 23 Vadim Rozenfeld 2011-10-09 08:56:59 UTC 
(In reply to comment #22)
> (In reply to comment #21)
> > Hi Mike,
> > 
> > may I see the most recent cpk and setupapi.dev.log files?
> Hi, Vadim
> 
> since we are more focusing on passing whql last week ,we delete all the failed
> jobs ,QE will reproduce it and supply some debuginfo
> 

sure. no rush.

> BTW ,where does setupapi.dev.log located ?

must be under C:\WINDOWS\INF\

> > 
> > Best,
> > Vadim.
Comment 26 Min Deng 2011-11-03 02:16:57 UTC 
Hi Vadim,

   Actually QE tried the bug in the past a few days,both in WORKGROUP and Domain ENV.Not reproduce the issue.


Thanks 
Min
Comment 27 Vadim Rozenfeld 2011-11-03 07:11:15 UTC 
(In reply to comment #26)
> Hi Vadim,
> 
>    Actually QE tried the bug in the past a few days,both in WORKGROUP and
> Domain ENV.Not reproduce the issue.
> 
> 
> Thanks 
> Min

Good news.
Thank you, Min.
Can we close this bug?

Best regards,
Vadim.
Comment 28 Min Deng 2011-11-04 05:26:36 UTC 
(In reply to comment #27)
> (In reply to comment #26)
> > Hi Vadim,
> > 
> >    Actually QE tried the bug in the past a few days,both in WORKGROUP and
> > Domain ENV.Not reproduce the issue.
> > 
> > 
> > Thanks 
> > Min
> 
> Good news.
> Thank you, Min.
> Can we close this bug?
> 
> Best regards,
> Vadim.

Hi Vadim,

   Frankly,the issue cannot be reproduced 100%.I still re-submit two jobs on two different Host yesterday.Fortunately,I got one failed.So I attached the relevant failure info to this bug.Hope it can help you.Any issues please let me know.Thanks.

Best Regards,
Min
Comment 29 Min Deng 2011-11-04 05:27:42 UTC 
Created attachment 531697 [details]
Failure info

Setup log and CPK
Comment 33 Min Deng 2011-12-26 03:08:09 UTC 
Created attachment 549529 [details]
It's for win2k3-64
Comment 35 Mike Cao 2012-02-08 10:22:30 UTC 
Close this bug since the original issue(comment #2) does not happened .
open Bug 788393 to track Common Stress With DiskIO issue .
Note You need to log in before you can comment on or make changes to this bug.