You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now Vagrant file configures win2k8 box to run using libvirt provider but as I can see in Vagrant Cloud there is no such provider available:
Host System
OS: ArchLinux
Packer Version: v1.9.1
Vagrant Version: 2.3.6
VirtualBox Version: 7.0.8
Command Output
So one that try to get this box up get the error:
$ vagrant up win2k8
Bringing machine 'win2k8' up with 'libvirt' provider...
==> win2k8: Box 'rapid7/metasploitable3-win2k8' could not be found. Attempting to find and install...
win2k8: Box Provider: libvirt
win2k8: Box Version: >= 0
==> win2k8: Loading metadata for box 'rapid7/metasploitable3-win2k8'
win2k8: URL: https://vagrantcloud.com/rapid7/metasploitable3-win2k8
The box you're attempting to add doesn't support the provider
you requested. Please find an alternate box or use an alternate
provider. Double-check your requested provider to verify you didn't
simply misspell it.
If you're adding a box from HashiCorp's Vagrant Cloud, make sure the box is
released.
Name: rapid7/metasploitable3-win2k8
Address: https://vagrantcloud.com/rapid7/metasploitable3-win2k8
Requested provider: [:libvirt]
But running it through VirtualBox seems to works:
$ vagrant up --provider=virtualbox win2k8
Bringing machine 'win2k8' up with 'virtualbox' provider...
==> win2k8: Box 'rapid7/metasploitable3-win2k8' could not be found. Attempting to find and install...
win2k8: Box Provider: virtualbox
win2k8: Box Version: >= 0
==> win2k8: Loading metadata for box 'rapid7/metasploitable3-win2k8'
win2k8: URL: https://vagrantcloud.com/rapid7/metasploitable3-win2k8
==> win2k8: Adding box 'rapid7/metasploitable3-win2k8' (v0.1.0-weekly) for provider: virtualbox
win2k8: Downloading: https://vagrantcloud.com/rapid7/boxes/metasploitable3-win2k8/versions/0.1.0-weekly/providers/virtualbox.box
Progress: ...
The text was updated successfully, but these errors were encountered:
A libvirt build is not currently published to vagrant cloud, only vmware and virtualbox are published by the automation. The Vagrantfile support is there for users who build the VM from scratch on a libvirt environment at this time.
Agreed, just wasted some time trying to get this stuff to run. The default Vagrantfile should really be updated because, well, by default it's completely broken.
Issue Description
Right now Vagrant file configures
win2k8
box to run usinglibvirt
provider but as I can see in Vagrant Cloud there is no such provider available:Host System
Command Output
So one that try to get this box up get the error:
But running it through VirtualBox seems to works:
The text was updated successfully, but these errors were encountered: