Ubuntu
virt-manager package

virt-manager 0.6.1-1ubuntu1 fails to start

Bug #332108 reported by Márcio Santos
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
virt-manager (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Jaunty by Popa Adrian Marius

Bug Description

Binary package hint: virt-manager

$ lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04

$ apt-cache policy virt-manager
virt-manager:
  Installed: 0.6.1-1ubuntu1
  Candidate: 0.6.1-1ubuntu1
  Version table:
 *** 0.6.1-1ubuntu1 0
        500 http://archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

Running Jaunty Alpha 4.
Installed virt-manager 0.6.1-1ubuntu1 for testing and it refuses to start.
Running with --debug --no-fork returns:

2009-02-20 15:39:00,599 INFO Application startup
2009-02-20 15:39:00,895 DEBUG About to connect to uris []
2009-02-20 15:39:00,902 ERROR global name 'engine' is not defined
Traceback (most recent call last):
  File "/usr/share/virt-manager/virt-manager.py", line 374, in <module>
    main()
  File "/usr/share/virt-manager/virt-manager.py", line 361, in main
    options.no_conn_auto)
  File "/usr/share/virt-manager/virt-manager.py", line 236, in show_engine
    tryuri = default_uri()
  File "/usr/share/virt-manager/virt-manager.py", line 197, in default_uri
    engine.add_connection("qemu:///session")
NameError: global name 'engine' is not defined
2009-02-20 15:39:00,925 DEBUG Uncaught Error: Error starting Virtual Machine Manager: global name 'engine' is not defined : Traceback (most recent call last):
  File "/usr/share/virt-manager/virt-manager.py", line 374, in <module>
    main()
  File "/usr/share/virt-manager/virt-manager.py", line 361, in main
    options.no_conn_auto)
  File "/usr/share/virt-manager/virt-manager.py", line 236, in show_engine
    tryuri = default_uri()
  File "/usr/share/virt-manager/virt-manager.py", line 197, in default_uri
    engine.add_connection("qemu:///session")
NameError: global name 'engine' is not defined

Chad Waters (chad)
Changed in virt-manager:
status: New → Confirmed
Revision history for this message
Aaron Kurtz (a.kurtz) wrote :

This is a problem with virt-manager 0.6.1-1ubuntu3 as well, as upgrading did not fix this.

It also does not appear to be a problem when running on a separate machine that automatically connects to my KVM-using libvirt host, only when run locally on the KVM machine.

Revision history for this message
Brazen (jdinkel) wrote :

Also having this problem in virt-manager 0.6.1-1ubuntu3 after a fresh install of Jaunty Alpha 5.

Revision history for this message
Brazen (jdinkel) wrote :

I found a workaround for this by specifying the uri at the command line. For instance start it with this command: 'sudo virt-manager -c qemu:///system' and it starts up fine. I haven't created any storage groups or virtual machines yet, but it does get past this bug.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package virt-manager - 0.6.1-1ubuntu4

---------------
virt-manager (0.6.1-1ubuntu4) jaunty; urgency=low

  * Pass engine object to default_uri. (LP: #332108)

 -- Soren Hansen <email address hidden> Mon, 02 Mar 2009 10:05:37 -0800

Changed in virt-manager:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.