virt-manager traceback if select an architecture on VM creation

Bug #453467 reported by Jamie Strandboge on 2009-10-16
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
virt-manager (Ubuntu)
Low
Unassigned
Karmic
Low
Unassigned

Bug Description

Binary package hint: virt-manager

Steps to reproduce:

1. start virt-manager, connect to the 'localhost (System)', then click New
2. enter name of vm eg 'testme' and use local install media, click Forward
3. select an iso to use, with OS type Generic and Version Generic, click Forward
4. leave memory and CPUs as defaults, click Forward
5. enable storage for the VM, but don't allocate all of it now, click Forward
6. Click Advanced options, and choose an architecture, click Finish

While the VM starts, you do not get the VNC window like normal. Instead, you get the following:

Error bringing up domain details: 'NoneType' object has no attribute 'get_driver'

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 272, in show_details
    details = vmmDetails(self.get_config(), con.get_vm(uuid), self)
  File "/usr/share/virt-manager/virtManager/details.py", line 337, in __init__
    self.update_widget_states(self.vm, self.vm.status())
  File "/usr/share/virt-manager/virtManager/details.py", line 783, in update_widget_states
    self.set_migrate_menu()
  File "/usr/share/virt-manager/virtManager/details.py", line 730, in set_migrate_menu
    self.engine.populate_migrate_menu(menu, self.control_vm_migrate)
  File "/usr/share/virt-manager/virtManager/engine.py", line 578, in populate_migrate_menu
    conns = self.get_available_migrate_hostnames()
  File "/usr/share/virt-manager/virtManager/engine.py", line 601, in get_available_migrate_hostnames
    driver = self.windowManager.current_connection().get_driver()
AttributeError: 'NoneType' object has no attribute 'get_driver'

ProblemType: Bug
Architecture: amd64
Date: Fri Oct 16 15:36:30 2009
DistroRelease: Ubuntu 9.10
LiveMediaBuild: Ubuntu 9.04 "Jaunty Jackalope" - Release amd64 (20090420.1)
Package: virt-manager 0.7.0-3ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.47-generic
SourcePackage: virt-manager
Uname: Linux 2.6.31-14-generic x86_64

Jamie Strandboge (jdstrand) wrote :
summary: - virt-manager traceback if select an architecture
+ virt-manager traceback if select an architecture on VM creation
Jamie Strandboge (jdstrand) wrote :

You may have to first delete a VM before the above steps work.

tags: added: regression-potential
Changed in virt-manager (Ubuntu):
importance: Undecided → Low
status: New → Confirmed
Thierry Carrez (ttx) wrote :

Per 20091020 meeting

Changed in virt-manager (Ubuntu Karmic):
status: Confirmed → Won't Fix
Jamie Strandboge (jdstrand) wrote :

This is a regression over 9.04, which has a different wizard for creating a vm. Tested using qemu/mips.

tags: added: regression-release
removed: regression-potential
Marc Deslauriers (mdeslaur) wrote :

Jamie, is this still an issue with virt-manager in Lucid?

Changed in virt-manager (Ubuntu):
status: Confirmed → Incomplete
assignee: nobody → Jamie Strandboge (jdstrand)
Jamie Strandboge (jdstrand) wrote :

This is fixed in Lucid.

Changed in virt-manager (Ubuntu):
assignee: Jamie Strandboge (jdstrand) → nobody
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers