From: eoli3n <eoli3n@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] [package request] vagrant-libvirt
Date: Sat, 29 Jan 2022 20:56:46 +0100 [thread overview]
Message-ID: <20220129195646.KtVsk9qLOtm7oUhbEMCCBA1mn5n_Z0GsH88GlFrkMTI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35292@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]
Closed issue by eoli3n on void-packages repository
https://github.com/void-linux/void-packages/issues/35292
Description:
I can't get vagrant-libvirt vagrant plugin to work with the current vagrant version.
Here the playbook I use to setup
```yaml
---
- name: install virt packages
community.general.xbps:
name: '{{item}}'
loop:
- qemu
- libvirt
- virt-manager
- virt-manager-tools
- dnsmasq
- vagrant
# For vagrant-libvirt
- libvirt-devel
- libguestfs
- libxslt-devel
- libxml2-devel
notify: restart libvirt
- name: add user to libvirt group
user:
name: '{{user}}'
groups: libvirt
append: yes
```
Then with my user
```bash
➜ vagrant plugin install vagrant-libvirt
You appear to be running Vagrant outside of the official installers.
Note that the installers are what ensure that Vagrant has all required
dependencies, and Vagrant assumes that these dependencies exist. By
running outside of the installer environment, Vagrant may not function
properly. To remove this warning, install Vagrant using one of the
official packages from vagrantup.com.
Installing the 'vagrant-libvirt' plugin. This can take a few minutes...
Building native extensions. This could take a while...
Vagrant failed to install the requested plugin because it depends
on a library which is not currently installed on this system. The
following library is required by the 'vagrant-libvirt' plugin:
libvirt
Please install the library and then run the command again.
```
Related issue for fedora ? https://github.com/vagrant-libvirt/vagrant-libvirt/issues/1403
next prev parent reply other threads:[~2022-01-29 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 11:15 [ISSUE] " eoli3n
2022-01-29 19:56 ` eoli3n [this message]
2022-01-29 19:56 ` eoli3n
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220129195646.KtVsk9qLOtm7oUhbEMCCBA1mn5n_Z0GsH88GlFrkMTI@z \
--to=eoli3n@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).