Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 682680[details]
bsod screenshot
Description of problem:
BSOD in qxl driver when turning on/off monitor 4
Version-Release number of selected component (if applicable):
Guest: win7x32
qxl-win-0.1-17
vdagent-win-0.1-12
virtio-win-prewhql-0.1-51
Host RHEL 6.4:
qemu-kvm-0.12.1.2-2.351.el6.x86_64
spice-server-0.12.0-11.el6.x86_64
How reproducible:
did get another bsod by similar steps but that didn't produce a memory dump
Steps to Reproduce:
1. install a clean windows machine, update it, install virtio-serial, qxl and vdagent manually
2. enable 4th monitor in the guest
3. switch on/off display 4 or display 3 (keep display 2 off)
Actual results:
BSOD can be triggered
Expected results:
no such thing can trigger BSOD
Additional info:
rhevm-3.2.z? would be handy here.
Hi David,
Does this happen without virtio-serial?
Is the switching on/off of the monitor in step 3 done via closing the corresponding window in remove-viewer?
Alon
Hi Alon,
(In reply to comment #6)
> Hi David,
>
> Does this happen without virtio-serial?
I don't really know as I didn't encounter the bug in last month or two
> Is the switching on/off of the monitor in step 3 done via closing the
> corresponding window in remove-viewer?
Yes.
Created attachment 682680 [details] bsod screenshot Description of problem: BSOD in qxl driver when turning on/off monitor 4 Version-Release number of selected component (if applicable): Guest: win7x32 qxl-win-0.1-17 vdagent-win-0.1-12 virtio-win-prewhql-0.1-51 Host RHEL 6.4: qemu-kvm-0.12.1.2-2.351.el6.x86_64 spice-server-0.12.0-11.el6.x86_64 How reproducible: did get another bsod by similar steps but that didn't produce a memory dump Steps to Reproduce: 1. install a clean windows machine, update it, install virtio-serial, qxl and vdagent manually 2. enable 4th monitor in the guest 3. switch on/off display 4 or display 3 (keep display 2 off) Actual results: BSOD can be triggered Expected results: no such thing can trigger BSOD Additional info: rhevm-3.2.z? would be handy here.