vagrant-libvirt | Vagrant provider for libvirt | Plugin library

 by   vagrant-libvirt Ruby Version: 0.12.1 License: MIT

kandi X-RAY | vagrant-libvirt Summary

kandi X-RAY | vagrant-libvirt Summary

vagrant-libvirt is a Ruby library typically used in Telecommunications, Media, Media, Entertainment, Plugin, Ansible applications. vagrant-libvirt has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

This is a Vagrant plugin that adds a Libvirt provider to Vagrant, allowing Vagrant to control and provision machines via Libvirt toolkit. Note: Actual version is still a development one. Feedback is welcome and can help a lot :-).
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              vagrant-libvirt has a medium active ecosystem.
              It has 2172 star(s) with 490 fork(s). There are 77 watchers for this library.
              There were 1 major release(s) in the last 12 months.
              There are 77 open issues and 790 have been closed. On average issues are closed in 515 days. There are 3 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of vagrant-libvirt is 0.12.1

            kandi-Quality Quality

              vagrant-libvirt has 0 bugs and 29 code smells.

            kandi-Security Security

              vagrant-libvirt has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              vagrant-libvirt code analysis shows 0 unresolved vulnerabilities.
              There are 8 security hotspots that need review.

            kandi-License License

              vagrant-libvirt is licensed under the MIT License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              vagrant-libvirt releases are available to install and integrate.
              Installation instructions, examples and code snippets are available.
              vagrant-libvirt saves you 2585 person hours of effort in developing the same functionality from scratch.
              It has 5616 lines of code, 206 functions and 73 files.
              It has medium code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of vagrant-libvirt
            Get all kandi verified functions for this library.

            vagrant-libvirt Key Features

            No Key Features are available at this moment for vagrant-libvirt.

            vagrant-libvirt Examples and Code Snippets

            No Code Snippets are available at this moment for vagrant-libvirt.

            Community Discussions

            QUESTION

            Command 'vagrant' not found
            Asked 2020-Sep-30 at 22:54

            I am re-installing vagrant on my local machine unsuccessfully. Initially, I had vagrant downloaded, installed and running well, but decided to uninstall it. My uninstall was as follows:

            ...

            ANSWER

            Answered 2020-Sep-30 at 22:54

            As you just removed the files instead of using apt-get or dpkg to uninstall the package, the package management is not aware of your manual removal, and so apt-get and dpkg still think the newest version is already installed, and so do nothing.

            apt-get --reinstall install vagrant

            should solve this.

            Source https://stackoverflow.com/questions/64129477

            QUESTION

            Vagrant how to install 'vagrant-disksize' plugin
            Asked 2020-Aug-22 at 17:26

            On Ubunto 18 and Windows 10 Vagrant could install vagrant-disksize plugin, configured as:

            ...

            ANSWER

            Answered 2020-Aug-22 at 17:26

            I could install the plugin manually via vagrant plugin install vagrant-disksize command.

            Via Vagrant itself, it is still not working.

            Source https://stackoverflow.com/questions/63509800

            QUESTION

            Unable to add Raspbian image to Vagrant-libvirt Virtual machine
            Asked 2019-Sep-09 at 07:03

            Am trying to create a virtual machine for Raspbian using Vagrant-libvirt plugin. However I failed find out how to add '2017-09-07-raspbian-stretch-lite.img' image.

            Am able to boot the image using qemu.

            qemu-system-arm -kernel kernel-qemu-4.4.34-jessie -cpu arm1176 -m 256 -machine versatilepb -append "root=/dev/sda2 panic=1 rootfstype=ext4 rw vga=normal console=ttyAMA0" -drive "file=./2017-09-07-raspbian-stretch-lite.img,index=0,media=disk,format=raw" -no-reboot -serial stdio -curses

            Here is my incomplete Vagrantfile:

            ...

            ANSWER

            Answered 2017-Sep-28 at 09:34

            I've committed support to vagrant-libvirt for precisely this. This is a working config:

            Source https://stackoverflow.com/questions/46380695

            QUESTION

            `vagrant up` times out at "Waiting for domain to get an IP address..."
            Asked 2019-Aug-04 at 07:36

            This appears to only happen when I'm using the generic/arch box. I've tried several ubuntu boxes and everything works fine.

            Host OS is Manjaro.

            It's freezing with output:

            ...

            ANSWER

            Answered 2018-Jan-26 at 06:08

            Since you are using the libvirt provider, you should be able to check out the state of the virtual machine with virt-manager.

            The rest of the answer is written under the two assumptions that my system is not so different from yours and that I have run into the same problem using vagrant-libvirt and generic/arch (v1.3.40)

            Opening the VM in virt-manager, I've found out that the system cannot detect the root filesystem and also boots into an emergency shell. That's because the initramfs-linux.img provided by the generic/arch box does not include the necessary kernel modules for the default settings that the libvirt-provider with QEMU/kvm uses.

            If it's somehow important to boot this box, you should be able to start the box by using the fallback image because it ships more modules. To make it rebootable without intervention, you can run sudo mkinitcpio -p linux to add the missing modules in the guest. Alternatively, you could also change the SCSI controller from Hypervisor Defaults to VirtIO SCSI (eg. with virt-manager) on the host.

            For a more permanent solution (nothing of the aforementioned would survive a vagrant destroy), there ist not much to be done - besides maybe waiting for a "fixed" release of the box or patching the plugin.

            ps. The easiest solution would probably be to pick another box (e.g. archlinux/archlinux).

            Source https://stackoverflow.com/questions/48271741

            QUESTION

            vagrant up hangs on ssh
            Asked 2017-May-15 at 15:32

            I did vagrant up --provision libvirt and it hangs on:

            ...

            ANSWER

            Answered 2017-May-15 at 15:32

            I ran into similar issue when trying to run vagrant up --provider=lxc I got it fixed simply by checking to see if any ruby/vagrant process was already running and kill it. FYI, In my case, the vagrant up process initiated by me prior to the current run was still running.

            Source https://stackoverflow.com/questions/43981877

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install vagrant-libvirt

            First, you should have both QEMU and Libvirt installed if you plan to run VMs on your local system. For instructions, refer to your Linux distribution's documentation. NOTE: Before you start using vagrant-libvirt, please make sure your Libvirt and QEMU installation is working correctly and you are able to create QEMU or KVM type virtual machines with virsh or virt-manager. Next, you must have Vagrant installed. Vagrant-libvirt supports Vagrant 2.0, 2.1 & 2.2. It should also work with earlier releases from 1.5 onwards but they are not actively tested. Check the unit tests for the current list of tested versions. We only test with the upstream version! If you decide to install your distro's version and you run into problems, as a first step you should switch to upstream.
            Ubuntu 18.10, Debian 9 and up:
            Ubuntu 18.04, Debian 8 and older:
            CentOS 6, 7, Fedora 21:
            Fedora 22 and up:
            OpenSUSE leap 15.1:
            Arch Linux: please read the related ArchWiki page.
            Fedora 32 + upstream Vagrant: export CONFIGURE_ARGS="with-libvirt-include=/usr/include/libvirt with-libvirt-lib=/usr/lib64"

            Support

            vagrant-libvirt supports using QEMU user sessions to maintain Vagrant VMs. As the session connection does not have root access to the system features which require root will not work. Access to networks created by the system QEMU connection can be granted by using the QEMU bridge helper. The bridge helper is enabled by default on some distros but may need to be enabled/installed on others. There must be a virbr network defined in the QEMU system session. The libvirt default network which comes by default, the vagrant vagrant-libvirt network which is generated if you run a Vagrantfile using the System session, or a manually defined network can be used. These networks can be set to autostart with sudo virsh net-autostart <net-name>, which'll mean no further root access is required even after reboots. The QEMU bridge helper is configured via /etc/qemu/bridge.conf. This file must include the virbr you wish to use (e.g. virbr0, virbr1, etc). You can find this out via sudo virsh net-dumpxml <net-name>.
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/vagrant-libvirt/vagrant-libvirt.git

          • CLI

            gh repo clone vagrant-libvirt/vagrant-libvirt

          • sshUrl

            git@github.com:vagrant-libvirt/vagrant-libvirt.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link