
KVM
This section describes the system requirements, installation and configuration procedures for vEOS.
Server
A server can be either a hardware or software entity.
A hardware server is the physical computer that executes the virtual machine manager or hypervisor and all the
virtual machines. This is also known as the host machine.
A software server is the hypervisor or virtual machine manager that hosts and manages the virtual machines. It
is also sometimes referred to as the host. In this document specifically, the software server is comprised of
RedHat Linux with virtualization support (KVM).
System Requirements
KVM (Kernel-based Virtual Machine) is a full virtualization solution for Linux on x86 hardware containing
virtualization extensions.
The vEOS is part of the Arista EOS that allows it to deploy as a virtual machine image. This document details
the system requirements of vEOS on Linux KVM based hypervisors.
Minimum Server Requirements
• Intel x86
• Four cores running at 2.4GHz or greater
• 16 GB memory
• Intel VT-d support
• For SR-IOV based deployment, the NICs need to be SR-IOV capable
Hypervisor support
• RedHat 7 with virtualization support. See below for virtualization
https://wiki.centos.org/HowTos/KVM
. Make
sure libvirt is installed by executing virsh list which should return without errors. Python 2.7+ is needed to
run the installation script vSphere 5.5 and 6.0.
Supported Images
KVM vEOS image
File Name:
EOS.qcow2
Details: Image Hard Disk that contains vEOS. This file can grow as agents in vEOS generates logs/traces, etc.
Using Libvirt to Manage vEOS VM on KVM
Libvirt is an open source library which provides vEOS management of Virtual Machines.
Libvirt supports many functions such as creation, update, and deletion and of VMs.
The complete Libvirt command reference can be found at
http://libvirt.org/virshcmdref.html
Define a new VM
Define a domain from an XML file, by using the
virsh define <vm-definition-file.xml >
command. This defines the domain, but it does not start the domain.
81
Server Requirements
Summary of Contents for vEOS
Page 6: ......
Page 12: ......
Page 60: ......
Page 72: ......
Page 77: ...7 Select the default network 8 Complete the launch process 77 Server Requirements ...
Page 94: ...Figure 17 Linux SRIOV PCI Passthrough based Deployment vEOS Router Configuration Guide 94 ...
Page 124: ......
Page 128: ......