Bug 957245
| Summary: | vdagent fails to start with 4 qxl devices (was: v-v one display enabled out of 4) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Bill Sanford <bsanford> | ||||||||
| Component: | spice-vdagent-win | Assignee: | Arnon Gilboa <agilboa> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Desktop QE <desktop-qa-list> | ||||||||
| Severity: | urgent | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | --- | CC: | acathrow, cfergeau, dblechte, dyasny, iheim, marcandre.lureau, mkrcmari, pvine, vipatel | ||||||||
| Target Milestone: | rc | Keywords: | Regression | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | spice | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-05-09 14:31:40 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | Spice | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 958954 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Bill Sanford
2013-04-26 17:59:11 UTC
In the VM, I see the 2 or 4 VM displays when I go into the screen resolution. Created attachment 740564 [details]
This is what virt-viewer shows with four monitors
Created attachment 740565 [details]
This is what is on the VM where virt-viewer shows only one monitor.
Reassigned to mingw from QXL Created attachment 740567 [details]
This better descibes what I am seeing
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. Please verify that the agent service is running. What you describes happen when the agent isn't running (or not logged in) 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. I am taking TestBlocker out since there is a workaround. 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. 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. (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? 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. The error message in comment 12 is when I shut both RHEV Agent and RHEV Spice Agent off. 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 (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 I can reproduce agent not working when guest is configured with 4 qxl devices. Moving. 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? 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. 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 |