virt-install fails to create guests with an --os-type other than linux

[Kai Blin]

Binary package hint: python-virtinst

On Kubuntu Hardy running virt-install 0.300.2-0ubuntu5 (both from the virt-manager GUI and from command line) fails to successfully create a VM when the OS type is set to unix.

To reproduce the error on the command line with a useful backtrace, use something like the following command line:

$ sudo virt-install -n pcbsd -r 512 --vcpus=1 -f /home/kai/vm/pcbsd/pcbsd.img -s 6000 -w bridge:br0 --accelerate --os-type=unix
Thu, 01 May 2008 09:29:33 ERROR 'virtio_blk'
Traceback (most recent call last):
  File "/usr/bin/virt-install", line 519, in <module>
    main()
  File "/usr/bin/virt-install", line 438, in main
    guest, hvm, conn)
  File "/usr/bin/virt-install", line 134, in get_disks
    disk, size)
  File "/usr/bin/virt-install", line 133, in <lambda>
    map(lambda d, s: get_disk(d, s, sparse, guest, hvm, conn),
  File "/usr/bin/virt-install", line 108, in get_disk
    d.virtio = 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'

Same error appears for --os-type=windows and --os-type=other

In the GUI, you notice that when selecting the OS type unix, windows or other, clicking "forward" on the "Assigning storage space" wizard page doesn't get you to a new page.

Changing the command line to
$ sudo virt-install -n pcbsd -r 512 --vcpus=1 -f /home/kai/vm/pcbsd/pcbsd.img -s 6000 -w bridge:br0 --accelerate --os-type=linux
makes it work.

At least for --os-type=windows this used to work some time ago in Hardy beta, as I did create windows guests before. I have seen numerous updates to kvm-related packages though, I guess one of them broke this.

[Jamie Strandboge (jdstrand)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 221746, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.