View Issue Details

IDProjectCategoryView StatusLast Update
0007885Kali LinuxGeneral Bugpublic2022-10-24 07:27
Reporterdachiefjustice Assigned Todaniruiz  
Status resolvedResolutionfixed 
Product Version2022.3 
Fixed in Version2022.4 
Summary0007885: Vagrant kalilinux/rolling Virtualbox broken (2022.3.1, 2022.3.2)

When attempting to use the Virtualbox provider of kalilinux/rolling Vagrant box (with either 2022.3.1 or 2022.3.2), issuing any Vagrant command causes the following error

Vagrant failed to initialize at a very early stage:

There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
a syntax error.

Path: <provider config: libvirt>
Line number: 27
Message: NameError: undefined local variable or method `v' for main:Object

Steps To Reproduce

On a host with Vagrant and Virtualbox installed:

vagrant init kalilinux/rolling
vagrant up

This will trigger the error.

Additional Information

This issue appears to have started with 2022.3 versions, and seems to be specific to the libvirt provider. AFAICT, libvirt support was included in the kalilinux/rolling box since 2022.3.1 (which is the first version where I experienced this issue)

Workaround is to version-pin to 2022.2.0 in a line in the Vagrantfile:
config.vm.box_version = "2022.2.0" # avoid libvirt error




2022-08-28 23:10

reporter   ~0016667

When people follow the "Kali Inside Vagrant" doc ( they'll likely encounter this issue.

So I was thinking, the folks who maintain the Vagrant Kali boxes might want to know about this.

The issue seems to have appeared with 2022.3.1 (the first box version that has libvirt support)



2022-10-09 19:40

reporter   ~0016947

This should be fixed now according to this GitLab issue:

You'll probably have to do something like vagrant box remove kalilinux/rolling to remove the old version and then you could do a vagrant up again.



2022-10-10 16:22

reporter   ~0016952

Yup -- this issue is fixed now (with kalilinux/rolling 2022.3.2).

To apply the fix, I did the following:
1) vagrant destroy -f
2) Remove the version-pin line from the Vagrantfile
3) vagrant box remove kalilinux/rolling --all (clear Vagrant's cached box versions)
4) vagrant up

This issue can be closed/resolved now.

Issue History

Date Modified Username Field Change
2022-08-22 22:17 dachiefjustice New Issue
2022-08-28 23:10 dachiefjustice Note Added: 0016667
2022-10-09 19:40 elrey Note Added: 0016947
2022-10-10 16:22 dachiefjustice Note Added: 0016952
2022-10-24 07:27 daniruiz Assigned To => daniruiz
2022-10-24 07:27 daniruiz Status new => resolved
2022-10-24 07:27 daniruiz Resolution open => fixed
2022-10-24 07:27 daniruiz Fixed in Version => 2022.4