This ensures the bdev.conf file is found. Reported-by: Amir More (in GitHub issue #420) Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I309d8f211e0a3e0e4530c5d3c225a52b6ea68c2c Reviewed-on: https://review.gerrithub.io/423931 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
7.6 KiB
SPDK Vagrant and VirtualBox
The following guide explains how to use the scripts in the spdk/scripts/vagrant
. Both Mac and Windows platforms are supported.
- Install and configure Git on your platform.
- Install VirtualBox 5.1 or newer
- Install VirtualBox Extension Pack
- Install and configure Vagrant 1.9.4 or newer
Mac OSX Setup (High Sierra)
OSX platforms already have Git installed, however, installing the Apple xCode developer kit and xCode Command Line tools will provide UNIX command line tools such as make, awk, sed, ssh, tar, and zip. xCode can be installed through the App Store on you Mac.
Quick start instructions for OSX:
- Install Homebrew
- Install Virtual Box Cask
- Install Virtual Box Extentions
- Install Vagrant Cask
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
brew doctor
brew update
brew cask install virtualbox
brew cask install virtualbox-extension-pack
brew cask install vagrant
Windows 10 Setup
- Windows platforms should install Git from git-scm.com.
- This provides everything needed to use git on Windows, including a
git-bash
command line environment.
- This provides everything needed to use git on Windows, including a
- Install VirtualBox 5.1 or newer
- Install VirtualBox Extension Pack
- Install and configure Vagrant 1.9.4 or newer
- Note: VirtualBox requires virtualization to be enabled in the BIOS.
- Note: You should disable Hyper-V in Windows RS 3 laptop. Search
windows features
uncheck Hyper-V, restart laptop
Configure Vagrant
If you are behind a corporate firewall, configure the following proxy settings.
- Set the http_proxy and https_proxy
- Install the proxyconf plugin
$ export http_proxy=....
$ export https_proxy=....
$ vagrant plugin install vagrant-proxyconf
Download SPDK from GitHub
Use git to clone a new spdk repository. GerritHub can also be used. See the instructions at spdk.io to setup your GerritHub account. Note that this spdk repository will be rsync'd into your VM, so you can use this repository to continue development within the VM.
Create a Virtual Box
Use the spdk/scripts/vagrant/create_vbox.sh
script to create a VM of your choice. Supported VM platforms are:
- centos7
- ubuntu16
- ubuntu18
- fedora26
- fedora27
- freebsd11
$ spdk/scripts/vagrant/create_vbox.sh -h
Usage: create_vbox.sh [-n <num-cpus>] [-s <ram-size>] [-x <http-proxy>] [-hvr] <distro>
distro = <centos7 | ubuntu16 | ubuntu18 | fedora26 | fedora27 | freebsd11>
-s <ram-size> in kb default: 4096
-n <num-cpus> 1 to 4 default: 4
-x <http-proxy> default: ""
-r dry-run
-h help
-v verbose
Examples:
spdk/scripts/vagrant/create_vbox.sh -x http://user:password@host:port fedora27
spdk/scripts/vagrant/create_vbox.sh -s 2048 -n 2 ubuntu16
spdk/scripts/vagrant/create_vbox.sh -rv freebsd
spdk/scripts/vagrant/create_vbox.sh fedora26
It is recommended that you call the create_vbox.sh
script from outside of the spdk repository. Call this script from a parent directory. This will allow the creation of multiple VMs in separate directories, all using the same spdk repository. For example:
$ spdk/scripts/vagrant/create_vbox.sh -s 2048 -n 2 fedora26
This script will:
- create a subdirectory named in your $PWD
- copy the needed files from
spdk/scripts/vagrant/
into the directory - create a working virtual box in the directory
- rsycn the
~/.gitconfig
file to/home/vagrant/
in the newly provisioned virtual box - rsync a copy of the source
spdk
repository to/home/vagrant/spdk_repo/spdk
- rsync a copy of the
~/vagrant_tools
directory to/home/vagrant/tools
(optional)
This arrangement allows the provisioning of multiple, different VMs within that same directory hiearchy using the same spdk repository. Following the creation of the vm you'll need to ssh into your virtual box and finish the VM initializaton.
$ cd <distro>
$ vagrant ssh
Finish VM Initializtion
A copy of the spdk
repository you cloned will exist in the spdk_repo
directory of the /home/vagrant
user account. After using vagrant ssh
to enter your VM you must complete the initialization of your VM by running the scripts/vagrant/update.sh
script. For example:
$ script -c 'sudo spdk_repo/spdk/scripts/vagrant/update.sh' update.log
The update.sh
script completes initialization of the VM by automating the following steps.
- Runs yum/apt-get update (Linux)
- Runs the scripts/pdkdep.sh script
- Installs the FreeBSD source in /usr/sys (FreeBSD only)
This only needs to be done once.
Post VM Initializtion
Following VM initializtion you must:
- Verify you have an emulated NVMe device
- Compile your spdk source tree
- Run the hello_world example to validate the environment is set up correctly
Verify you have an emulated NVMe device
$ lspci | grep "Non-Volatile"
00:0e.0 Non-Volatile memory controller: InnoTek Systemberatung GmbH Device 4e56
Compile SPDK
$ cd spdk_repo/spdk
$ git submodule update --init
$ ./configure --enable-debug
$ make
Run the hello_world example script
$ sudo scripts/setup.sh
$ cd examples/bdev/hello_world
$ sudo ./hello_bdev
Additional Setup for Fedora 26
As of this writing the vm_setup.sh
script only supports Fedora 26. To complete the full installation of all packages needed to run autotest.sh on your fedora26 VM, run the spdk/test/common/config/vm_setup.sh
script. Note: this will take some time. It is recommended that the output of vm_setup.sh is captured in a script log.
$ script -c 'spdk_repo/spdk/test/common/config/vm_setup.sh -i -t librxe,iscsi,rocksdb,fio,flamegraph,libiscsi' vm_setup.log
Running autorun.sh with vagrant
After running vm_setup.sh the run-autorun.sh
can be used to run spdk/autorun.sh
on a Fedora 26 vagrant machine. Note that the spdk/scripts/vagrant/autorun-spdk.conf
should be copied to ~/autorun-spdk.conf
before starting your tests.
$ cp spdk/scripts/vagrant/autorun-spdk.conf ~/
$ spdk/scripts/vagrant/run-autorun.sh -h
Usage: scripts/vagrant/run-autorun.sh -d <path_to_spdk_tree> [-h] | [-q] | [-n]
-d : Specify a path to an SPDK source tree
-q : No output to screen
-n : Noop - dry-run
-h : This help
Examples:
run-spdk-autotest.sh -d . -q
run-spdk-autotest.sh -d /home/vagrant/spdk_repo/spdk
FreeBSD Appendix
NOTE: As of this writing the FreeBSD Virtualbox instance does not correctly support the vagrant-proxyconf feature.
The following steps are done by the update.sh
script. It is recommened that you capture the output of update.sh
with a typescript. E.g.:
$ script update.log sudo spdk_repo/spdk/scripts/vagrant/update.sh
- Updates the pkg catalog
- Installs the needed FreeBSD packages on the system by calling pkgdep.sh
- Installs the FreeBSD source in /usr/src
$ sudo pkg upgrade -f
$ sudo spdk_repo/spdk/scripts/pkgdep.sh
$ sudo git clone --depth 10 -b releases/11.1.0 https://github.com/freebsd/freebsd.git /usr/src
To build spdk on FreeBSD use gmake MAKE=gmake
. E.g.:
$ cd spdk_repo/spdk
$ git submodule update --init
$ ./configure --enable-debug
$ gmake MAKE=gmake