summaryrefslogtreecommitdiff
path: root/pages
diff options
context:
space:
mode:
Diffstat (limited to 'pages')
-rw-r--r--pages/docs/platform/tutorials/vagrant.md4
1 files changed, 1 insertions, 3 deletions
diff --git a/pages/docs/platform/tutorials/vagrant.md b/pages/docs/platform/tutorials/vagrant.md
index 710c266..a741b1b 100644
--- a/pages/docs/platform/tutorials/vagrant.md
+++ b/pages/docs/platform/tutorials/vagrant.md
@@ -302,7 +302,7 @@ By default, Vagrant will use VirtualBox to create the virtual machines, but this
sudo apt-get install ruby-dev libxslt-dev libxml2-dev libvirt-dev
# install the required plugins
- vagrant plugin install vagrant-libvirt fog fog-libvirt sahara
+ vagrant plugin install vagrant-libvirt sahara
Log out and then log back in.
@@ -353,8 +353,6 @@ Known issues
* `Call to virConnectOpen failed: internal error: Unable to locate libvirtd daemon in /usr/sbin (to override, set $LIBVIRTD_PATH to the name of the libvirtd binary)` - you don't have the libvirtd daemon running or installed, be sure you installed the 'libvirt-bin' package and it is running
* `Call to virConnectOpen failed: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied` - you need to be in the libvirt group to access the socket, do 'sudo adduser <user> libvirtd' and then re-login to your session.
* if each call to vagrant ends up with a segfault, it may be because you still have virtualbox around. if so, remove virtualbox to keep only libvirt + KVM. according to https://github.com/pradels/vagrant-libvirt/issues/75 having two virtualization engines installed simultaneously can lead to such weird issues.
-* see the [vagrant-libvirt issue list on github](https://github.com/pradels/vagrant-libvirt/issues)
-* be sure to use vagrant-libvirt >= 0.0.11 and sahara >= 0.0.16 (which are the latest stable gems you would get with `vagrant plugin install [vagrant-libvirt|sahara]`) for proper libvirt support,
Useful commands
------------------------