libguestfs appliances launched by nova will attempt to use KVM even if libvirt_type=qemu in nova.conf

Bug #1286257 reported by Lars Kellogg-Stedman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Confirmed
Low
Unassigned

Bug Description

The value of libvirt_type in nova.conf is not respected when Nova launches libguestfs appliances. This can cause problems were an administrator has explicitly set libvirt_type=qemu to work around KVM issues (or to test qemu). Newer versions of libguestfs support the 'force_tcg' option to disable the use of hardware emulation.

Revision history for this message
Lars Kellogg-Stedman (larsks) wrote :

Where "newer versions" means >= 1.25.23 (force_tcg introduced in libguestfs commit 11ac9f7).

Revision history for this message
Kashyap Chamarthy (kashyapc) wrote :

@Lars: Just to clarify: 'force_tcg' doesn't _disable_ use of hardware acceleration. It's an environment variable that will force libguestfs appliance to use software emulation.

From its man page[1]

    export LIBGUESTFS_BACKEND_SETTINGS=force_tcg

    which will force the 'direct' and 'libvirt' backends to use TCG (software emulation) instead of KVM (hardware accelerated virtualization).

  [1] http://libguestfs.org/guestfs.3.html#guestfs_set_backend_settings

Tracy Jones (tjones-i)
tags: added: libvirt
Solly Ross (sross-7)
Changed in nova:
importance: Undecided → Low
status: New → Confirmed
Matt Riedemann (mriedem)
tags: added: libguestfs
Revision history for this message
Dmitry Guryanov (dguryanov) wrote :

The same issue has been resolved - https://bugs.launchpad.net/nova/+bug/1286256

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.