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 957245 - vdagent fails to start with 4 qxl devices (was: v-v one display enabled out of 4)
Summary: vdagent fails to start with 4 qxl devices (was: v-v one display enabled out o...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: spice-vdagent-win
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Arnon Gilboa
QA Contact: Desktop QE
URL:
Whiteboard: spice
Depends On:
Blocks: 958954
TreeView+ depends on / blocked
 
Reported: 2013-04-26 17:59 UTC by Bill Sanford
Modified: 2019-10-10 14:19 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-09 14:31:40 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
This is what virt-viewer shows with four monitors (746.23 KB, image/png)
2013-04-26 18:11 UTC, Bill Sanford 		no flags Details
This is what is on the VM where virt-viewer shows only one monitor. (399.00 KB, image/png)
2013-04-26 18:12 UTC, Bill Sanford 		no flags Details
This better descibes what I am seeing (388.49 KB, image/png)
2013-04-26 18:36 UTC, Bill Sanford 		no flags Details
View All

Description Bill Sanford 2013-04-26 17:59:11 UTC 
Description of problem:
In RHEV-M, I set the displays in the console of the VM to two or four displays. When I launch the Windows 7 x64 VM, there is only one diplay enabled and the other displays are grayed out.

Version-Release number of selected component (if applicable):
RHEV-M 3.2 (sf14)
virt-viewer 0.5.3-23

How reproducible:
100%

Steps to Reproduce:
1. See above.
2.
3.
  
Actual results:
Only one display available.

Expected results:
All for displays available.

Additional info:
This is a clean install of sf14 and W2K8R2 Server.
Comment 1 Bill Sanford 2013-04-26 18:07:59 UTC 
In the VM, I see the 2 or 4 VM displays when I go into the screen resolution.
Comment 2 Bill Sanford 2013-04-26 18:11:30 UTC 
Created attachment 740564 [details]
This is what virt-viewer shows with four monitors
Comment 3 Bill Sanford 2013-04-26 18:12:18 UTC 
Created attachment 740565 [details]
This is what is on the VM where virt-viewer shows only one monitor.
Comment 4 Bill Sanford 2013-04-26 18:21:40 UTC 
Reassigned to mingw from QXL
Comment 5 Bill Sanford 2013-04-26 18:36:23 UTC 
Created attachment 740567 [details]
This better descibes what I am seeing
Comment 6 Bill Sanford 2013-04-26 18:56:36 UTC 
If I go into the display properties of the VM and extend each display to the desktop, THEN one by one they get added to the desktop and subsequently the virt-viewer menu.
Comment 7 Marc-Andre Lureau 2013-04-29 12:51:15 UTC 
Please verify that the agent service is running. What you describes happen when the agent isn't running (or not logged in)
Comment 8 Bill Sanford 2013-04-30 14:26:12 UTC 
Marc, same thing in spice-client-msi-3.2-10. If I have one or three displays enabled, the remaining ones need to change the display properties of the VM and extend each display to the desktop.
Comment 9 Bill Sanford 2013-04-30 14:27:34 UTC 
I am taking TestBlocker out since there is a workaround.
Comment 10 Marc-Andre Lureau 2013-04-30 14:28:46 UTC 
Bill,

(In reply to comment #7)
> Please verify that the agent service is running. What you describes happen
> when the agent isn't running (or not logged in)

Can you answer my question. Thanks.
Comment 11 Bill Sanford 2013-04-30 14:41:08 UTC 
If the agent is killed, I get and error message: 

Guest Agent is not responsive
Could not connect to the agent on the guest, it may be unresponsive or not installed.
As a result, some features may not work.

I still get all 4 monitors with limited (non-agent) functionality.
Comment 12 Marc-Andre Lureau 2013-04-30 14:49:53 UTC 
(In reply to comment #11)
> If the agent is killed, I get and error message: 
> 
> Guest Agent is not responsive
> Could not connect to the agent on the guest, it may be unresponsive or not
> installed.
> As a result, some features may not work.

I have never seen such message. That might be the rhevm agent? Is the Spice Agent running, and what version is installed?
Comment 13 Bill Sanford 2013-04-30 18:51:17 UTC 
I installed the rhev-guest-tools-iso-3.2-5.noarch.rpm to the guest and the version on the SPICE Agent is 1.1.0.100106.
Comment 14 Bill Sanford 2013-04-30 18:53:29 UTC 
The error message in comment 12 is when I shut both RHEV Agent and RHEV Spice Agent off.
Comment 15 Marc-Andre Lureau 2013-05-01 00:16:09 UTC 
I can't reproduce with mingw -24, -25, and f19 remote-viewer, using 1.1.0.10017 (last build). 

And I can't explain that the display menu items would be insensitve, but that the agent is somehow not connected.

Please check also the RHEL virt-viewer has the same issue.

Please get the whole mingw or RHEL SPICE_DEBUG log (use debug-helper and a very large cmd Screen Buffer)

thanks
Comment 16 David Blechter 2013-05-01 01:13:50 UTC 
(In reply to comment #13)
> I installed the rhev-guest-tools-iso-3.2-5.noarch.rpm to the guest and the
> version on the SPICE Agent is 1.1.0.100106.

Bill. can you please, finally answer the question you have been asked multiple times in comments 7, 10 and 13:  Is the Spice Agent running? 
also, can you verify the Spice agent version. according to your comment it is version 106, but the current version is 17
Comment 18 Marc-Andre Lureau 2013-05-02 14:20:27 UTC 
I can reproduce agent not working when guest is configured with 4 qxl devices. Moving.
Comment 20 Arnon Gilboa 2013-05-06 11:45:31 UTC 
Hi Bill,

Please try to repro with latest vdagent, and verify "RHEV Spice Agent" service is up and running. Attach vdagent.log in any case, so we can see if/what MONITORS_CONFIG it does get from the client.

As Marc-Andre said, this might be similar to bug 958051, if one of the 4 qxl devices failed to initialize due to lack of memory. Can you please check all 4 qxls are properly working in the device manager?

BTW, are you connecting from UP/AP?
Comment 21 Bill Sanford 2013-05-06 14:17:32 UTC 
Arnon, the latest vdagent seems to have done the trick. I am connecting from the UP. When we have the build that contains vdagent-win-0.1-17, I will retest and verify this bug.
Comment 22 Bill Sanford 2013-05-09 14:31:40 UTC 
Closed based on testing with

RHEV-M 3.2 (si14) 
W2K8R2 client 
spice-client-msi-3.2-10 (mingw-virt-viewer 0.5.3-25).
vdagent-win-0.1-17 to Win7
Note You need to log in before you can comment on or make changes to this bug.