diff options
| author | varac <varacanero@zeromail.org> | 2015-06-16 12:34:20 +0200 |
|---|---|---|
| committer | varac <varacanero@zeromail.org> | 2015-06-16 12:34:28 +0200 |
| commit | 0b1a403c1a21ae4f8606a91c7ca787a1d0fb1cd8 (patch) | |
| tree | 920cda28394f7625cc6793e80e9a7c383c7f549f /pages/docs | |
| parent | 4f7f95cd7aff0bc590cbf983751b7feff7013f0f (diff) | |
use dots instead of stars so code is displayed as code
Diffstat (limited to 'pages/docs')
| -rw-r--r-- | pages/docs/platform/details/development.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/pages/docs/platform/details/development.md b/pages/docs/platform/details/development.md index 8df2bbb..b13de53 100644 --- a/pages/docs/platform/details/development.md +++ b/pages/docs/platform/details/development.md @@ -344,12 +344,12 @@ Now you should be able to use the `leap local` commands. 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 -* 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) +. '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 +. 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-serve |