diff options
author | Dan Prince <dprince@redhat.com> | 2013-02-21 15:28:38 -0500 |
---|---|---|
committer | Dan Prince <dprince@redhat.com> | 2013-02-22 09:54:38 -0500 |
commit | 014499acf5d6d6a557c9415aa49c536817a02a0a (patch) | |
tree | aef210b0f9f8934279f62ba3f1be27c805387964 /nova/utils.py | |
parent | 4f0c2ddcf69d838b4954749091ae0056aa46ef07 (diff) | |
download | nova-014499acf5d6d6a557c9415aa49c536817a02a0a.tar.gz nova-014499acf5d6d6a557c9415aa49c536817a02a0a.tar.xz nova-014499acf5d6d6a557c9415aa49c536817a02a0a.zip |
Make guestfs use same libvirt URI as Nova.
Updates our libguestfs vfs implementation so that it makes use of
the same libvirt connection URI as Nova does when using
attach mode 'libvirt'. Previously when libguestfs used attach
mode 'libvirt' (the default on some newer distros like Fedora 18)
you could get permissions issues and ultimately get a libvirt
connection error from libguestfs:
could not connect to libvirt (URI = NULL)
Docs on guestfs attach method can be found here:
http://libguestfs.org/guestfs.3.html#attach-method
Having libguestfs use the same connection URL as Nova makes sense
and gets past these permission issues. (avoiding things like forcing
you to create a $HOME dir for the nova user among other things)
Full thread on this is here:
https://bugzilla.redhat.com/show_bug.cgi?id=913345
Note that on most distros the default libguestfs attach method
is still 'appliance' so this would have no affect unless explicitly
enabled via LIBGUESTFS_ATTACH_METHOD.
Fixes LP Bug #1131768.
Change-Id: I7e9f010022731a43e8d793cf8415ec12b346fdb4
Diffstat (limited to 'nova/utils.py')
0 files changed, 0 insertions, 0 deletions