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
Upgraded to Vagrant v2.2.2 and receive this warning
==> default: Vagrant has detected a configuration issue which exposes a
==> default: vulnerability with the installed version of VirtualBox. The
==> default: current guest is configured to use an E1000 NIC type for a
==> default: network adapter which is vulnerable in this version of VirtualBox.
==> default: Ensure the guest is trusted to use this configuration or update
==> default: the NIC type using one of the methods below:
==> default:
==> default: https://www.vagrantup.com/docs/virtualbox/configuration.html#default-nic-type
==> default: https://www.vagrantup.com/docs/virtualbox/networking.html#virtualbox-nic-type
The text was updated successfully, but these errors were encountered:
config.vm.provider "virtualbox" do |v|v.default_nic_type = "82543GC"end
Does not fix the problem VM networking problem and vagrant still complains
config.vm.network :forwarded_port, guest: 5985, host: 5985, id: "winrm", auto_correct: true, nic_type: "82543GC"
config.vm.network :forwarded_port, guest: 3389, host: 3389, id: "rdp", auto_correct: true, nic_type: "82543GC"
# Port forward SSH (ssh is forwarded by default in most versions of Vagrant,
# but be sure). This is not necessary if you are not using SSH, but it doesn't
# hurt anything to have it
config.vm.network :forwarded_port, guest: 22, host: 2222, id: "ssh", auto_correct: true, nic_type: "82543GC"
Doesn't fix the VM networking problem either and vagrant still complains
basictheprogram
added a commit
to basictheprogram/chocolatey-test-environment
that referenced
this issue
Nov 29, 2018
Upgraded to Vagrant v2.2.2 and receive this warning
The text was updated successfully, but these errors were encountered: