vagrant fails to create box with libvirt

Question

I am using Neovim on windows, as well as the vim-fugitive plugin. The plugin has a command that pushes commits, Gpush. I get an error saying "permission denied (publickey) fatal: could not read from remote repository. I am using an ssh key, everything works fine in a console but not with the plugin. I can't find anyone else with the same issue online.

Solution 1

I got this Error while connecting to libvirt error but it was simply a case that I was running vagrant up without specifying the provider.

In my case I needed

$ vagrant up --provider virtualbox

Solution 2

I got this error while trying to start a Vagrant machine up, without having Virtualbox initially installed (although I had previously written I needed it).

Installing Virtualbox fixed this issue right away.

Solution 3

I also had this error on a pretty much fresh install of Ubuntu 19.10.

When I did: vagrant up --provider virtualbox

I got this error message

The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:

Vagrant has detected that you have a version of VirtualBox installed
that is not supported by this version of Vagrant. Please install one of
the supported versions listed below to use Vagrant:

4.0, 4.1, 4.2, 4.3, 5.0, 5.1, 5.2, 6.0

A Vagrant update may also be available that adds support for the version
you specified. Please check www.vagrantup.com/downloads.html to download
the latest version

So this helped in my case: sudo apt-get install virtualbox-6.0

Solution 4

I too had this same issue. To fix it I had to essentially follow this guide : http://wiki.libvirt.org/page/TLSSetup

Note that the guide has multiple steps and it is LONG. Its not an "easy" fix though once you have the CAcert/key HostCert/key and ClientCert/key all in place, with the correct permissions and the correct ownership, everything works as expected.

thanks for reporting this and I hope this helps.

View more solutions

Comments

[S.Roshanth]

I hit the same issue, it's due to secure booting and signing issue. follow the link below if you are using version Ubuntu 20.04, virtualbox 6.1 stackoverflow.com/questions/61248315/…,

[Ethan Fischer]

Didn't work for me on ubuntu 20.04

[VonC]

@EthanFischer What version of Git do you have?

[Ethan Fischer]

2.25.1 Also I think the issue in my case was that I had initially pulled my repo from github using http. After removing the http remote and replacing it with the ssh one, everything works as expected

[VonC]

@Eth good call, well done.