Bullying error: memory could not be written

Question

When trying to execute the "vagrant up" command, the following error appears:

--------------------------- VBoxHeadless.exe - Application Error --------------------------- The instruction at 0x00007FFDEFEACD38 referenced memory at 0x0000000000003CB0. The memory could not be read. Click on OK to terminate the program --------------------------- OK --------------------------- 

Here is the console output log:

 vagrant up Bringing machine 'absolute-mysql' up with 'virtualbox' provider... Bringing machine 'absolute' up with 'virtualbox' provider... ==> absolute-mysql: Checking if box 'ubuntu/trusty64' is up to date... ==> absolute-mysql: A newer version of the box 'ubuntu/trusty64' is available! You currently ==> absolute-mysql: have version '20171019.0.0'. The latest is version '20171205.0.1'. Run ==> absolute-mysql: `vagrant box update` to update. ==> absolute-mysql: Clearing any previously set forwarded ports... ==> absolute-mysql: Clearing any previously set network interfaces... ==> absolute-mysql: Preparing network interfaces based on configuration... absolute-mysql: Adapter 1: nat absolute-mysql: Adapter 2: hostonly ==> absolute-mysql: Forwarding ports... absolute-mysql: 3306 (guest) => 3306 (host) (adapter 1) absolute-mysql: 22 (guest) => 8022 (host) (adapter 1) absolute-mysql: 22 (guest) => 2222 (host) (adapter 1) ==> absolute-mysql: Running 'pre-boot' VM customizations... ==> absolute-mysql: 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", "de3601aa-69df-49cb-abdf-698a1bbb91c7", "--type", "headless"] Stderr: VBoxManage.exe: error: The VM session was aborted VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component SessionMachine, interface ISession 

Please let me know if there is any additional information that I must provide. I am running a 64-bit version of a roaming and virtual window on Windows 10.

Answer 1

I have the same problem and hopefully a bug will be fixed soon.

In the meantime, I managed to start the installation process by adding the .iso image on the VirtualBox IDE repository settings page, and not in the "mount" dialog box that caused the error.

Open the parameters of your virtual machine in the VirtualBox user interface, go to "Storage", click on the "blank" entry in the list of IDE controllers and select the drive icon to the right of the screen. Finally, select “Select Virtual Optical Disk File” and select your .iso selection. Then start the virtual machine and it should boot just fine.