You are not logged in.
Hi all,
I use vagrant to test some service while I develop, today after update vagrant from 2.2.6-1 to 2.2.6-3 not "recognize" the plugin vagrant-libvirt, for example, I start a vm with
vagrant up --provider=libvirt vm01But I get
Bringing machine 'vm01' up with 'libvirt' provider...
Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.
Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires
this to be available on the PATH. If VirtualBox is installed, please find the
`VBoxManage` binary and add it to the PATH environmental variable.obviously I set
VAGRANT_DEFAULT_PROVIDER="libvirt"before use --provider in the command
and have installed the plugins
$ vagrant plugin list
vagrant-cachier (1.2.1, global)
vagrant-disksize (0.1.3, global)
vagrant-hosts (2.9.0, global)
vagrant-libvirt (0.0.45, global)Any idea why vagrant can't detect libvirt?
Cheers.
Last edited by dubcl (2020-01-20 17:32:30)
-- dub
Offline
Step #1 - try to enable debug logs, it might provide more useful information https://superuser.com/questions/804214/ … rbose-mode
There are multiple changes happen in this area recently:
vagrant-2.2.6-2 - adds some virtualbox related packages
vagrant-2.2.6-3 rebuilt the package for ruby 2.7
libvirt has been updated
ovmf has been updated (not sure if it can cause such issue but worth mentioning this update anyway)
virtualbox 6.1 update
You need to find out which update caused the problem. Please try to downgrade to the prev version of the package and see if it changes the situation for you.
Read it before posting http://www.catb.org/esr/faqs/smart-questions.html
Ruby gems repository done right https://bbs.archlinux.org/viewtopic.php?id=182729
Fast initramfs generator with security in mind https://wiki.archlinux.org/index.php/Booster
Offline
Hi anatolik, thanks for you response.
Finally the problem was the plugin vagrant-disksize, I remove the plugin and vagrant work well again.
Cheers.
-- dub
Offline