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
2024-02-20 11:20:19,112 - INFO - attack_range - [action] > build
Bringing machine 'ar-splunk-attack-range-key-pair-ar' up with 'virtualbox' provider...
Bringing machine 'ar-win-attack-range-key-pair-ar-0' up with 'virtualbox' provider...
==> ar-splunk-attack-range-key-pair-ar: Checking if box 'generic/ubuntu2004' version '4.3.12' is up to date...
==> ar-splunk-attack-range-key-pair-ar: Clearing any previously set forwarded ports...
==> ar-splunk-attack-range-key-pair-ar: Clearing any previously set network interfaces...
==> ar-splunk-attack-range-key-pair-ar: Preparing network interfaces based on configuration...
ar-splunk-attack-range-key-pair-ar: Adapter 1: nat
ar-splunk-attack-range-key-pair-ar: Adapter 2: hostonly
==> ar-splunk-attack-range-key-pair-ar: Forwarding ports...
ar-splunk-attack-range-key-pair-ar: 8000 (guest) => 8000 (host) (adapter 1)
ar-splunk-attack-range-key-pair-ar: 8089 (guest) => 8089 (host) (adapter 1)
ar-splunk-attack-range-key-pair-ar: 8080 (guest) => 8080 (host) (adapter 1)
ar-splunk-attack-range-key-pair-ar: 22 (guest) => 2222 (host) (adapter 1)
==> ar-splunk-attack-range-key-pair-ar: Running 'pre-boot' VM customizations...
==> ar-splunk-attack-range-key-pair-ar: Booting VM...
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Stderr: VBoxManage: error: The virtual machine 'ar-splunk' has terminated unexpectedly during startup because of signal 6
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine
Any idea ? I tried on 2 fresh , different ubuntu machines , resulting in the same issue ....
The text was updated successfully, but these errors were encountered:
Run this with Ubuntu Desktop edition with GUI.
Or install KDE if you are using Ubuntu Server edition without any GUI
Else you can edit the vagrant files vb.gui to false.
Hi ,
I'm following your guidelines step for step from https://attack-range.readthedocs.io/en/latest/Attack_Range_AWS.html#linux on a fresh Ubuntu 22.04.3 LTS machine.
When trying to perform python attack_range.py build on the machine I get :
2024-02-20 11:20:19,112 - INFO - attack_range - [action] > build
Bringing machine 'ar-splunk-attack-range-key-pair-ar' up with 'virtualbox' provider...
Bringing machine 'ar-win-attack-range-key-pair-ar-0' up with 'virtualbox' provider...
==> ar-splunk-attack-range-key-pair-ar: Checking if box 'generic/ubuntu2004' version '4.3.12' is up to date...
==> ar-splunk-attack-range-key-pair-ar: Clearing any previously set forwarded ports...
==> ar-splunk-attack-range-key-pair-ar: Clearing any previously set network interfaces...
==> ar-splunk-attack-range-key-pair-ar: Preparing network interfaces based on configuration...
ar-splunk-attack-range-key-pair-ar: Adapter 1: nat
ar-splunk-attack-range-key-pair-ar: Adapter 2: hostonly
==> ar-splunk-attack-range-key-pair-ar: Forwarding ports...
ar-splunk-attack-range-key-pair-ar: 8000 (guest) => 8000 (host) (adapter 1)
ar-splunk-attack-range-key-pair-ar: 8089 (guest) => 8089 (host) (adapter 1)
ar-splunk-attack-range-key-pair-ar: 8080 (guest) => 8080 (host) (adapter 1)
ar-splunk-attack-range-key-pair-ar: 22 (guest) => 2222 (host) (adapter 1)
==> ar-splunk-attack-range-key-pair-ar: Running 'pre-boot' VM customizations...
==> ar-splunk-attack-range-key-pair-ar: Booting VM...
There was an error while executing
VBoxManage
, a CLI used by Vagrantfor controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "2f457d3e-1e25-4514-95dc-ad903a3efe34", "--type", "gui"]
Stderr: VBoxManage: error: The virtual machine 'ar-splunk' has terminated unexpectedly during startup because of signal 6
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine
Any idea ? I tried on 2 fresh , different ubuntu machines , resulting in the same issue ....
The text was updated successfully, but these errors were encountered: