Vagrant: Please Assist to resolve this problem VIRTUAL BOX

[chisumo2016]

PS C:\my-project> vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'scotch/box'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'scotch/box' is up to date...
==> default: Setting the name of the VM: my-project_default_1543837245866_98665
==> 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
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "b2e0b6af-a8dd-48a7-956e-bf5f5b43d434", "--type", "headless"]

Stderr: VBoxManage.exe: error: The virtual machine 'my-project_default_1543837245866_98665' has terminated unexpectedly
during startup with exit code 1 (0x1). More details may be available in 'C:\Users\bundalla\VirtualBox VMs\my-project_de
fault_1543837245866_98665\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
PS C:\my-project>

[briancain]

Hi @chisumo2016 - Can you bring up a virtual machine outside of Vagrant using the VirtualBox gui? Also what does your log say:

More details may be available in 'C:\Users\bundalla\VirtualBox VMs\my-project_de
fault_1543837245866_98665\Logs\VBoxHardening.log'

[anishbangalore]

@briancain I am also facing a similar issue, here I am giving the message which I got with "Vagrant up" and my Vagrant and Virtualbox versions,

Message:
_==> homestead-7: Vagrant has detected a configuration issue which exposes a
==> homestead-7: vulnerability with the installed version of VirtualBox. The
==> homestead-7: current guest is configured to use an E1000 NIC type for a
==> homestead-7: network adapter which is vulnerable in this version of VirtualBox.
==> homestead-7: Ensure the guest is trusted to use this configuration or update
==> homestead-7: the NIC type using one of the methods below:
==> homestead-7:
==> homestead-7: https://www.vagrantup.com/docs/virtualbox/configuration.html#default-nic-type
==> homestead-7: https://www.vagrantup.com/docs/virtualbox/networking.html#virtualbox-nic-type_

Vagrant Version: 2.2.2
VirtualBox Version: Version 5.2.22 r126460 (Qt5.9.5)
Operating System: LinuxMint (Tara)
_DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS"_

[briancain]

Hi @anishbangalore - That is not an error, it is just a warning. If there was an error, it might be further along in your Vagrant log. If it's not the same error as the original issue here, please open a new issue. Thanks!

[anishbangalore]

@briancain Yes its a warning, not error, hope with next updates this warning will go off

Thanks

[wtorcaso]

I just upgraded Vagrant, and now I get the message described above. I get that it is just a warning. What I don't get is what I might do with parameter 'nic_type'. I've read both of the links in the message; I have no idea what my current nic_type value is, or what I could change it to (if anything).

Also, is the question just whether I trust the guest OS and the software applications that it runs? The answer is, Yes, I trust them. This is just my development VM before executing in the cloud.

So: I don't have any information on how to fix the vulnerability, and I don't know if I need to. It feels like I should not have upgraded -- ignorance is bliss.

[proseLA]

@wtorcaso i disagree that ignorance is bliss.

with regards to the NIC warning messages (which the OP has as well, but the OP has a more serious problem as well), it seems that there is a 0-day exploit with regards to virtualbox as documented here:

https://goo.gl/kDHXXN

vagrant has a small problem in that it is reporting that error when it should not be. if you are running Vagrant 2.2.2 and VirtualBox 5.2.22, you will see the warning and you can safely ignore it. you can view the author copping to his mistake here:

https://github.com/hashicorp/vagrant/issues/10481#issuecomment-445074331

best.

[wtorcaso]

Thanks for this information.

What I meant by "ignorance is bliss" is that it is frustrating to know about a vulnerability while having insufficient information to fix it.

Bill Torcaso | Web Developer/Analyst |Oxfam America

From: proseLA [e-mail]
Reply-To: hashicorp/vagrant [e-mail]
Date: Thursday, December 13, 2018 at 11:37 AM
To: hashicorp/vagrant [e-mail]
Cc: William Torcaso [e-mail], Mention [e-mail]
Subject: Re: [hashicorp/vagrant] Please Assist to resolve this problem VIRTUAL BOX (#10473)

@wtorcasohttps://github.com/wtorcaso i disagree that ignorance is bliss.

with regards to the NIC warning messages (which the OP has as well, but the OP has a more serious problem as well), it seems that there is a 0-day exploit with regards to virtualbox as documented here:

https://goo.gl/kDHXXN

vagrant has a small problem in that it is reporting that error when it should not be. if you are running Vagrant 2.2.2 and VirtualBox 5.2.22, you will see the warning and you can safely ignore it. you can view the author copping to his mistake here:

10481 (comment)https://github.com/hashicorp/vagrant/issues/10481#issuecomment-445074331

best.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/hashicorp/vagrant/issues/10473#issuecomment-447035416, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AXhBqXzqJm1kImfLjl_3GK2HtXkk1Przks5u4oJCgaJpZM4Y-al1.

This message (including any attachments) may contain confidential, proprietary, privileged and/or private information. The information is intended to be for the use of the individual or entity designated above. If you are not the intended recipient of this message, please notify the sender immediately, and delete the message and any attachments. Any disclosure, reproduction, distribution or other use of this message or any attachments by an individual or entity other than the intended recipient is prohibited. This message is for discussion purposes only and cannot be used to create a binding contract.

[briancain]

Hello @chisumo2016 - my best guess is your machine might not have VT-X enabled. When you bring up the VM, open the virtualbox gui. It might have more information. I'm going to close this since there hasn't been a reply in a while from the original poster of the issue. Thanks!

[getong]

I have the same problem, but 2.2.0 seems ok, and 2.2.2 does not work.

[karimfayed]

I have a similar problem but the error that I get is that the process has timed out, so I'd really appreciate any help here.
Thanks in advance.
New Text Document (2).txt

[anishbangalore]

Hi Friends,

For me this issue is resolved when I updated my Oracle Vm Virtualbox to newer version
"Version 6.0.0 r127566 (Qt5.9.5)"
Thanks

[hashibot[bot]]

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.