Bug 1156259
Summary: | Win7-64 guest BSOD(0x000000A0) when doing s4 | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | ShupingCui <scui> | ||||
Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> | ||||
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 7.1 | CC: | coli, ghammer, hhuang, juzhang, lijin, michen, rbalakri, scui, shuang, virt-maint, vrozenfe, xuhan, yvugenfi | ||||
Target Milestone: | rc | Keywords: | Regression | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | Fixed_Not_Ship | ||||||
Fixed In Version: | virtio-win-prewhql-0.1-94 | Doc Type: | Bug Fix | ||||
Doc Text: |
NO_DOCS
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-11-24 08:45: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: | |||||||
Attachments: |
|
Description
ShupingCui
2014-10-24 03:14:12 UTC
Created attachment 950160 [details]
screenshot
I cannot get dump file in guest, guest always on Collecting data for crash dump...
ShupingCui, Can you try to isolate a component that triggers the issue. For example virtio-scsi/virtio-net. Thanks. (In reply to Ronen Hod from comment #3) > ShupingCui, > > Can you try to isolate a component that triggers the issue. For example > virtio-scsi/virtio-net. > Thanks. Hi Ronen, Tried with the following matrix for S4: |--------------|------------|---------| | driveformat | nicmodel | result | |--------------|------------|---------| | virtio-scsi | virtio-net | BSOD | | virtio-scsi | e1000 | BSOD | | virtio-blk | virtio-net | PASSED | | virtio-blk | e1000 | PASSED | |--------------|------------|---------| Driver Details: Red Hat VirtIO SCSI controller 60.71.104.9300 Red Hat VirtIO SCSI pass-through controller 60.71.104.9300 (In reply to ShupingCui from comment #5) > > Driver Details: > Red Hat VirtIO SCSI controller > 60.71.104.9300 > > Red Hat VirtIO SCSI pass-through controller > 60.71.104.9300 Thanks. You certainly nailed it down. (In reply to Ronen Hod from comment #6) > (In reply to ShupingCui from comment #5) > > > > > Driver Details: > > Red Hat VirtIO SCSI controller > > 60.71.104.9300 > > > > Red Hat VirtIO SCSI pass-through controller > > 60.71.104.9300 > > Thanks. You certainly nailed it down. Please try downgrading virtio-scsi driver to build 88. At least it should fix crashdump file generation problem. Vadim. (In reply to Vadim Rozenfeld from comment #7) > (In reply to Ronen Hod from comment #6) > > (In reply to ShupingCui from comment #5) > > > > > > > > Driver Details: > > > Red Hat VirtIO SCSI controller > > > 60.71.104.9300 > > > > > > Red Hat VirtIO SCSI pass-through controller > > > 60.71.104.9300 > > > > Thanks. You certainly nailed it down. > > Please try downgrading virtio-scsi driver to build 88. At least it should > fix crashdump file generation problem. > > Vadim. Hi Vadim, Tried downgrading virtio-scsi driver to build 88, do s4 -> PASSED, guest can s4 successfully. Red Hat VirtIO SCSI pass-through controller 60.71.104.8800 Please re-test with drivers from build 94 available at https://brewweb.devel.redhat.com/buildinfo?buildID=399548 Thanks, Vadim Tried virtio-scsi driver for build 94, do s4 -> PASSED, guest can s4 successfully. Red Hat VirtIO SCSI pass-through controller 60.71.104.9400 (In reply to ShupingCui from comment #12) > Tried virtio-scsi driver for build 94, do s4 -> PASSED, guest can s4 > successfully. > > Red Hat VirtIO SCSI pass-through controller > 60.71.104.9400 Thanks, Vadim. change status to verified according to comment#12 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-2513.html |