VirtualBox application error - memory could not be written
Posted: 9. Nov 2015, 19:20
I'm trying to spin up a virtual box machine (ver 5.0.8 ) using vagrant set up.Whenever vagrant is trying to spin up virtualbox machine , the VirtualBox runs into an application error of referenced memory , stating memory could not be overwritten.Post this vagrant goes into aborted state and exits out mentioning the below -
"==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'aborted' state. Please verify everything is configured
properly and try again.
If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.
The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue."
Attached snapshot of the error seen on VirtualBox .
Could you please help giving some pointers to what could be done to fix this ?
"==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'aborted' state. Please verify everything is configured
properly and try again.
If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.
The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue."
Attached snapshot of the error seen on VirtualBox .
Could you please help giving some pointers to what could be done to fix this ?