| Summary: | BSOD of guest occurs when shutting down multiple screens Windows guest. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Marian Krcmarik <mkrcmari> |
| Component: | spice-qxl-xddm | Assignee: | Alon Levy <alevy> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | --- | CC: | acathrow, bcao, dblechte, pvine |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-08-09 08:20:07 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Marian Krcmarik
2011-11-17 13:05:59 UTC
I reproduced with off-screen surface driver installed on guest qxl-win-0.1-13 but unfortunately I was not able to get dump since creating of dump always got stuck in "Initializing disk fro crash dump" phase. Reproducing the "PAUSED state guest" is much easier and more often, I am not really sure It is related to the BSOD or maybe BSOD is the cause of "emulation error". I would appreciate if anyone can take a look and maybe say little bit more. I own information about host: qemu-kvm-0.12.1.2-2.207.el6.x86_64 libvirt-python-0.9.4-21.el6.x86_64 libvirt-0.9.4-21.el6.x86_64 qemu-kvm-debuginfo-0.12.1.2-2.207.el6.x86_64 spice-server-0.8.2-5.el6.x86_64 vdsm-4.9-110.el6.x86_64 qemu-img-0.12.1.2-2.207.el6.x86_64 libvirt-client-0.9.4-21.el6.x86_64 vdsm-cli-4.9-110.el6.x86_64 gpxe-roms-qemu-0.9.7-6.9.el6.noarch I took the KVM internal error bug out from this and created a new one. This bug remains to be bug for BSOD of guest, qxl related. What is the KVM internal error bug number? (In reply to comment #4) > What is the KVM internal error bug number? https://bugzilla.redhat.com/show_bug.cgi?id=788227 I debugged with Gleb, so you can possibly ask him about details. Marian, the "virtio_ioport_write: unexpected address 0x13 value 0x1" reference suggests to check the newest virtio drivers, can you see if you can reproduce? (your later comment also suggests this: """ I could not reproduce without tools but with qxl driver as well (but with BSOD I was maybe just lucky) but the second problem with PAUSED state seems to be not reproducible with only qxl and no virtio-serial. """) Thanks, Alon (In reply to Alon Levy from comment #6) > Marian, the "virtio_ioport_write: unexpected address 0x13 value 0x1" > reference suggests to check the newest virtio drivers, can you see if you > can reproduce? > > (your later comment also suggests this: > """ > I could not reproduce without tools but with qxl driver as well (but with > BSOD I was maybe just lucky) but the second problem with PAUSED state seems > to be not reproducible with only qxl and no virtio-serial. > """) > > Thanks, > Alon Well, It's been a while I reported this bug (1.5 yrs) so all of the involved components changed and as I stated I could not reproduce with the off-screen surface driver but that time older driver was used. I tried to reproduce but not very hard hard and nothing showed up, The dumps are still available though. Since I cannot reproduce, and the original reporter cannot either, even though I'm sure there is a bug in shutdown per Gleb's comment 9 on #788227, I prefer to close this for now and reopen if someone can reproduce. Alon based on https://bugzilla.redhat.com/show_bug.cgi?id=754704#c8 this bug is closed. |