"libvirtError: internal error cannot determine default video type" when using UML

Bug #805083 reported by Matt Thompson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
High
Unassigned

Bug Description

Hello,

I received the following error while trying to spawn UML instances on version 2011.3-dev:

(nova.exception): TRACE: Traceback (most recent call last):
(nova.exception): TRACE: File "/usr/lib/pymodules/python2.6/nova/exception.py", line 87, in _wrap
(nova.exception): TRACE: return f(*args, **kw)
(nova.exception): TRACE: File "/usr/lib/pymodules/python2.6/nova/virt/libvirt/connection.py", line 591, in spawn
(nova.exception): TRACE: domain = self._create_new_domain(xml)
(nova.exception): TRACE: File "/usr/lib/pymodules/python2.6/nova/virt/libvirt/connection.py", line 1085, in _create_new_domain
(nova.exception): TRACE: domain = self._conn.defineXML(xml)
(nova.exception): TRACE: File "/usr/lib/python2.6/dist-packages/libvirt.py", line 1368, in defineXML
(nova.exception): TRACE: if ret is None:raise libvirtError('virDomainDefineXML() failed', conn=self)
(nova.exception): TRACE: libvirtError: internal error cannot determine default video type
(nova.exception): TRACE:

This appears to be similar to the LXC issue outlined (and fixed) in https://bugs.launchpad.net/nova/+bug/749973.

As a workaround, I copied /usr/share/pyshared/nova/virt/libvirt.xml.template to /etc/nova/libvirt.xml.template, removed the vnc stuff from /etc/nova/libvirt.xml.template, added --libvirt_xml_template=/etc/nova/libvirt.xml.template to /etc/nova/nova.conf, and restarted nova-compute.

Let me know if you need any further info or if I'm doing something wrong to hit this 'bug'.

Thanks!

-Matt

Related branches

Revision history for this message
Chuck Short (zulcss) wrote :

This is due to uml not understanding vnc in libvirt

Changed in nova:
status: New → Confirmed
Thierry Carrez (ttx)
Changed in nova:
assignee: nobody → Chuck Short (zulcss)
importance: Undecided → High
status: Confirmed → In Progress
Thierry Carrez (ttx)
Changed in nova:
status: In Progress → Fix Committed
Revision history for this message
Matt Thompson (mattt416) wrote :

Hi all,

This doesn't appear to have resolved the issue for me. If I change the if statement in nova/virt/libvirt/connection.py from:

if FLAGS.libvirt_type != 'lxc' or FLAGS.libvirt_type != 'uml':

to:

if FLAGS.libvirt_type != 'lxc' and FLAGS.libvirt_type != 'uml':

... my libvirt.xml looks good and my instance boots as expected.

In other news, I could simply have added "--vnc_enabled=false" to /etc/nova/nova.conf rather than use an alternate /usr/share/pyshared/nova/virt/libvirt.xml.template file.

Thanks!

-Matt

Revision history for this message
Thierry Carrez (ttx) wrote :

Oh, good catch.

(FLAGS.libvirt_type != 'lxc' or FLAGS.libvirt_type != 'uml') is actually always True.

Changed in nova:
status: Fix Committed → Triaged
assignee: Chuck Short (zulcss) → nobody
Revision history for this message
Thierry Carrez (ttx) wrote :

This wa812553

Revision history for this message
Thierry Carrez (ttx) wrote :

I mean: The regression was actually fixed as bug 812553

Changed in nova:
status: Triaged → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → diablo-3
Thierry Carrez (ttx)
Changed in nova:
milestone: diablo-3 → 2011.3
status: Fix Committed → Fix Released
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.