Bug 1409298
| Summary: | [virtio-win][balloon] Guest win2008-32 occurs BSoD when running job 'Device Path Exerciser' | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Peixiu Hou <phou> |
| Component: | virtio-win | Assignee: | Ladi Prosek <lprosek> |
| virtio-win sub component: | virtio-win-prewhql | QA Contact: | Virtualization Bugs <virt-bugs> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | ailan, lijin |
| Version: | 7.3 | Keywords: | Regression, TestBlocker |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 12:55:38 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: | |||
|
Description
Peixiu Hou
2016-12-31 11:42:30 UTC
This is a tight race between request completion and cancellation in the balloon driver. Very likely not a regression but requires specific timing to hit. Fix coming. Tried this job with virtio-win-prewhql-130 on win2008-32. Also reproduced this issue with '-M q35', tried 3 times totally, hit bsod 2 times(bsod(d1)+bsod(8e)), and it can be passed on the last time. Cannot reproduce this issue with '-M pc'. Best Regards~ Peixiu (In reply to Peixiu Hou from comment #5) > Tried this job with virtio-win-prewhql-130 on win2008-32. > > Also reproduced this issue with '-M q35', tried 3 times totally, hit bsod 2 > times(bsod(d1)+bsod(8e)), and it can be passed on the last time. > > Cannot reproduce this issue with '-M pc'. Can you please double-check that it reproduces with -M pc and virtio-win 129 and does not reproduce with -M pc and virtio-win 130? Also, would it be possible to share the new dumps? Thanks! Ladi (In reply to Ladi Prosek from comment #6) > (In reply to Peixiu Hou from comment #5) > > Tried this job with virtio-win-prewhql-130 on win2008-32. > > > > Also reproduced this issue with '-M q35', tried 3 times totally, hit bsod 2 > > times(bsod(d1)+bsod(8e)), and it can be passed on the last time. > > > > Cannot reproduce this issue with '-M pc'. > > Can you please double-check that it reproduces with -M pc and virtio-win 129 > and does not reproduce with -M pc and virtio-win 130? Also, would it be > possible to share the new dumps? > > Thanks! > Ladi Hi Ladi, This issue can be reproduced on virtio-win 129 with -M pc easily, used same image, reinstall the virtio-win 129 balloon driver, run the job, the bsod(8e) occurred. And then, reinstall the virtio-win 130 balloon driver, the job can be easily passed. With -M q35, first try occurred bsod(d1), second try occurred bsod(8e) and then reboot the guest, occurred bsod(d1), reboot the guest again, occurred bsod(7e). I saved the dump file bsod(d1) on first test and bsod(7e) on second test(the bsod(8e) dump file is covered). Best Regards~ Peixiu Hi Peixiu Hou, (In reply to Peixiu Hou from comment #8) > Hi Ladi, > > This issue can be reproduced on virtio-win 129 with -M pc easily, used same > image, reinstall the virtio-win 129 balloon driver, run the job, the > bsod(8e) occurred. > And then, reinstall the virtio-win 130 balloon driver, the job can be easily > passed. > > With -M q35, first try occurred bsod(d1), second try occurred bsod(8e) and > then reboot the guest, occurred bsod(d1), reboot the guest again, occurred > bsod(7e). I saved the dump file bsod(d1) on first test and bsod(7e) on > second test(the bsod(8e) dump file is covered). Thank you. The crashes you're getting on Q35 are a different issue, not specific to balloon. It's the same thing we hit in bug 1408771. Two possible workarounds are: 1) use less than 4GB of memory, or 2) do not use cdrom. Thanks! (In reply to Ladi Prosek from comment #10) > Hi Peixiu Hou, > > (In reply to Peixiu Hou from comment #8) > > Hi Ladi, > > > > This issue can be reproduced on virtio-win 129 with -M pc easily, used same > > image, reinstall the virtio-win 129 balloon driver, run the job, the > > bsod(8e) occurred. > > And then, reinstall the virtio-win 130 balloon driver, the job can be easily > > passed. > > > > With -M q35, first try occurred bsod(d1), second try occurred bsod(8e) and > > then reboot the guest, occurred bsod(d1), reboot the guest again, occurred > > bsod(7e). I saved the dump file bsod(d1) on first test and bsod(7e) on > > second test(the bsod(8e) dump file is covered). > > Thank you. The crashes you're getting on Q35 are a different issue, not > specific to balloon. It's the same thing we hit in bug 1408771. Two possible > workarounds are: 1) use less than 4GB of memory, or 2) do not use cdrom. > Thanks! Hi Ladi, Ok, thanks a lot, I tried it without cdrom on a new installed image, the job can be passed, did not reproduce this bug, then added cdrom, bsod occurred when the system booting, and then run this job again, it can be passed. And also I tried it with less than 4GB mem on a new installed image, the job can be passed, did not reproduce this bug, then restore mem to 4G to rerun this job, the job failed 1 time, and passed 1 time. Best Regards~ Peixiu this bug tracks only balloon tight race issue,bug1408771 will track q35 issue. change status to verified according to comment8 and comment#10 Hi Amnon, Could you help to ack? Thanks 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. https://access.redhat.com/errata/RHBA-2017:2341 |