vagrant
[root@nckmvdsla19591 ~]# vagrant box centos
Usage: vagrant box <subcommand> [<args>]
Available subcommands:
add
list
outdated
prune
remove
repackage
update
For help on any individual subcommand run `vagrant box <subcommand> -h`
[root@nckmvdsla19591 ~]# vagrant status
No usable default provider could be found for your system.
Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.
The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.
If you believe you already have a provider available, make sure it
is properly installed and configured. You can see more details about
why a particular provider isn't working by forcing usage with
`vagrant up --provider=PROVIDER`, which should give you a more specific
error message for that particular provider.
[root@nckmvdsla19591 ~]# yum -y install VirtualBox-5.1
Loaded plugins: changelog, langpacks, verify
No package VirtualBox-5.1 available.
Error: Nothing to do
[root@nckmvdsla19591 ~]# cd /etc/yum.repos.d/
[root@nckmvdsla19591 yum.repos.d]# wget http://download.virtualbox.org/virtualbox/rpm/rhel/virtualbox.repo
--2018-07-13 00:45:13-- http://download.virtualbox.org/virtualbox/rpm/rhel/virtualbox.repo
Resolving download.virtualbox.org (download.virtualbox.org)... 23.60.166.109
Connecting to download.virtualbox.org (download.virtualbox.org)|23.60.166.109|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 259 [text/plain]
Saving to: ‘virtualbox.repo’
100%[=========================================================================================>] 259 --.-K/s in 0s
2018-07-13 00:45:14 (28.9 MB/s) - ‘virtualbox.repo’ saved [259/259]
[root@nckmvdsla19591 yum.repos.d]# yum -y install VirtualBox-5.1
Loaded plugins: changelog, langpacks, verify
virtualbox/7Server/x86_64/signature | 181 B 00:00:00
Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
Importing GPG key 0x98AB5139:
Userid : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
From : https://www.virtualbox.org/download/oracle_vbox.asc
virtualbox/7Server/x86_64/signature | 1.1 kB 00:00:01 !!!
virtualbox/7Server/x86_64/primary | 11 kB 00:00:00
virtualbox 55/55
Resolving Dependencies
--> Running transaction check
---> Package VirtualBox-5.1.x86_64 0:5.1.38_122592_el7-1 will be installed
--> Processing Dependency: libXt.so.6()(64bit) for package: VirtualBox-5.1-5.1.38_122592_el7-1.x86_64
--> Processing Dependency: libGL.so.1()(64bit) for package: VirtualBox-5.1-5.1.38_122592_el7-1.x86_64
--> Processing Dependency: libXinerama.so.1()(64bit) for package: VirtualBox-5.1-5.1.38_122592_el7-1.x86_64
--> Processing Dependency: libvpx.so.1()(64bit) for package: VirtualBox-5.1-5.1.38_122592_el7-1.x86_64
--> Processing Dependency: libXmu.so.6()(64bit) for package: VirtualBox-5.1-5.1.38_122592_el7-1.x86_64
--> Processing Dependency: libSDL-1.2.so.0()(64bit) for package: VirtualBox-5.1-5.1.38_122592_el7-1.x86_64
--> Processing Dependency: libXcursor.so.1()(64bit) for package: VirtualBox-5.1-5.1.38_122592_el7-1.x86_64
--> Running transaction check
---> Package SDL.x86_64 0:1.2.15-14.el7 will be installed
---> Package libXcursor.x86_64 0:1.1.14-8.el7 will be installed
--> Processing Dependency: libXfixes.so.3()(64bit) for package: libXcursor-1.1.14-8.el7.x86_64
---> Package libXinerama.x86_64 0:1.1.3-2.1.el7 will be installed
---> Package libXmu.x86_64 0:1.1.2-2.el7 will be installed
---> Package libXt.x86_64 0:1.1.5-3.el7 will be installed
---> Package libvpx.x86_64 0:1.3.0-5.el7_0 will be installed
---> Package mesa-libGL.x86_64 0:17.2.3-8.20171019.el7 will be installed
--> Processing Dependency: mesa-libglapi = 17.2.3-8.20171019.el7 for package: mesa-libGL-17.2.3-8.20171019.el7.x86_64
--> Processing Dependency: libXdamage.so.1()(64bit) for package: mesa-libGL-17.2.3-8.20171019.el7.x86_64
--> Processing Dependency: libXxf86vm.so.1()(64bit) for package: mesa-libGL-17.2.3-8.20171019.el7.x86_64
--> Processing Dependency: libglapi.so.0()(64bit) for package: mesa-libGL-17.2.3-8.20171019.el7.x86_64
--> Processing Dependency: libxshmfence.so.1()(64bit) for package: mesa-libGL-17.2.3-8.20171019.el7.x86_64
--> Running transaction check
---> Package libXdamage.x86_64 0:1.1.4-4.1.el7 will be installed
---> Package libXfixes.x86_64 0:5.0.3-1.el7 will be installed
---> Package libXxf86vm.x86_64 0:1.1.4-1.el7 will be installed
---> Package libxshmfence.x86_64 0:1.2-1.el7 will be installed
---> Package mesa-libglapi.x86_64 0:17.2.3-8.20171019.el7 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
===================================================================================================================================
Package Arch Version Repository Size
===================================================================================================================================
Installing:
VirtualBox-5.1 x86_64 5.1.38_122592_el7-1 virtualbox 76 M
Installing for dependencies:
SDL x86_64 1.2.15-14.el7 wdprt-base 204 k
libXcursor x86_64 1.1.14-8.el7 wdprt-base 30 k
libXdamage x86_64 1.1.4-4.1.el7 wdprt-base 20 k
libXfixes x86_64 5.0.3-1.el7 wdprt-base 18 k
libXinerama x86_64 1.1.3-2.1.el7 wdprt-base 14 k
libXmu x86_64 1.1.2-2.el7 wdprt-base 71 k
libXt x86_64 1.1.5-3.el7 wdprt-base 173 k
libXxf86vm x86_64 1.1.4-1.el7 wdprt-base 18 k
libvpx x86_64 1.3.0-5.el7_0 wdprt-base 498 k
libxshmfence x86_64 1.2-1.el7 wdprt-base 7.1 k
mesa-libGL x86_64 17.2.3-8.20171019.el7 wdprt-base 156 k
mesa-libglapi x86_64 17.2.3-8.20171019.el7 wdprt-base 43 k
Transaction Summary
===================================================================================================================================
Install 1 Package (+12 Dependent packages)
Total download size: 77 M
Installed size: 173 M
Downloading packages:
(1/13): libXdamage-1.1.4-4.1.el7.x86_64.rpm | 20 kB 00:00:00
(2/13): SDL-1.2.15-14.el7.x86_64.rpm | 204 kB 00:00:00
(3/13): libXinerama-1.1.3-2.1.el7.x86_64.rpm | 14 kB 00:00:00
(4/13): libXt-1.1.5-3.el7.x86_64.rpm | 173 kB 00:00:00
(5/13): libXmu-1.1.2-2.el7.x86_64.rpm | 71 kB 00:00:00
(6/13): libXxf86vm-1.1.4-1.el7.x86_64.rpm | 18 kB 00:00:00
(7/13): libXcursor-1.1.14-8.el7.x86_64.rpm | 30 kB 00:00:00
(8/13): libXfixes-5.0.3-1.el7.x86_64.rpm | 18 kB 00:00:00
(9/13): libxshmfence-1.2-1.el7.x86_64.rpm | 7.1 kB 00:00:00
(10/13): libvpx-1.3.0-5.el7_0.x86_64.rpm | 498 kB 00:00:00
(11/13): mesa-libGL-17.2.3-8.20171019.el7.x86_64.rpm | 156 kB 00:00:00
(12/13): mesa-libglapi-17.2.3-8.20171019.el7.x86_64.rpm | 43 kB 00:00:00
warning: /var/cache/yum/x86_64/7Server/virtualbox/packages/VirtualBox-5.1-5.1.38_122592_el7-1.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 98ab5139: NOKEY
Public key for VirtualBox-5.1-5.1.38_122592_el7-1.x86_64.rpm is not installed
(13/13): VirtualBox-5.1-5.1.38_122592_el7-1.x86_64.rpm | 76 MB 00:00:05
-----------------------------------------------------------------------------------------------------------------------------------
Total 14 MB/s | 77 MB 00:00:05
Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
Importing GPG key 0x98AB5139:
Userid : "Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>"
Fingerprint: 7b0f ab3a 13b9 0743 5925 d9c9 5442 2a4b 98ab 5139
From : https://www.virtualbox.org/download/oracle_vbox.asc
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : libXfixes-5.0.3-1.el7.x86_64 1/13
Installing : libXt-1.1.5-3.el7.x86_64 2/13
Installing : libXmu-1.1.2-2.el7.x86_64 3/13
Installing : libXdamage-1.1.4-4.1.el7.x86_64 4/13
Installing : libXcursor-1.1.14-8.el7.x86_64 5/13
Installing : libxshmfence-1.2-1.el7.x86_64 6/13
Installing : libvpx-1.3.0-5.el7_0.x86_64 7/13
Installing : SDL-1.2.15-14.el7.x86_64 8/13
Installing : libXxf86vm-1.1.4-1.el7.x86_64 9/13
Installing : libXinerama-1.1.3-2.1.el7.x86_64 10/13
Installing : mesa-libglapi-17.2.3-8.20171019.el7.x86_64 11/13
Installing : mesa-libGL-17.2.3-8.20171019.el7.x86_64 12/13
Installing : VirtualBox-5.1-5.1.38_122592_el7-1.x86_64 13/13
Creating group 'vboxusers'. VM users must be member of that group!
Verifying : mesa-libglapi-17.2.3-8.20171019.el7.x86_64 1/13
Verifying : libXdamage-1.1.4-4.1.el7.x86_64 2/13
Verifying : libXinerama-1.1.3-2.1.el7.x86_64 3/13
Verifying : libXcursor-1.1.14-8.el7.x86_64 4/13
Verifying : libXfixes-5.0.3-1.el7.x86_64 5/13
Verifying : libXxf86vm-1.1.4-1.el7.x86_64 6/13
Verifying : SDL-1.2.15-14.el7.x86_64 7/13
Verifying : libXmu-1.1.2-2.el7.x86_64 8/13
Verifying : mesa-libGL-17.2.3-8.20171019.el7.x86_64 9/13
Verifying : libXt-1.1.5-3.el7.x86_64 10/13
Verifying : libvpx-1.3.0-5.el7_0.x86_64 11/13
Verifying : VirtualBox-5.1-5.1.38_122592_el7-1.x86_64 12/13
Verifying : libxshmfence-1.2-1.el7.x86_64 13/13
Installed:
VirtualBox-5.1.x86_64 0:5.1.38_122592_el7-1
Dependency Installed:
SDL.x86_64 0:1.2.15-14.el7 libXcursor.x86_64 0:1.1.14-8.el7 libXdamage.x86_64 0:1.1.4-4.1.el7
libXfixes.x86_64 0:5.0.3-1.el7 libXinerama.x86_64 0:1.1.3-2.1.el7 libXmu.x86_64 0:1.1.2-2.el7
libXt.x86_64 0:1.1.5-3.el7 libXxf86vm.x86_64 0:1.1.4-1.el7 libvpx.x86_64 0:1.3.0-5.el7_0
libxshmfence.x86_64 0:1.2-1.el7 mesa-libGL.x86_64 0:17.2.3-8.20171019.el7 mesa-libglapi.x86_64 0:17.2.3-8.20171019.el7
Complete!
[root@nckmvdsla19591 yum.repos.d]# vagrant status
A Vagrant environment or target machine is required to run this
command. Run `vagrant init` to create a new Vagrant environment. Or,
get an ID of a target machine from `vagrant global-status` to run
this command on. A final option is to change to a directory with a
Vagrantfile and to try again.
[root@nckmvdsla19591 yum.repos.d]# vagrant init hashicorp/precise64
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
[root@nckmvdsla19591 yum.repos.d]# vagrant status
Current machine states:
default not created (virtualbox)
The environment has not yet been created. Run `vagrant up` to
create the environment. If a machine is not created, only the
default provider will be shown. So if a provider is not listed,
then the machine is not created for that environment.
[root@nckmvdsla19591 yum.repos.d]# vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'hashicorp/precise64' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Loading metadata for box 'hashicorp/precise64'
default: URL: https://vagrantcloud.com/hashicorp/precise64
==> default: Adding box 'hashicorp/precise64' (v1.1.0) for provider: virtualbox
default: Downloading: https://vagrantcloud.com/hashicorp/boxes/precise64/versions/1.1.0/providers/virtualbox.box
==> default: Successfully added box 'hashicorp/precise64' (v1.1.0) for 'virtualbox'!
==> default: Importing base box 'hashicorp/precise64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'hashicorp/precise64' is up to date...
==> default: Setting the name of the VM: yumreposd_default_1531457271868_88893
==> 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", "5c738d6d-7637-4d5e-b0ec-22d2577af3e2", "--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
[root@nckmvdsla19591 yum.repos.d]# vagrant status
Current machine states:
default poweroff (virtualbox)
The VM is powered off. To restart the VM, simply run `vagrant up`
[root@nckmvdsla19591 yum.repos.d]# vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'hashicorp/precise64' is up to date...
==> 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: 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", "5c738d6d-7637-4d5e-b0ec-22d2577af3e2", "--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
[root@nckmvdsla19591 yum.repos.d]# vagrant "startvm", "5c738d6d-7637-4d5e-b0ec-22d2577af3e2", "--type", "headless"
Usage: vagrant [options] <command> [<args>]
-v, --version Print the version and exit.
-h, --help Print this help.
Common commands:
box manages boxes: installation, removal, etc.
connect connect to a remotely shared Vagrant environment
destroy stops and deletes all traces of the vagrant machine
global-status outputs status Vagrant environments for this user
halt stops the vagrant machine
help shows the help for a subcommand
init initializes a new Vagrant environment by creating a Vagrantfile
login log in to HashiCorp's Vagrant Cloud
package packages a running vagrant environment into a box
plugin manages plugins: install, uninstall, update, etc.
port displays information about guest port mappings
powershell connects to machine via powershell remoting
provision provisions the vagrant machine
push deploys code in this environment to a configured destination
rdp connects to machine via RDP
reload restarts vagrant machine, loads new Vagrantfile configuration
resume resume a suspended vagrant machine
share share your Vagrant environment with anyone in the world
snapshot manages snapshots: saving, restoring, etc.
ssh connects to machine via SSH
ssh-config outputs OpenSSH valid configuration to connect to the machine
status outputs status of the vagrant machine
suspend suspends the machine
up starts and provisions the vagrant environment
validate validates the Vagrantfile
version prints current and latest Vagrant version
For help on any individual command run `vagrant COMMAND -h`
Additional subcommands are available, but are either more advanced
or not commonly used. To see all subcommands, run the command
`vagrant list-commands`.
[root@nckmvdsla19591 yum.repos.d]# vagrant init hashicorp/precise64
`Vagrantfile` already exists in this directory. Remove it before
running `vagrant init`.
[root@nckmvdsla19591 yum.repos.d]# ls
datastax.repo Vagrantfile wdprt-epel.repo wdprt-optional.repo yum-mirrors-extras.list
epel.repo virtualbox.repo wdprt-extras.repo yum-mirrors-base.list yum-mirrors-imod.list
epel-testing.repo wdprt-base.repo wdprt-imod.repo yum-mirrors-epel.list yum-mirrors-optional.list
[root@nckmvdsla19591 yum.repos.d]# cd
[root@nckmvdsla19591 ~]# cd
[root@nckmvdsla19591 ~]# vagrant init hashicorp/precise64
`Vagrantfile` already exists in this directory. Remove it before
running `vagrant init`.
[root@nckmvdsla19591 ~]# # vagrant init centos/7
[root@nckmvdsla19591 ~]# vagrant init centos/7
`Vagrantfile` already exists in this directory. Remove it before
running `vagrant init`.
[root@nckmvdsla19591 ~]# vagrant ssh
VM must be created before running this command. Run `vagrant up` first.
[root@nckmvdsla19591 ~]# vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'hashicorp/precise64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'hashicorp/precise64' is up to date...
==> default: Setting the name of the VM: root_default_1531457486976_96751
==> 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", "6997e08b-cde4-4b16-b592-638b1042eac5", "--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
[root@nckmvdsla19591 ~]# vagrant ssh
VM must be running to open SSH connection. Run `vagrant up`
to start the virtual machine.
[root@nckmvdsla19591 ~]# vagrant up hashicorp/precise6
The machine with the name 'hashicorp/precise6' was not found configured for
this Vagrant environment.
[root@nckmvdsla19591 ~]# vagrant ps
Usage: vagrant [options] <command> [<args>]
-v, --version Print the version and exit.
-h, --help Print this help.
Common commands:
box manages boxes: installation, removal, etc.
connect connect to a remotely shared Vagrant environment
destroy stops and deletes all traces of the vagrant machine
global-status outputs status Vagrant environments for this user
halt stops the vagrant machine
help shows the help for a subcommand
init initializes a new Vagrant environment by creating a Vagrantfile
login log in to HashiCorp's Vagrant Cloud
package packages a running vagrant environment into a box
plugin manages plugins: install, uninstall, update, etc.
port displays information about guest port mappings
powershell connects to machine via powershell remoting
provision provisions the vagrant machine
push deploys code in this environment to a configured destination
rdp connects to machine via RDP
reload restarts vagrant machine, loads new Vagrantfile configuration
resume resume a suspended vagrant machine
share share your Vagrant environment with anyone in the world
snapshot manages snapshots: saving, restoring, etc.
ssh connects to machine via SSH
ssh-config outputs OpenSSH valid configuration to connect to the machine
status outputs status of the vagrant machine
suspend suspends the machine
up starts and provisions the vagrant environment
validate validates the Vagrantfile
version prints current and latest Vagrant version
For help on any individual command run `vagrant COMMAND -h`
Additional subcommands are available, but are either more advanced
or not commonly used. To see all subcommands, run the command
`vagrant list-commands`.
[root@nckmvdsla19591 ~]# vagrant status
Current machine states:
default poweroff (virtualbox)
The VM is powered off. To restart the VM, simply run `vagrant up`
[root@nckmvdsla19591 ~]# vagrant up defalt
The machine with the name 'defalt' was not found configured for
this Vagrant environment.
[root@nckmvdsla19591 ~]# vagrant up default
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'hashicorp/precise64' is up to date...
==> 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: 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", "6997e08b-cde4-4b16-b592-638b1042eac5", "--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
[root@nckmvdsla19591 ~]# virtualbox
Qt FATAL: QXcbConnection: Could not connect to display
Aborted (core dumped)
[root@nckmvdsla19591 ~]# virtualbox hashicorp/precise64
Qt FATAL: QXcbConnection: Could not connect to display
Aborted (core dumped)
[root@nckmvdsla19591 ~]# vagrant box add centos-7.0-x86_64.box --name centos7
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'centos7' (v0) for provider:
box: Downloading: centos-7.0-x86_64.box
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
Couldn't open file /root/centos-7.0-x86_64.box
[root@nckmvdsla19591 ~]# vagrant init
`Vagrantfile` already exists in this directory. Remove it before
running `vagrant init`.
[root@nckmvdsla19591 ~]# vagrant init centos/7
`Vagrantfile` already exists in this directory. Remove it before
running `vagrant init`.
[root@nckmvdsla19591 ~]# vagrant up\
> ^C
[root@nckmvdsla19591 ~]# vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'hashicorp/precise64' is up to date...
==> 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: 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", "6997e08b-cde4-4b16-b592-638b1042eac5", "--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
[root@nckmvdsla19591 ~]# vagrant init bento/centos-7.2
`Vagrantfile` already exists in this directory. Remove it before
running `vagrant init`.
[root@nckmvdsla19591 ~]# vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'hashicorp/precise64' is up to date...
==> 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: 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", "6997e08b-cde4-4b16-b592-638b1042eac5", "--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
[root@nckmvdsla19591 ~]#
[root@nckmvdsla19591 ~]# vagrant box add hashicorp/precise64
==> box: Loading metadata for box 'hashicorp/precise64'
box: URL: https://vagrantcloud.com/hashicorp/precise64
This box can work with multiple providers! The providers that it
can work with are listed below. Please review the list and choose
the provider you will be working with.
1) hyperv
2) virtualbox
3) vmware_fusion
Enter your choice: 1
==> box: Adding box 'hashicorp/precise64' (v1.1.0) for provider: hyperv
box: Downloading: https://vagrantcloud.com/hashicorp/boxes/precise64/versions/1.1.0/providers/hyperv.box
Comments
Post a Comment