Description of problem: virt-viewer create new window for multiple monitors when reconnect to a guest. 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 qxl-win-0.1-14 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,use virsh restart the guest,run #virsh destroy win7_64 #virsh start win7_64 Actual results: when windows guest complete started,virt-viewer will create a new window to show second monitor,the old one still exist and without anything. there have three virt-viewer display. Expected results: should only have two virt-viewer page when guest have two monitor. Additional info:
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.
*** Bug 816468 has been marked as a duplicate of this bug. ***
The problem was that we discarded the VirtViewerWindow object when the guest shutdown, but we forgot to destroy the GtkWindow, so the windows on screen stayed visible. https://www.redhat.com/archives/virt-tools-list/2012-May/msg00007.html
Reproduced on the following build: virt-viewer-0.5.2-6.el6.x86_64 Verified pass on the following build: virt-viewer-0.5.2-7.el6.x86_64 Steps: Same as description Actual result: 1. After guest shut down, there is only single window left. 2. After restarting guest, the second window will be displayed. So change this bug 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. http://rhn.redhat.com/errata/RHBA-2012-0772.html