Answer by dbaxps for Hi, we currently switched from VNC to SPICE as concole used by nova. During this, we encountered the issue that the remote console type is defined on instance creation and switching the supported console does not changes this setting. This results in an "Unavailable console type spice" error, if you try to access the console on instances created previous to the change. We resolved this issue by changing the console type in the libvirt .xml machine describtion by hand (a script). After this change and a reboot of the Instance the SPICE console also works for the already existing instances in our cloud. To change the console for an instance manually, you have to change the following lines in the libvirt .xml configuration file for each instance. ( These files can usually be found at /etc/libvirt/ or you can access them with virsh edit <instance-name> ) In these line you have to set the 'type' from vnc to spice, thats all. <graphics type="vnc" autoport="yes" listen="0.0.0.0" keymap="en-us"> <listen type="address" address="0.0.0.0"/> </graphics> Only thing to do now is to restart the instance. This method works well for us but i like to know if there is a more convenient method especially for bigger setups. Or if i am messing somehow with the database, by changing this manually. I searched for a related entry in the nova tables of the database but didn't found anything. Thy Stefan

In regards of RDO Kilo , manual update of libvirt.xml doesn't make any sense. Libvirt.xml will be regenerated according classes and methods defined in virt/libvirt/config.py and virt/libvirt/driver.py after rebooting instance via nova. Details here :-
http://bderzhavets.blogspot.com/2015/06/enable-dashboard-spice-console-in-rdo.html
Original post for IceHouse by Y.Kawada
http://www.slideshare.net/YukihiroKawada/rdo-spice