On your guest, you should see three Intel e1000 NICs, the first one being the management interface (NATed to your host), and the two other ones belonging two the host-only private sudo lshw -class network -businfoīus info Device Class eth0 network 82540EM Gigabit Ethernet eth1 network 82540EM Gigabit Ethernet eth2 network 82540EM Gigabit Ethernet Controller The private network is accessible from your host OS via the interface vboxnet0. Host:~/vpp/build-root/vagrant$ vagrant ssh Host:~/vpp/build-root/vagrant$ vagrant up
Host:~/vpp/build-root/vagrant$ vagrant halt If your machine was already running, please restart it so as to be in a clean state. You can now boot up and access your virtual machine. With Virtualbox, this can be achieved with -> Settings -> Network -> Adapter X -> Promiscuous Mode -> Allow AllĪnother option is to set the VM NICs in promiscuous mode when updating your Vagrantfile: # Define some physical ports for your VMs to be used by DPDKĬonfig.vm.network "private_network", type: "dhcp"Īlso, make sure promiscuous mode is enabled for your VM NICs. Host:~/vpp/build-root/vagrant$ cat Vagrantfile Make sure your file looks like the following. If you have not changed your Vagrantfile, Vagrant should be configured to use two NICs on your VPP virtual machine, belonging to a private network on your host OS. Using DPDK interfaces Configuring Vagrant and start the VM
SHOULD YOU NIC TEA A VIRTUALMACHINE INSTALL
The easiest way to get it done is to install Vagrant and build a test image.
2.1 Configuring Vagrant and start the VM.
0 kommentar(er)
