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 816468

Summary: wrong message display in virt-viewer when reconnect guest for multiple monitors testing.
Product: Red Hat Enterprise Linux 6 Reporter: zhe peng <zpeng>
Component: virt-viewerAssignee: Daniel Berrangé <berrange>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 6.3CC: cfergeau, dblechte, dyasny, gkong, jwu, mzhan, rwu, yupzhang, zpeng
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: 2012-05-04 15:42:41 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:

Description zhe peng 2012-04-26 07:31:08 UTC
Description of problem:
wrong message display in virt-viewer when use --reconnect --wait for multiple monitors testing.

Version-Release number of selected component (if applicable):
virt-viewer-0.5.2-6.el6.x86_64
libvirt-0.9.10-14.el6.x86_64
qemu-kvm-0.12.1.2-2.267.el6.x86_64
spice-gtk-0.11-8.el6.x86_64
spice-server-0.10.1-5.el6.x86_64


How reproducible:
always

Steps to Reproduce:
1: prepare win guest with spice
2: add two qxl video,and start the guest
3: in guest , install qxl-win driver,config two monitors
4: use virt-viewer to open guest with --reconnect --wait
 #virt-viewer win7_64 --reconnect --wait
5: virt-viewer will open two display
6: in host console shutdown the guest,run
#virsh destroy win7_64
  
Actual results:
the first virt-viewer window show message "Waiting for guest domain to re-start"
the second window show message "Connected to graphic server", this is not make sense


Expected results:
all virt-viewer message should same with first window
"Waiting for guest domain to re-start"

Additional info:

Comment 2 RHEL Program Management 2012-05-03 04:43:08 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 3 Daniel Berrangé 2012-05-04 15:42:41 UTC
The windows should not even have remained visible once the guest shutdown. This is actually the same root cause as bug 816550

*** This bug has been marked as a duplicate of bug 816550 ***