Vagrant (1.9.4) and VirtualBox (5.1.22): E_FAIL (0x80004005) and VBoxHardening ExitCode=0xc0000005

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Vagrant (1.9.4) and VirtualBox (5.1.22): E_FAIL (0x80004005) and VBoxHardening ExitCode=0xc0000005

Colton Glasgow
Hello all, 

I am currently experiencing an issue with either Vagrant or VirtualBox and was curious if you could assist me in solving this problem. I am running VirtualBox 5.1.22 (latest) and vagrant 1.9.4 (latest) on Windows 10 x64. I am attempting to quickly deploy a preconfigured Vagrant box with a batch script (to easily share between my network), however I keep receiving an error. 

Batch file I am using to automate vagrant (setup.bat). Located inside folder with mybox.box (preconfigured Vagrant box):
vagrant destroy --force
vagrant box remove mybox
--force
vagrant box add mybox mybox
.box --force
vagrant up
echo
"finished!"
pause

The Vagrantfile used to configure mybox.box is attached to this post along with a screenshot of VirtualBox's fail dialog and the full VBoxHardening.log file.

After running this script, I am given this Vagrant output:
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'dl-elk' (v0) for provider:
    box
: Unpacking necessary files from: file://C:/mybox.box
    box
: Progress: 100% (Rate: 704M/s, Estimated time remaining: --:--:--)
==> box: Successfully added box 'mybox' (v0) for 'virtualbox'!
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'mybox'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: mybox
==> default: Using hostname "mybox" as node name for Chef...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
   
default: Adapter 1: nat
   
default: Adapter 2: bridged
==> default: Forwarding ports...
   
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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", "c0d0b043-2bf4-4574-84b9-37507a0b14b9", "--type", "headless"]
Stderr: VBoxManage.exe: error: The virtual machine 'dl-elk' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\...\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine


At this point, the box has been added to VirtualBox’s UI, however it will not start from there either. When attempting to run the new VM from within VirtualBox’s UI, I get the error E_FAIL (0x80004005) VirtualBox mentions there is a log file with information inside. I attached that file as well in hopes you could help me decipher it. I found the error ExitCode=0xc0000005 in VBoxHardening.log after reading through this forum post (https://forums.virtualbox.org/viewtopic.php?f=25&t=82106). 

The forum post states:
     ”Error Symptom 2: Error code 0xC0000005
     Error 0xC0000005 is what's known as an general protection fault or memory access error: the application tried to access an invalid memory address or jump to code which doesn't exist. Hence this is most likely a consequence of RULE2: a bad 
     DLL got unloaded, but some other DLL is still trying to use it. You can often narrow the cause if you look at which DLL faulted. Quite often you find that the bad memory access came from a graphics related DLL, which implies that the 
     graphics provider omitted to sign one of their DLLs. You should check for updates for your graphics card drivers.
     1 If you find that the VM will not start in normal mode, but will start when run in headless mode, then that makes it pretty much certain that your problem is the graphics drivers.”

I updated the graphics driver with no luck. They mention: ”You can often narrow the cause if you look at which DLL faulted.” I do not know how I would go about narrowing down the problem further from this point but it appears to be a DLL issue. Any information or suggestions would be greatly appreciated. 

Thank you in advance,

colton

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/1ea039a1-b341-4c0b-9786-3f737b5cea8b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Vagrantfile (967 bytes) Download Attachment
VBoxHardening.log (17K) Download Attachment
VirtualBox E-FAIL.PNG (24K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Vagrant (1.9.4) and VirtualBox (5.1.22): E_FAIL (0x80004005) and VBoxHardening ExitCode=0xc0000005

Alvaro Miranda Aguilera
Hello

The easiest way to troubleshoot will be comment all out and leave the bare minimum and test if the box works at all.

From there, start uncommenting settings one by one and do a vagrant reload to test all is fine.

I di a test and seems the issue is on

VM goes from template to mybox, and then it try to move it to mybox/mybox and fails



try a different name of group

Alvaro

On Thu, May 11, 2017 at 1:54 AM, Colton Glasgow <[hidden email]> wrote:
Hello all, 

I am currently experiencing an issue with either Vagrant or VirtualBox and was curious if you could assist me in solving this problem. I am running VirtualBox 5.1.22 (latest) and vagrant 1.9.4 (latest) on Windows 10 x64. I am attempting to quickly deploy a preconfigured Vagrant box with a batch script (to easily share between my network), however I keep receiving an error. 

Batch file I am using to automate vagrant (setup.bat). Located inside folder with mybox.box (preconfigured Vagrant box):
vagrant destroy --force
vagrant box remove mybox
--force
vagrant box add mybox mybox
.box --force
vagrant up
echo
"finished!"
pause

The Vagrantfile used to configure mybox.box is attached to this post along with a screenshot of VirtualBox's fail dialog and the full VBoxHardening.log file.

After running this script, I am given this Vagrant output:
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'dl-elk' (v0) for provider:
    box
: Unpacking necessary files from: file://C:/mybox.box
    box
: Progress: 100% (Rate: 704M/s, Estimated time remaining: --:--:--)
==> box: Successfully added box 'mybox' (v0) for 'virtualbox'!
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'mybox'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: mybox
==> default: Using hostname "mybox" as node name for Chef...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
   
default: Adapter 1: nat
   
default: Adapter 2: bridged
==> default: Forwarding ports...
   
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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", "c0d0b043-2bf4-4574-84b9-37507a0b14b9", "--type", "headless"]
Stderr: VBoxManage.exe: error: The virtual machine 'dl-elk' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\...\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine


At this point, the box has been added to VirtualBox’s UI, however it will not start from there either. When attempting to run the new VM from within VirtualBox’s UI, I get the error E_FAIL (0x80004005) VirtualBox mentions there is a log file with information inside. I attached that file as well in hopes you could help me decipher it. I found the error ExitCode=0xc0000005 in VBoxHardening.log after reading through this forum post (https://forums.virtualbox.org/viewtopic.php?f=25&t=82106). 

The forum post states:
     ”Error Symptom 2: Error code 0xC0000005
     Error 0xC0000005 is what's known as an general protection fault or memory access error: the application tried to access an invalid memory address or jump to code which doesn't exist. Hence this is most likely a consequence of RULE2: a bad 
     DLL got unloaded, but some other DLL is still trying to use it. You can often narrow the cause if you look at which DLL faulted. Quite often you find that the bad memory access came from a graphics related DLL, which implies that the 
     graphics provider omitted to sign one of their DLLs. You should check for updates for your graphics card drivers.
     1 If you find that the VM will not start in normal mode, but will start when run in headless mode, then that makes it pretty much certain that your problem is the graphics drivers.”

I updated the graphics driver with no luck. They mention: ”You can often narrow the cause if you look at which DLL faulted.” I do not know how I would go about narrowing down the problem further from this point but it appears to be a DLL issue. Any information or suggestions would be greatly appreciated. 

Thank you in advance,

colton

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/1ea039a1-b341-4c0b-9786-3f737b5cea8b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ey6Os5VUQv%3DWyKFG%3DuFBFWAgvNcBifKxMDaaEWWp0UAmg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Vagrant (1.9.4) and VirtualBox (5.1.22): E_FAIL (0x80004005) and VBoxHardening ExitCode=0xc0000005

Colton Glasgow
Alvaro, 

Thank you for the quick reply. I generated a new vagrantfile for mybox.box. It gets to the same point, "==> default: Booting VM..." and then gives me the E_FAIL (0x80004005) error. The interesting thing is that mybox.box works on my other test computer with the same version of VirtualBox (5.1.18) and Vagrant (1.9.4).

Vagrant File: 
Vagrant.configure("2") do |config|

  config.vm.box = "dl-elk"

end

Output:
C:\>cd C:\mybox\

C:\mybox>vagrant destroy --force
==> default: Destroying VM and associated drives...

C:\mybox>vagrant box remove mybox --force
Removing box 'mybox' (v0) with provider 'virtualbox'...

C:\mybox>vagrant box add mybox mybox.box --force
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'mybox' (v0) for provider:
    box: Unpacking necessary files from: file://C:/mybox/mybox.box
    box: Progress: 100% (Rate: 176M/s, Estimated time remaining: --:--:--)
==> box: Successfully added box 'mybox' (v0) for 'virtualbox'!

C:\mybox>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'mybox'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: mybox_default_1494533801678_82699
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> 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", "a620331e-b05f-4720-a935-6cb25f4c9125", "--type", "headless"]

Stderr: VBoxManage.exe: error: The virtual machine 'mybox_default_1494533801678_82699' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\Users\user\VirtualBox VMs\mybox_default_1494533801678_82699\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

Thanks, 
Colton 

On Wednesday, May 10, 2017 at 11:02:06 PM UTC-7, Alvaro Miranda Aguilera wrote:
Hello

The easiest way to troubleshoot will be comment all out and leave the bare minimum and test if the box works at all.

From there, start uncommenting settings one by one and do a vagrant reload to test all is fine.

I di a test and seems the issue is on

VM goes from template to mybox, and then it try to move it to mybox/mybox and fails



try a different name of group

Alvaro

On Thu, May 11, 2017 at 1:54 AM, Colton Glasgow <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="Q4Oy7UpVCQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">xxcolton....@...> wrote:
Hello all, 

I am currently experiencing an issue with either Vagrant or VirtualBox and was curious if you could assist me in solving this problem. I am running VirtualBox 5.1.22 (latest) and vagrant 1.9.4 (latest) on Windows 10 x64. I am attempting to quickly deploy a preconfigured Vagrant box with a batch script (to easily share between my network), however I keep receiving an error. 

Batch file I am using to automate vagrant (setup.bat). Located inside folder with mybox.box (preconfigured Vagrant box):
vagrant destroy --force
vagrant box remove mybox
--force
vagrant box add mybox mybox
.box --force
vagrant up
echo
"finished!"
pause

The Vagrantfile used to configure mybox.box is attached to this post along with a screenshot of VirtualBox's fail dialog and the full VBoxHardening.log file.

After running this script, I am given this Vagrant output:
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'dl-elk' (v0) for provider:
    box
: Unpacking necessary files from: file://C:/mybox.box
    box
: Progress: 100% (Rate: 704M/s, Estimated time remaining: --:--:--)
==> box: Successfully added box 'mybox' (v0) for 'virtualbox'!
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'mybox'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: mybox
==> default: Using hostname "mybox" as node name for Chef...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
   
default: Adapter 1: nat
   
default: Adapter 2: bridged
==> default: Forwarding ports...
   
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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", "c0d0b043-2bf4-4574-84b9-37507a0b14b9", "--type", "headless"]
Stderr: VBoxManage.exe: error: The virtual machine 'dl-elk' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\...\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine


At this point, the box has been added to VirtualBox’s UI, however it will not start from there either. When attempting to run the new VM from within VirtualBox’s UI, I get the error E_FAIL (0x80004005) VirtualBox mentions there is a log file with information inside. I attached that file as well in hopes you could help me decipher it. I found the error ExitCode=0xc0000005 in VBoxHardening.log after reading through this forum post (<a href="https://forums.virtualbox.org/viewtopic.php?f=25&amp;t=82106" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fforums.virtualbox.org%2Fviewtopic.php%3Ff%3D25%26t%3D82106\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF3M8JHG5mYEM3iiuyVVl3x-yAHmQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fforums.virtualbox.org%2Fviewtopic.php%3Ff%3D25%26t%3D82106\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF3M8JHG5mYEM3iiuyVVl3x-yAHmQ&#39;;return true;">https://forums.virtualbox.org/viewtopic.php?f=25&t=82106). 

The forum post states:
     ”Error Symptom 2: Error code 0xC0000005
     Error 0xC0000005 is what's known as an general protection fault or memory access error: the application tried to access an invalid memory address or jump to code which doesn't exist. Hence this is most likely a consequence of RULE2: a bad 
     DLL got unloaded, but some other DLL is still trying to use it. You can often narrow the cause if you look at which DLL faulted. Quite often you find that the bad memory access came from a graphics related DLL, which implies that the 
     graphics provider omitted to sign one of their DLLs. You should check for updates for your graphics card drivers.
     1 If you find that the VM will not start in normal mode, but will start when run in headless mode, then that makes it pretty much certain that your problem is the graphics drivers.”

I updated the graphics driver with no luck. They mention: ”You can often narrow the cause if you look at which DLL faulted.” I do not know how I would go about narrowing down the problem further from this point but it appears to be a DLL issue. Any information or suggestions would be greatly appreciated. 

Thank you in advance,

colton

--
This mailing list is governed under the HashiCorp Community Guidelines - <a href="https://www.hashicorp.com/community-guidelines.html" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;">https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: <a href="https://github.com/mitchellh/vagrant/issues" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;">https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="Q4Oy7UpVCQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">vagrant-up+...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/vagrant-up/1ea039a1-b341-4c0b-9786-3f737b5cea8b%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/1ea039a1-b341-4c0b-9786-3f737b5cea8b%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/1ea039a1-b341-4c0b-9786-3f737b5cea8b%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/vagrant-up/1ea039a1-b341-4c0b-9786-3f737b5cea8b%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.



--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/73f9622a-1cd8-44cc-93a5-f4ddcefd25ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Vagrant (1.9.4) and VirtualBox (5.1.22): E_FAIL (0x80004005) and VBoxHardening ExitCode=0xc0000005

Colton Glasgow
In reply to this post by Alvaro Miranda Aguilera
Alvaro, 

Thank you for the quick reply. I generated a new vagrantfile for mybox.box. It gets to the same point, "==> default: Booting VM..." and then gives me the E_FAIL (0x80004005) error. The interesting thing is that mybox.box works on my other test computer with the same version of VirtualBox (5.1.18) and Vagrant (1.9.4).

Vagrant File: 
Vagrant.configure("2") do |config|

  config.vm.box = "mybox"

end

Output:
C:\>cd C:\mybox\

C:\mybox>vagrant destroy --force
==> default: Destroying VM and associated drives...

C:\mybox>vagrant box remove mybox --force
Removing box 'mybox' (v0) with provider 'virtualbox'...

C:\mybox>vagrant box add mybox mybox.box --force
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'mybox' (v0) for provider:
    box: Unpacking necessary files from: file://C:/mybox/mybox.box
    box: Progress: 100% (Rate: 176M/s, Estimated time remaining: --:--:--)
==> box: Successfully added box 'mybox' (v0) for 'virtualbox'!

C:\mybox>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'mybox'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: mybox_default_1494533801678_82699
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> 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", "a620331e-b05f-4720-a935-6cb25f4c9125", "--type", "headless"]

Stderr: VBoxManage.exe: error: The virtual machine 'mybox_default_1494533801678_82699' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\Users\user\VirtualBox VMs\mybox_default_1494533801678_82699\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

Thanks, 
Colton 

On Wednesday, May 10, 2017 at 11:02:06 PM UTC-7, Alvaro Miranda Aguilera wrote:
Hello

The easiest way to troubleshoot will be comment all out and leave the bare minimum and test if the box works at all.

From there, start uncommenting settings one by one and do a vagrant reload to test all is fine.

I di a test and seems the issue is on

VM goes from template to mybox, and then it try to move it to mybox/mybox and fails



try a different name of group

Alvaro

On Thu, May 11, 2017 at 1:54 AM, Colton Glasgow <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="Q4Oy7UpVCQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">xxcolton....@...> wrote:
Hello all, 

I am currently experiencing an issue with either Vagrant or VirtualBox and was curious if you could assist me in solving this problem. I am running VirtualBox 5.1.22 (latest) and vagrant 1.9.4 (latest) on Windows 10 x64. I am attempting to quickly deploy a preconfigured Vagrant box with a batch script (to easily share between my network), however I keep receiving an error. 

Batch file I am using to automate vagrant (setup.bat). Located inside folder with mybox.box (preconfigured Vagrant box):
vagrant destroy --force
vagrant box remove mybox
--force
vagrant box add mybox mybox
.box --force
vagrant up
echo
"finished!"
pause

The Vagrantfile used to configure mybox.box is attached to this post along with a screenshot of VirtualBox's fail dialog and the full VBoxHardening.log file.

After running this script, I am given this Vagrant output:
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'dl-elk' (v0) for provider:
    box
: Unpacking necessary files from: file://C:/mybox.box
    box
: Progress: 100% (Rate: 704M/s, Estimated time remaining: --:--:--)
==> box: Successfully added box 'mybox' (v0) for 'virtualbox'!
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'mybox'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: mybox
==> default: Using hostname "mybox" as node name for Chef...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
   
default: Adapter 1: nat
   
default: Adapter 2: bridged
==> default: Forwarding ports...
   
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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", "c0d0b043-2bf4-4574-84b9-37507a0b14b9", "--type", "headless"]
Stderr: VBoxManage.exe: error: The virtual machine 'dl-elk' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\...\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine


At this point, the box has been added to VirtualBox’s UI, however it will not start from there either. When attempting to run the new VM from within VirtualBox’s UI, I get the error E_FAIL (0x80004005) VirtualBox mentions there is a log file with information inside. I attached that file as well in hopes you could help me decipher it. I found the error ExitCode=0xc0000005 in VBoxHardening.log after reading through this forum post (<a href="https://forums.virtualbox.org/viewtopic.php?f=25&amp;t=82106" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fforums.virtualbox.org%2Fviewtopic.php%3Ff%3D25%26t%3D82106\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF3M8JHG5mYEM3iiuyVVl3x-yAHmQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fforums.virtualbox.org%2Fviewtopic.php%3Ff%3D25%26t%3D82106\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF3M8JHG5mYEM3iiuyVVl3x-yAHmQ&#39;;return true;">https://forums.virtualbox.org/viewtopic.php?f=25&t=82106). 

The forum post states:
     ”Error Symptom 2: Error code 0xC0000005
     Error 0xC0000005 is what's known as an general protection fault or memory access error: the application tried to access an invalid memory address or jump to code which doesn't exist. Hence this is most likely a consequence of RULE2: a bad 
     DLL got unloaded, but some other DLL is still trying to use it. You can often narrow the cause if you look at which DLL faulted. Quite often you find that the bad memory access came from a graphics related DLL, which implies that the 
     graphics provider omitted to sign one of their DLLs. You should check for updates for your graphics card drivers.
     1 If you find that the VM will not start in normal mode, but will start when run in headless mode, then that makes it pretty much certain that your problem is the graphics drivers.”

I updated the graphics driver with no luck. They mention: ”You can often narrow the cause if you look at which DLL faulted.” I do not know how I would go about narrowing down the problem further from this point but it appears to be a DLL issue. Any information or suggestions would be greatly appreciated. 

Thank you in advance,

colton

--
This mailing list is governed under the HashiCorp Community Guidelines - <a href="https://www.hashicorp.com/community-guidelines.html" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;">https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: <a href="https://github.com/mitchellh/vagrant/issues" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;">https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="Q4Oy7UpVCQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">vagrant-up+...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/vagrant-up/1ea039a1-b341-4c0b-9786-3f737b5cea8b%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/1ea039a1-b341-4c0b-9786-3f737b5cea8b%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/1ea039a1-b341-4c0b-9786-3f737b5cea8b%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/vagrant-up/1ea039a1-b341-4c0b-9786-3f737b5cea8b%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.



--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/4a8b3835-5543-46d7-b9bf-bf33b60ec8a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Vagrant (1.9.4) and VirtualBox (5.1.22): E_FAIL (0x80004005) and VBoxHardening ExitCode=0xc0000005

Colton Glasgow
Solved the problem. Uninstalled Cylance Protect thanks to VirtualBox forum. Thanks for the help! 

Colton 

On Thursday, May 11, 2017 at 1:38:36 PM UTC-7, Colton Glasgow wrote:
Alvaro, 

Thank you for the quick reply. I generated a new vagrantfile for mybox.box. It gets to the same point, "==> default: Booting VM..." and then gives me the E_FAIL (0x80004005) error. The interesting thing is that mybox.box works on my other test computer with the same version of VirtualBox (5.1.18) and Vagrant (1.9.4).

Vagrant File: 
Vagrant.configure("2") do |config|

  config.vm.box = "mybox"

end

Output:
C:\>cd C:\mybox\

C:\mybox>vagrant destroy --force
==> default: Destroying VM and associated drives...

C:\mybox>vagrant box remove mybox --force
Removing box 'mybox' (v0) with provider 'virtualbox'...

C:\mybox>vagrant box add mybox mybox.box --force
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'mybox' (v0) for provider:
    box: Unpacking necessary files from: file://C:/mybox/mybox.box
    box: Progress: 100% (Rate: 176M/s, Estimated time remaining: --:--:--)
==> box: Successfully added box 'mybox' (v0) for 'virtualbox'!

C:\mybox>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'mybox'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: mybox_default_1494533801678_82699
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> 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", "a620331e-b05f-4720-a935-6cb25f4c9125", "--type", "headless"]

Stderr: VBoxManage.exe: error: The virtual machine 'mybox_default_1494533801678_82699' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\Users\user\VirtualBox VMs\mybox_default_1494533801678_82699\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

Thanks, 
Colton 

On Wednesday, May 10, 2017 at 11:02:06 PM UTC-7, Alvaro Miranda Aguilera wrote:
Hello

The easiest way to troubleshoot will be comment all out and leave the bare minimum and test if the box works at all.

From there, start uncommenting settings one by one and do a vagrant reload to test all is fine.

I di a test and seems the issue is on

VM goes from template to mybox, and then it try to move it to mybox/mybox and fails



try a different name of group

Alvaro

On Thu, May 11, 2017 at 1:54 AM, Colton Glasgow <[hidden email]> wrote:
Hello all, 

I am currently experiencing an issue with either Vagrant or VirtualBox and was curious if you could assist me in solving this problem. I am running VirtualBox 5.1.22 (latest) and vagrant 1.9.4 (latest) on Windows 10 x64. I am attempting to quickly deploy a preconfigured Vagrant box with a batch script (to easily share between my network), however I keep receiving an error. 

Batch file I am using to automate vagrant (setup.bat). Located inside folder with mybox.box (preconfigured Vagrant box):
vagrant destroy --force
vagrant box remove mybox
--force
vagrant box add mybox mybox
.box --force
vagrant up
echo
"finished!"
pause

The Vagrantfile used to configure mybox.box is attached to this post along with a screenshot of VirtualBox's fail dialog and the full VBoxHardening.log file.

After running this script, I am given this Vagrant output:
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'dl-elk' (v0) for provider:
    box
: Unpacking necessary files from: file://C:/mybox.box
    box
: Progress: 100% (Rate: 704M/s, Estimated time remaining: --:--:--)
==> box: Successfully added box 'mybox' (v0) for 'virtualbox'!
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'mybox'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: mybox
==> default: Using hostname "mybox" as node name for Chef...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
   
default: Adapter 1: nat
   
default: Adapter 2: bridged
==> default: Forwarding ports...
   
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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", "c0d0b043-2bf4-4574-84b9-37507a0b14b9", "--type", "headless"]
Stderr: VBoxManage.exe: error: The virtual machine 'dl-elk' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\...\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine


At this point, the box has been added to VirtualBox’s UI, however it will not start from there either. When attempting to run the new VM from within VirtualBox’s UI, I get the error E_FAIL (0x80004005) VirtualBox mentions there is a log file with information inside. I attached that file as well in hopes you could help me decipher it. I found the error ExitCode=0xc0000005 in VBoxHardening.log after reading through this forum post (<a href="https://forums.virtualbox.org/viewtopic.php?f=25&amp;t=82106" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fforums.virtualbox.org%2Fviewtopic.php%3Ff%3D25%26t%3D82106\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF3M8JHG5mYEM3iiuyVVl3x-yAHmQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fforums.virtualbox.org%2Fviewtopic.php%3Ff%3D25%26t%3D82106\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF3M8JHG5mYEM3iiuyVVl3x-yAHmQ&#39;;return true;">https://forums.virtualbox.org/viewtopic.php?f=25&t=82106). 

The forum post states:
     ”Error Symptom 2: Error code 0xC0000005
     Error 0xC0000005 is what's known as an general protection fault or memory access error: the application tried to access an invalid memory address or jump to code which doesn't exist. Hence this is most likely a consequence of RULE2: a bad 
     DLL got unloaded, but some other DLL is still trying to use it. You can often narrow the cause if you look at which DLL faulted. Quite often you find that the bad memory access came from a graphics related DLL, which implies that the 
     graphics provider omitted to sign one of their DLLs. You should check for updates for your graphics card drivers.
     1 If you find that the VM will not start in normal mode, but will start when run in headless mode, then that makes it pretty much certain that your problem is the graphics drivers.”

I updated the graphics driver with no luck. They mention: ”You can often narrow the cause if you look at which DLL faulted.” I do not know how I would go about narrowing down the problem further from this point but it appears to be a DLL issue. Any information or suggestions would be greatly appreciated. 

Thank you in advance,

colton

--
This mailing list is governed under the HashiCorp Community Guidelines - <a href="https://www.hashicorp.com/community-guidelines.html" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;">https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: <a href="https://github.com/mitchellh/vagrant/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;">https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/vagrant-up/1ea039a1-b341-4c0b-9786-3f737b5cea8b%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/1ea039a1-b341-4c0b-9786-3f737b5cea8b%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/1ea039a1-b341-4c0b-9786-3f737b5cea8b%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/vagrant-up/1ea039a1-b341-4c0b-9786-3f737b5cea8b%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.



--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/65bd3581-3ecf-4c2a-b3f5-e9e9750dd7b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.