Using libvirt connection and Xen, whenever I try to attach a volume to an instance I get:
2011-11-14 13:51:29,765 ERROR nova.exception [-] Uncaught exception
(nova.exception): TRACE: Traceback (most recent call last):
(nova.exception): TRACE: File "/usr/lib/python2.6/dist-packages/nova/exception.py", line 98, in wrapped
(nova.exception): TRACE: return f(*args, **kw)
(nova.exception): TRACE: File "/usr/lib/python2.6/dist-packages/nova/virt/libvirt/connection.py", line 372, in attach
_volume
(nova.exception): TRACE: virt_dom.attachDevice(xml)
(nova.exception): TRACE: File "/usr/lib/python2.6/dist-packages/libvirt.py", line 400, in attachDevice
(nova.exception): TRACE: if ret == -1: raise libvirtError ('virDomainAttachDevice() failed', dom=self)
(nova.exception): TRACE: libvirtError: POST operation failed: xend_post: error from xen daemon: (xend.err 'Block device
type "quemu" is invalid.')
Reviewed: https:/ /review. openstack. org/1580 github. com/openstack/ nova/commit/ aa7dd96f1c23b29 bd2cabd57d579f2 c3b0fe678a
Committed: http://
Submitter: Jenkins
Branch: master
status fixcommitted
done
commit aa7dd96f1c23b29 bd2cabd57d579f2 c3b0fe678a
Author: Alvaro Lopez <email address hidden>
Date: Mon Nov 14 16:58:05 2011 +0100
Fixes bug 890206
Add a check when creating the volume definition for the libvirt manager
to use the apporpiate driver for the disk, according to [1].
[1] http:// libvirt. org/formatdomai n.html# elementsDisks
Change-Id: I89cf3bb308cff2 8194de0beb36d69 f0e32224cbe