• Tag : KVM



Introduction vEOS-lab/cEOS-lab on GNS3 – What is it? Fast, Multi-user, Efficient nested virtual lab using Qemu/Kvm/docker images of vEOS-lab/cEOS-lab Dynamic persistent config/storage of each cEOS container across stop/starts and GNS3 project closure/re-opens Deployed in minutes on ESXi host. Cloning and creating another bubble is easy, fast and can be moved around Integrated data plane traffic generation tool (Ostinato) in this lab Packet capture on any links between vEOS/cEOS devices Required SW/HW  GNS3 Server VM (Ubuntu 18.04 LTS VM + GNS3 Server) VMware Host system running ESXi version 6 or above with Mgmt Network access ESXi host to deploy this GNS3...
Continue reading →

vEOS BGP fails to establish with Cumulus VX

I’m running vEOS (4.17.0F) in a KVM hypervisor along with an instance of Cumulus VX 3.0.1. I’m attempting to bring up a simple BGP session between the devices through a virbr virtual network, but AFACT the vEOS instance is failing to ack any SYN packets to TCP/179 coming from the Cumulus instance; every 30 seconds the vEOS instance sends a SYN to TCP/179 to the Cumulus instance, which then sends a SYNACK back…which vEOS doesn’t acknowledge either. I’m not seeing any oddities WRT the BGP configs or basic reachability (the fact that I do see SYNs going in both directions...
Continue reading →

unable to load EOS image in OpenStack/KVM

Hello all, Recently I tried to install the vEOS on KVM/OpenStack. In OpenStack, I created two images for Aboot and vEOS vmdk files. An instance is created with the Aboot image to get it loaded properly and the vEOS vmdk image is attached as a storage (Attached To vEOS 4.15.0F on /dev/vda). Unfortunately, the instance loads and stopped with error in the attached screenshot. It seems the Aboot image is unable to find the attached storage in order to load the EOS image. Wondering if you experienced this and have a solution / workaround. Thanks, Steven

Problem in installing EOS image on KVM

Executing the following cmd, cant open iso image. Any help please. /usr/libexec/qemu-kvm -nographic -vga std -cdrom Aboot-veos-2.0.8.iso d -hda vEOS-lab-4.14.5F.vmdk -usb -m 1024 -net nic,macaddr=52:54:00:01:02:03,model=e1000  -net nic,macaddr=52:54:00:01:02:04,model=e1000 -net nic,macaddr=52:54:00:01:02:05,model=e1000 -net nic,macaddr=52:54:00:01:02:06,model=e1000 -net nic,macaddr=52:54:00:01:02:07,model=e1000   qemu-kvm: -cdrom Aboot-veos-2.0.8.iso: could not open disk image d: No such file or directory

Virtual Machines in EOS

How-to implement virtual machines in Arista EOS Virtualization was first developed in the 1960s and used to partition mainframe hardware to improve utilization. Today, virtualization has many meanings and widely implemented on a variety of platforms. Arista EOS leveraging it’s unmodified Linux kernel and embracing open source standards based technology has brought the concept of operating system virtualization to Ethernet switching. The approach that Arista has taken is to utilize Kernel-based Vitual Machines (KVM). Turning the Linux kernel into a hypervisor by loading a kernel module which provides the core virtualization infrastructure, a processor specific module (Intel or AMD) which...
Continue reading →


Get every new post on this blog delivered to your Inbox.

Join other followers: