diff options
| author | Gabriel Filion <gabster@lelutin.ca> | 2013-11-13 02:21:56 -0500 |
|---|---|---|
| committer | Gabriel Filion <gabster@lelutin.ca> | 2013-11-13 02:26:14 -0500 |
| commit | bb0de27c6437749bd4fe1c12d9be0c59d916e975 (patch) | |
| tree | 86078b2bcb6ecbf72b558ea73ae5c13d5e52e0cf | |
| parent | ab6163d4e7afd1a76c20d68c3bf50ae861d63226 (diff) | |
remove virtualbox packages during the procedure
also mention the segfaults that keeping virtualbox around can cause:
this can be very confusing at first. making people remove virtualbox
will reduce confusion.
| -rw-r--r-- | docs/platform/development.md | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/docs/platform/development.md b/docs/platform/development.md index 3c3e5bb..264c647 100644 --- a/docs/platform/development.md +++ b/docs/platform/development.md @@ -227,9 +227,12 @@ Install vagrant-libvirt plugin and add box ------------------------------------------ sudo apt-get install libvirt-bin libvirt-dev vagrant plugin install vagrant-libvirt - vagrant plugin install sahara + vagrant plugin install sahara vagrant box add leap-wheezy https://downloads.leap.se/leap-debian-libvirt.box +Remove Virtualbox +----------------- + sudo apt-get remove virtualbox* Debugging --------- @@ -268,5 +271,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> libvirt' 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 |