Lab1: error while executing `VBoxManage`
stefanrutka
Posts: 2
Hi, this is Stefan from Germany testing Lab1 ;-)
Unfortunately Vagrant won't start running, after "vagrant up" I get the following error:
[email protected]:~$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 3000 (guest) => 3000 (host) (adapter 1)
default: 3333 (guest) => 3333 (host) (adapter 1)
default: 8080 (guest) => 8080 (host) (adapter 1)
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", "7c41ded3-fb59-4be3-b4e4-d856aad3f7b8", "--type", "headless"]
Stderr: VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole**
I am using: Ubuntu 18.04.1 LTS with VirtualBox 5.2.18 for Ubuntu 18.04 / Debian 10 AMD64
Any help would be appreciated, thanks in advance!
Stefan
Comments
Hi @stefanrutka, is it possible that you were trying to run Ubuntu inside another OS or so? Say, Ubuntu 18.04.1 LTS from within Windows?
It's either this, or a BIOS setting (for allowing virtualization)
https://askubuntu.com/questions/779277/when-using-vagrant-stderr-vboxmanage-error-vt-x-is-not-available-verr-vmx-no
Kept on digging at Vagrant's support side, and it seems as if one can only run 32-bit VMs inside another VM... however, no Virtual Box inside a Virtual Box:
https://stackoverflow.com/questions/24620599/error-vt-x-not-available-for-vagrant-machine-inside-virtualbox
The course's labs were built and designed to run Virtual Box natively on 3 supported operating systems... but please let me know if this was the issue.
Hi Jonathan,
thank you for your reply. You were right: I tried to use vagrant inside a virtual box (Ubuntu) which was running on Win 10.
I now use vegrant 4 Windows and the Lab works fine.
Thanks for your help!
Stefan