diff options
| author | varac <varacanero@zeromail.org> | 2014-09-23 17:17:37 +0200 |
|---|---|---|
| committer | varac <varacanero@zeromail.org> | 2014-09-23 17:17:37 +0200 |
| commit | 7f44b739c95625296c4a916ba1674ad908b8be45 (patch) | |
| tree | 2cab00f0a55c3abb20775545f0f90bfdd8009a80 | |
| parent | 0da3ebcedc6c5a27bd995412e9a7cb17c46c711b (diff) | |
updated vagrant notes in development.md
| -rw-r--r-- | docs/platform/development.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/platform/development.md b/docs/platform/development.md index 57c296d..8138c5d 100644 --- a/docs/platform/development.md +++ b/docs/platform/development.md @@ -307,4 +307,7 @@ Known Issues * 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 -* for shared folder support, you need nfs-kernel-server installed on the host machine and set up sudo to allow unpriviledged users to modify /etc/exports and ..... +* for shared folder support, you need nfs-kernel-server installed on the host machine and set up sudo to allow unpriviledged users to modify /etc/exports. See [vagrant-libvirt#synced-folders](https://github.com/pradels/vagrant-libvirt#synced-folders) + + + sudo apt-get install nfs-kernel-server |