Bug 1130853
| Summary: | [whql][balloon][rhel6]guest bsod with 7e code when running DF - PNP* jobs | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | lijin <lijin> |
| Component: | virtio-win | Assignee: | Gal Hammer <ghammer> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.1 | CC: | bcao, ghammer, knoel, lijin, mdeng, rbalakri, shuyu, tlavigne, virt-maint, vrozenfe |
| Target Milestone: | rc | Keywords: | Regression, TestBlocker |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | virtio-win-prewhql-0.1-90 | Doc Type: | Bug Fix |
| Doc Text: |
Cause:
guest bsod with 7e code when running DF - PNP* jobs
Consequence:
running WHQL DF - PNP* jobs on balloon driver will lead
to triggering SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Fix:
Update balloon memory statistics only if status virtio-win queue is available.
Result:
WHQL DF - PNP* jobs on balloon driver can be passed witout BSOD.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-03-05 05:34:35 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: | 1113910, 1131838 | ||
|
Description
lijin
2014-08-18 03:30:21 UTC
Is the balloon's service is running on the guest during the HCK tests? (In reply to Gal Hammer from comment #4) > Is the balloon's service is running on the guest during the HCK tests? No. test with virtio-win-prewhql-90,all jobs passed,no bsod,so this issue has been fixed. package info: virtio-win-prewhql-90 kernel-2.6.32-486.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.428.el6.x86_64 seabios-0.6.1.2-28.el6.x86_64 spice-server-0.12.4-9.el6.x86_64 Move status to Verified according to comment #7 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://rhn.redhat.com/errata/RHBA-2015-0289.html |