I just fought installing VIRL on bare metal for nearly four days. I worked my way through multiple how-to’s and installed it three different times. Eventually I gave up doing it by the book and tried my own thing.
First, some back story. Linux changed the way network cards are named, and it appears that each vendor has implemented their own fix. As of version 1.2.84 VIRL is based on Lightweight Ubuntu (LUBUNTU) 14.04. Ubuntu has changed the network cards from being named eth0 through eth5 to em1 through whatever. I say whatever because it depends upon the cards you have installed.
For instance on my Dell R710 the cards were named em1, em2, em3, em4, p1p1 and p1p2. These stand for embedded network interface one through four, PCI slot 1 interface 1 and PCI slot 1 interface 2. Under the old naming scheme they would have been named eth0 through eth5.
The problem arises in that Openstack underneath VIRL is configured for eth0 through eth5. I worked my way through a number of different how-to’s, which are listed below, but I always seemed to end up with a problem.
Finally I just changed my interface back from the new naming scheme to the old ethX naming scheme.
I edited the file /etc/default/grub and added the following lines.
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX_DEFAULT="biosdevname=0"
GRUB_CMDLINE_LINUX="biosdevname=0
Because I had been fighting with the install, I also rehosted the install to make sure my interfaces lined back up.
sudo vinstall rehost
Then I rebooted my VIRL host and everything worked. I should have followed my gut and saved myself four days of lost study time.
List of different things I tried:
https://askubuntu.com/questions/680409/problems-setting-up-internet-connection-ubuntu-server-14-04-no-eth0
https://www.speaknetworks.com/cisco-virl-installation-on-bare-metal-standalone-server/
https://www.speaknetworks.com/cisco-virl-installation-on-vmware-esxi/
https://learningnetwork.cisco.com/docs/DOC-30422
https://learningnetwork.cisco.com/docs/DOC-30519
https://learningnetwork.cisco.com/docs/DOC-32305#jive_content_id_Resetting_NTP_Servers_via_UWM
ChainRingCircus 