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.

Bug 1040152

Summary: Rebooting a Windows 2008 Server (Not R2), kills the SPICE agent on the guest.
Product: Red Hat Enterprise Linux 8 Reporter: Bill Sanford <bsanford>
Component: spice-vdagent-winAssignee: Default Assignee for SPICE Bugs <rh-spice-bugs>
Status: CLOSED WONTFIX QA Contact: SPICE QE bug list <spice-qe-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: ---CC: bsanford, cfergeau, dblechte, marcandre.lureau, mkrcmari, pvine, rbalakri, vipatel, yeylon
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: 2015-06-04 12:59:47 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: 1135054    
Bug Blocks:    

Description Bill Sanford 2013-12-10 20:30:32 UTC
Description of problem:
When I have a Windows 2008 Server 32-bit as a guest, if I have >1 display and I restart the guest from the Start button, the virt-viewer window goes black and on the first display, and then you see the text "Waiting for display 1." The other displays that should display this are all black.

If I close virt-viewer and relaunch it from the UP, either I get black screens on the displays or an error, "Could not connect to the agent on the guest, it may be unresponsive or not installed. As a result, some of the features may not work."

Click ok and you get the same scenario with the first display black, and it now has "Connected to graphics server" and will stay there.

Version-Release number of selected component (if applicable):

RHEV-M:
RHEV-M 3.3 (is26)

Guest:
Windows 2008 Server 32-bit (Not R2)
rhev-guest-tools-iso-3.3-7.noarch.rpm

Windows 7 client 64-bit
mingw64-virt-viewer-0.5.615.el6_5


How reproducible:


Steps to Reproduce:
1. See above
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Marc-Andre Lureau 2013-12-10 21:02:24 UTC
(In reply to Bill Sanford from comment #0)
> Description of problem:
> When I have a Windows 2008 Server 32-bit as a guest, if I have >1 display
> and I restart the guest from the Start button, the virt-viewer window goes
> black and on the first display, and then you see the text "Waiting for
> display 1." The other displays that should display this are all black.

please verify the agent is running after restart. if not, the bug should be moved to vdagent.

Comment 2 Bill Sanford 2013-12-10 21:08:20 UTC
When I shut the VM down and bring it back up, the RHEV* services are running and set to automatic on boot. Moving to vdagent.

Comment 5 Christophe Fergeau 2014-08-26 15:21:48 UTC
I just tested this with a fresh install of win2k8 (not r2), fully up to date. I installed rhev-guest-tools-iso-3.3-14, set up 2 screens. I made sure c&p was working, restarted the VM from the start menu, and checked that c&p was still working after that.
I connected with remote-viewer from f20, and the VM was created locally in virt-manager.

Can you still reproduce this?

Comment 6 Christophe Fergeau 2014-08-27 12:39:39 UTC
Alternatively, could you give me access to a RHEV instance with a win2k8 VM or ISO? I could not find such an ISO in the instance I usually use, that's why I tested in virt-manager.

Comment 7 Bill Sanford 2014-08-27 12:43:56 UTC
I will retest.

Comment 8 Bill Sanford 2014-09-02 16:24:34 UTC
Christophe, I will retest once https://bugzilla.redhat.com/show_bug.cgi?id=1135054 is cleared and will install the QXL driver.

Comment 9 Christophe Fergeau 2015-06-04 12:59:47 UTC
We don't support Windows Server versions as SPICE guests, so I'll close this bug. Feel free to reopen if you think this is not correct.