Hide Forgot
Created attachment 489554 [details] win2k8-32-blk-sleepstress-BSOD
Hi, Vadim This bug is failed on win2k8-32 for 3 times, we will try to continue re-test in the mean while please help check it because it maybe a test blocker if if always failed.
(In reply to comment #2) > Hi, Vadim > This bug is failed on win2k8-32 for 3 times, we will try to continue re-test in > the mean while please help check it because it maybe a test blocker if if > always failed. Hi, Qunfang Has it passed on other platforms?
(In reply to comment #4) > (In reply to comment #2) > > Hi, Vadim > > This bug is failed on win2k8-32 for 3 times, we will try to continue re-test in > > the mean while please help check it because it maybe a test blocker if if > > always failed. > > Hi, Qunfang > Has it passed on other platforms? Only run virtio block for win2k8-R2 and winxp currently, it passed. "sleep stress" also passed for win2k3-64-balloon, win2k8-64-serial, win7-32 serial and so on. The failed win2k8-32-blk is a fresh image copied from a backup. But maybe we have re-install again to re-test.
And win2k8-32 whql block testing is passed smoothly on virtio-win-prewhql-0.1-8.
(In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #2) > > > Hi, Vadim > > > This bug is failed on win2k8-32 for 3 times, we will try to continue re-test in > > > the mean while please help check it because it maybe a test blocker if if > > > always failed. > > > > Hi, Qunfang > > Has it passed on other platforms? > > Only run virtio block for win2k8-R2 and winxp currently, it passed. > "sleep stress" also passed for win2k3-64-balloon, win2k8-64-serial, win7-32 > serial and so on. Yes, but what about viostor on other platforms, like win2k8-64 for example? > The failed win2k8-32-blk is a fresh image copied from a backup. > But maybe we have re-install again to re-test. Yes, please try it on a freshly installed system. The only difference between virtio-win-prewhql-0.1-8 and -0.1-9 is in MSISupported flag. It is the same binaries with the same power management support.
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
(In reply to comment #7) > (In reply to comment #5) > > (In reply to comment #4) > > > (In reply to comment #2) > > > > Hi, Vadim > > > > This bug is failed on win2k8-32 for 3 times, we will try to continue re-test in > > > > the mean while please help check it because it maybe a test blocker if if > > > > always failed. > > > > > > Hi, Qunfang > > > Has it passed on other platforms? > > > > Only run virtio block for win2k8-R2 and winxp currently, it passed. > > "sleep stress" also passed for win2k3-64-balloon, win2k8-64-serial, win7-32 > > serial and so on. > Yes, but what about viostor on other platforms, like win2k8-64 for example? win2k8-64 failed with the same BSOD. I will re-test with MSI=1 again. > > The failed win2k8-32-blk is a fresh image copied from a backup. > > But maybe we have re-install again to re-test. > > Yes, please try it on a freshly installed system. > The only difference between virtio-win-prewhql-0.1-8 and -0.1-9 > is in MSISupported flag. It is the same binaries with the same > power management support. Re-installed a fresh win2k8-32 image and retest, failed with the same BSOD. Enable MSI and re-run, passed. Disable again and run, failed.
Created attachment 489819 [details] virtio-win-prewhql-0.1-9 vfd attached please find a virtual floppy disk image, which contains virtio-win-prewhql-0.1-9 viostor drivers.
(In reply to comment #10) > Created attachment 489819 [details] > virtio-win-prewhql-0.1-9 vfd > > attached please find a virtual floppy disk image, > which contains virtio-win-prewhql-0.1-9 viostor > drivers. Hi, Qunfang Could you please git it a shot. I ran "Sleep Stress With IO" on my freshly installed win2k8-32 VM without any problem. Best regards, Vadim.
(In reply to comment #11) > (In reply to comment #10) > > Created attachment 489819 [details] > > virtio-win-prewhql-0.1-9 vfd > > > > attached please find a virtual floppy disk image, > > which contains virtio-win-prewhql-0.1-9 viostor > > drivers. > > Hi, Qunfang > > Could you please git it a shot. I ran > "Sleep Stress With IO" on my freshly > installed win2k8-32 VM without any problem. > > Best regards, > Vadim. OK, we will try it.
Hi Vadim, I retested this issue on win2k8-32 with updating driver to the one from vfd file,sleep stress still got the same BSOD and job failed. Currently I'm trying to install a fresh image with newly installing driver from vfd, and update the result. Best Regards, Dawn
(In reply to comment #13) > Hi Vadim, > > I retested this issue on win2k8-32 with updating driver to the one from vfd > file,sleep stress still got the same BSOD and job failed. > Hi Dawn, Do you have the crash dump? I'd like to see it. Thank you, Vadim. > Currently I'm trying to install a fresh image with newly installing driver from > vfd, and update the result. > > Best Regards, > Dawn
Hi Vadim, I retest this job with fresh image and installing driver directly from vfd file, and with default setting MSI=0,this job still fail with BSOD happened. CLI: /usr/libexec/qemu-kvm -m 6G -smp 4 -cpu cpu64-rhel6,+x2apic -usbdevice tablet -drive file=win2k8-32-sp2-bugverification.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:10:1a:12:31:16,bus=pci.0,addr=0x4 -boot c -uuid d247b32c-0160-4000-ad78-437ee59281a0 -rtc-td-hack -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-win2k8-32-sp2-bugverification-vfd,server,nowait -mon chardev=111a,mode=readline -name win2k8-32-blk-9-bugverification-vfd -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 Best Regards, Dawn
(In reply to comment #15) > Hi Vadim, > > I retest this job with fresh image and installing driver directly from vfd > file, and with default setting MSI=0,this job still fail with BSOD happened. > > CLI: > > /usr/libexec/qemu-kvm -m 6G -smp 4 -cpu cpu64-rhel6,+x2apic -usbdevice tablet > -drive > file=win2k8-32-sp2-bugverification.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:10:1a:12:31:16,bus=pci.0,addr=0x4 -boot c -uuid > d247b32c-0160-4000-ad78-437ee59281a0 -rtc-td-hack -no-kvm-pit-reinjection > -chardev > socket,id=111a,path=/tmp/monitor-win2k8-32-sp2-bugverification-vfd,server,nowait > -mon chardev=111a,mode=readline -name win2k8-32-blk-9-bugverification-vfd -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 > > Best Regards, > Dawn Here's mine: sudo /home/vrozenfe/work/troubles/qemu-kvm-rhel6/x86_64-softmmu/qemu-system-x86_64 -M rhel6.0.0 -m 1G -smp 2 -cpu qemu64,+x2apic -usbdevice tablet -drive file=/home/vrozenfe/work/images/w2k8-dtm-client.qcow2,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:10:1a:12:31:16,bus=pci.0,addr=0x4 -boot c -uuid d247b32c-0160-4000-ad78-437ee59281a0 -rtc-td-hack -no-kvm-pit-reinjection -name win2k8-32-blk-9-bugverification -drive file=/home/vrozenfe/work/images/test1.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=/home/vrozenfe/work/images/test2.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=/home/vrozenfe/work/images/test3.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=/home/vrozenfe/work/images/test4.qcow2,if=none,id=drive-virtio4,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio4,id=virtio-blk-pci4 -monitor stdio But still cannot reproduce the problem. Are you working with WLK 1.5 or 1.6? Can you create a submission package and sent it to me? I need to check all the details. Best regards, Vadim.
Created attachment 490479 [details] cpk file for win2k8-32-blk (msi=0)
(In reply to comment #24) > (In reply to comment #15) > > Hi Vadim, > > > > I retest this job with fresh image and installing driver directly from vfd > > file, and with default setting MSI=0,this job still fail with BSOD happened. > > > > CLI: > > > > /usr/libexec/qemu-kvm -m 6G -smp 4 -cpu cpu64-rhel6,+x2apic -usbdevice tablet > > -drive > > file=win2k8-32-sp2-bugverification.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:10:1a:12:31:16,bus=pci.0,addr=0x4 -boot c -uuid > > d247b32c-0160-4000-ad78-437ee59281a0 -rtc-td-hack -no-kvm-pit-reinjection > > -chardev > > socket,id=111a,path=/tmp/monitor-win2k8-32-sp2-bugverification-vfd,server,nowait > > -mon chardev=111a,mode=readline -name win2k8-32-blk-9-bugverification-vfd -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 > > > > Best Regards, > > Dawn > > > Here's mine: > > sudo > /home/vrozenfe/work/troubles/qemu-kvm-rhel6/x86_64-softmmu/qemu-system-x86_64 > -M rhel6.0.0 -m 1G -smp 2 -cpu qemu64,+x2apic -usbdevice tablet -drive > file=/home/vrozenfe/work/images/w2k8-dtm-client.qcow2,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:10:1a:12:31:16,bus=pci.0,addr=0x4 -boot c -uuid > d247b32c-0160-4000-ad78-437ee59281a0 -rtc-td-hack -no-kvm-pit-reinjection -name > win2k8-32-blk-9-bugverification -drive > file=/home/vrozenfe/work/images/test1.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=/home/vrozenfe/work/images/test2.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=/home/vrozenfe/work/images/test3.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=/home/vrozenfe/work/images/test4.qcow2,if=none,id=drive-virtio4,cache=none,werror=stop,rerror=stop > -device virtio-blk-pci,drive=drive-virtio4,id=virtio-blk-pci4 -monitor stdio > > But still cannot reproduce the problem. > Are you working with WLK 1.5 or 1.6? Hi, Vadim We used WLK1.5. > Can you create a submission package and > sent it to me? I need to check all the details. Please refer to the attachment I upload in Comment 5. > Best regards, > Vadim.
Clearing the regression/blocker flags since we passed whql with msi=1
Hi Dawn, Could you please decrease amount of guest's memory to 2G and retest it on a freshly installed system with the latest (0.1-15) drivers. Next, increase the amount of the memory up to 6G and retest it again. Please provide new memory dump and cpk files in case of crash(s). Best regards, Vadim.
Hi Vadim, I'll have a try with latest drivers with 2G and 6G memory on a freshly system, and will update the results for you later. Best Regards, Dawn
(In reply to comment #36) > Hi Dawn, > > Could you please decrease amount of guest's memory to 2G and retest it on a > freshly installed system with the latest (0.1-15) drivers. Next, increase the > amount of the memory up to 6G and retest it again. > Please provide new memory dump and cpk files in case of crash(s). > > Best regards, > Vadim. Hi Vadim, This issue still reproduce on driver(0.1-15), but a good news is that it does not reproduce on the latest driver "0.1-16", job of "Sleep Stress With IO" passed without any BSOD and error with 2G and 6G memory. Best Regards, Dawn
(In reply to comment #38) > (In reply to comment #36) > > Hi Dawn, > > > > Could you please decrease amount of guest's memory to 2G and retest it on a > > freshly installed system with the latest (0.1-15) drivers. Next, increase the > > amount of the memory up to 6G and retest it again. > > Please provide new memory dump and cpk files in case of crash(s). > > > > Best regards, > > Vadim. > > Hi Vadim, > > This issue still reproduce on driver(0.1-15), but a good news is that it does > not reproduce on the latest driver "0.1-16", job of "Sleep Stress With IO" Hi Dawn, It seems pretty weird. Nothing in viostor driver was changed between 0.1-15 and 0.1-16. Can we be sure that both drivers were tested in absolutely equal environments? Kind regards, Vadim. > passed without any BSOD and error with 2G and 6G memory. > > Best Regards, > Dawn
Hi Vadim, Yes, I am sure that this job was tested in the absolutely equal environments, the same host and the same guest, I only updated the driver from 0.1-15 to 0.1-16. In additional, I remembered Ronen mentioned in mail that for new build 0.1-16, blk driver has a bug fix that was never tested for WHQL (in 1-15),so whatever this change is related with this bug or not, but the driver should be changed, right? any wrong, please correct me, thanks! Best Regards, Dawn
(In reply to comment #40) > Hi Vadim, > > Yes, I am sure that this job was tested in the absolutely equal environments, > the same host and the same guest, I only updated the driver from 0.1-15 to > 0.1-16. > > In additional, I remembered Ronen mentioned in mail that for new build 0.1-16, > blk driver has a bug fix that was never tested for WHQL (in 1-15),so whatever > this change is related with this bug or not, but the driver should be changed, > right? any wrong, please correct me, thanks! > Hi Dawn. There were no viostor related changes between 0.1-15 and 0.1-16. There only difference between 0.1-14 and 0.1-15 was in disabling serial number support, which should affect XP and W2K3 guests only. The most significant changes were between 0.1-12 and 0.1-13. Anyway, I'm glad to know that the problem is not reproducible anymore with the latest driver. However, I would like to keep this bug open until the entire viostor WHQL process will be completed. Best regards, Vadim. > Best Regards, > Dawn (In reply to comment #40) > Hi Vadim, > > Yes, I am sure that this job was tested in the absolutely equal environments, > the same host and the same guest, I only updated the driver from 0.1-15 to > 0.1-16. > > In additional, I remembered Ronen mentioned in mail that for new build 0.1-16, > blk driver has a bug fix that was never tested for WHQL (in 1-15),so whatever > this change is related with this bug or not, but the driver should be changed, > right? any wrong, please correct me, thanks! > > Best Regards, > Dawn
(In reply to comment #41) > (In reply to comment #40) > > Hi Vadim, > > > > Yes, I am sure that this job was tested in the absolutely equal environments, > > the same host and the same guest, I only updated the driver from 0.1-15 to > > 0.1-16. > > > > In additional, I remembered Ronen mentioned in mail that for new build 0.1-16, > > blk driver has a bug fix that was never tested for WHQL (in 1-15),so whatever > > this change is related with this bug or not, but the driver should be changed, > > right? any wrong, please correct me, thanks! > > > Hi Dawn. > > There were no viostor related changes between 0.1-15 and 0.1-16. > There only difference between 0.1-14 and 0.1-15 was in disabling serial number > support, which should affect XP and W2K3 guests only. > The most significant changes were between 0.1-12 and 0.1-13. > > Anyway, I'm glad to know that the problem is not reproducible anymore with the > latest driver. > > However, I would like to keep this bug open until the entire viostor WHQL > process will be completed. > > Best regards, > Vadim. > Hi Vadim, Thanks for your explanation,I agree with you for keeping this bug open until the entire viostor WHQL, and I will try more times to make sure this bug does not always reproduce. Best Regards, Dawn > process will be completed. > > Best Regards, > > Dawn > > (In reply to comment #40) > > Hi Vadim, > > > > Yes, I am sure that this job was tested in the absolutely equal environments, > > the same host and the same guest, I only updated the driver from 0.1-15 to > > 0.1-16. > > > > In additional, I remembered Ronen mentioned in mail that for new build 0.1-16, > > blk driver has a bug fix that was never tested for WHQL (in 1-15),so whatever > > this change is related with this bug or not, but the driver should be changed, > > right? any wrong, please correct me, thanks! > > > > Best Regards, > > Dawn
According to comment 42, move this bug to verified.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Do not document
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1542.html