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 727414 - [virt-manager]can't open guest via virt-manager
Summary: [virt-manager]can't open guest via virt-manager
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.2
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Cole Robinson
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-02 05:19 UTC by zhe peng
Modified: 2011-12-06 16:14 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
No description necessary
Clone Of:
Environment:
Last Closed: 2011-12-06 16:14:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1642 0 normal SHIPPED_LIVE virt-manager bug fix and enhancement update 2011-12-06 00:50:37 UTC

Description zhe peng 2011-08-02 05:19:11 UTC
Description of problem:
click guest name from virt-manager ,will pop up error dialog,and can't open guest

Version-Release number of selected component (if applicable):
virt-manager-0.9.0-4.el6
libvirt-0.9.4-0rc1.el6
qemu-kvm-0.12.1.2-2.172.el6

How reproducible:
always

Steps to Reproduce:
1.install virt-manager-0.9.0.4.el6
2.#virt-manager --debug
3.click guest name on virt-manager
  
Actual results:
output:
2011-08-02 01:13:17,278 (cli:71): virt-manager startup
2011-08-02 01:13:17,279 (virt-manager:292): Launched as: /usr/share/virt-manager/virt-manager.py --debug
2011-08-02 01:13:17,279 (virt-manager:293): GTK version: (2, 18, 9)
2011-08-02 01:13:17,279 (virt-manager:294): virtManager import: <module 'virtManager' from '/usr/share/virt-manager/virtManager/__init__.pyc'>
connect : Connection refused
2011-08-02 01:13:17,407 (engine:555): No inspection thread because libguestfs is too old, not available, or libvirt is not thread safe.
2011-08-02 01:13:17,408 (engine:346): About to connect to uris ['qemu+ssh://10.66.5.110/system', 'qemu+ssh://root.4.218/system', 'qemu:///system']
connect : Connection refused
2011-08-02 01:13:17,423 (virt-manager:350): Connected to already running instance.
.........
2011-08-02 01:15:40,230 (connection:570): Connection managed save support: True
2011-08-02 01:15:40,428 (connection:160): Using libvirt API for netdev enumeration
2011-08-02 01:15:40,429 (connection:200): Using libvirt API for mediadev enumeration

double click a running guest on virt-manager:
output:

2011-08-02 01:16:24,505 (error:80): dialog message: Error launching details: 'AutoDrawer' object has no attribute 'set_has_window' : Error launching details: 'AutoDrawer' object has no attribute 'set_has_window'

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 741, in _show_vm_helper
    details = self._get_details_dialog(uri, uuid)
  File "/usr/share/virt-manager/virtManager/engine.py", line 720, in _get_details_dialog
    obj = vmmDetails(con.get_vm(uuid))
  File "/usr/share/virt-manager/virtManager/details.py", line 305, in __init__
    self.console = vmmConsolePages(self.vm, self.window)
  File "/usr/share/virt-manager/virtManager/console.py", line 562, in __init__
    self.init_fs_toolbar()
  File "/usr/share/virt-manager/virtManager/console.py", line 646, in init_fs_toolbar
    self.fs_drawer = AutoDrawer()
  File "/usr/share/virt-manager/virtManager/autodrawer.py", line 356, in __init__
    Drawer.__init__(self)
  File "/usr/share/virt-manager/virtManager/autodrawer.py", line 296, in __init__
    OverBox.__init__(self)
  File "/usr/share/virt-manager/virtManager/autodrawer.py", line 47, in __init__
    self.set_has_window(True)
AttributeError: 'AutoDrawer' object has no attribute 'set_has_window'


on virt-manager ,an error dialog shown up.

Expected results:
the guest can be opened.

Additional info:

Comment 3 Cole Robinson 2011-08-02 17:52:24 UTC
Fixed in virt-manager-0.9.0-5.el6

Comment 5 zhe peng 2011-08-03 02:51:55 UTC
Verify with :
virt-manager-0.9.0-5.el6
python-virtinst-0.600.0-2.el6
libvirt-0.9.4-0rc2.el6
qemu-kvm-0.12.1.2-2.172.el6

1.update to virt-manager-0.9.0.5.el6
2.#virt-manager --debug
3.click guest name on virt-manager

test both vnc and spice graphic guest, all worked well,guest can login,and no error message in debug log. 
Verification passed.

Comment 6 Cole Robinson 2011-11-07 16:41:10 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No description necessary

Comment 7 errata-xmlrpc 2011-12-06 16:14:46 UTC
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-2011-1642.html


Note You need to log in before you can comment on or make changes to this bug.