| Summary: | Warning "Display can only be attached through libvirt with --attach" should prompt in window when guest start running | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | zhoujunqin <juzhou> |
| Component: | virt-viewer | Assignee: | Snir Sheriber <ssheribe> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | CC: | cfergeau, dblechte, kuwei, mxie, mzhan, pgrunt, rbalakri, ssheribe, tzheng, xiaodwan |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | virt-viewer-5.0-1.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 15:04:11 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: | |
|
Description
zhoujunqin
2016-10-19 10:33:16 UTC
(In reply to zhoujunqin from comment #0) > 1. > When use virt-viewer connect to a running guest <listen type='none'> without > "-a" option directly, error "Failed to connect: Display can only be attached > through libvirt with --attach" shows in window, after click "OK", window > will closed and command exit. Or virt-viewer could just fallback to --attach behaviour when it detects a guest where --attach has to be used > Or virt-viewer could just fallback to --attach behaviour when it detects a
> guest where --attach has to be used
Do you mean virt-viewer will not report any error and connect to guest automatically with --attach implied?
If yes, it may have a little confusion for users when they connect to the guest again when it's running. Because they have to add --attach for a running guest.
Thanks
(In reply to xiaodwan from comment #2) > > Or virt-viewer could just fallback to --attach behaviour when it detects a > > guest where --attach has to be used > > Do you mean virt-viewer will not report any error and connect to guest > automatically with --attach implied? > > If yes, it may have a little confusion for users when they connect to the > guest again when it's running. Because they have to add --attach for a > running guest. It would have to do that in all cases. Actually, for this bug report, I think we'd get the same warning if the guest is already running ? (In reply to Christophe Fergeau from comment #3) > (In reply to xiaodwan from comment #2) > > > Or virt-viewer could just fallback to --attach behaviour when it detects a > > > guest where --attach has to be used > > > > Do you mean virt-viewer will not report any error and connect to guest > > automatically with --attach implied? > > > > If yes, it may have a little confusion for users when they connect to the > > guest again when it's running. Because they have to add --attach for a > > running guest. > > It would have to do that in all cases. Actually, for this bug report, I > think we'd get the same warning if the guest is already running ? Now an error dialog pops and ask user to add "--attach" option if the guest is running. If do that in all cases, then "--attach" option will be redundant. Fixed upstream https://git.fedorahosted.org/cgit/virt-viewer.git/commit/?id=d7ef44d44f4468b6fd792ec492025d6d5df11a08 Fixed upsrteam (new link): https://pagure.io/virt-viewer/c/d7ef44d44f4468b6fd792ec492025d6d5df11a08?branch=master I verified it with virt-viewer-5.0-2.el7.x86_64. if don't specify --attach when connecting to a shutdown guest, after start up the guest, Error "Display can only be attached through libvirt with --attach" displays in virt-viewer window. If specify --attach when connecting to a shutdown guest, after start up the guest, virt-viewer can connect to the guest successfully. So move the bug from ON_QA to VERIFIED. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1849 |