virt-manager unresponsive - KeyError 'virtio_blk'

Bug #221552 reported by cros13
4
Affects Status Importance Assigned to Milestone
virt-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: virt-manager

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/create.py", line 295, in forward
    if(self.validate(notebook.get_current_page()) != True):
  File "/usr/share/virt-manager/virtManager/create.py", line 915, in validate
    self._disk.virtio = self._guest.get_virtio_blk()
  File "/usr/lib/python2.5/site-packages/virtinst/FullVirtGuest.py", line 206, in get_virtio_blk
    return FullVirtGuest.OS_TYPES[self.os_type]["virtio_blk"]
KeyError: 'virtio_blk

Revision history for this message
Matti Laakso (matti-laakso) wrote :

Same thing here. This happens when OS-type is windows, kernel/hardware acceleration is enabled, and I press 'next' in the dialog where I have to choose where to install the virtualized system.

Changed in virt-manager:
assignee: nobody → jdstrand
status: New → Confirmed
assignee: jdstrand → nobody
Revision history for this message
Ryan Bair (dr.bair) wrote :

This also affects virt-install.

Revision history for this message
Ryan Bair (dr.bair) wrote :

Here's a patch which should correct this problem. The dicts which contained the settings for everything except Linux were missing the virtio_blk and virtio_net keys. It would also be possible to change the behavior of the get_virtio_{net|blk} functions to return the default if the ostype didn't have the key, but assuming the os_type has all the options seems to be more inline with the rest of the program.

After this I was able to create and start windows-winxp and unix-freebsd6 variants.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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