// Lesson 7 of 49 · Network fundamentals
Virtualisation fundamentals
Most servers you connect today are virtual. The network has to reach them and, increasingly, runs inside the same virtualised platforms.
Virtual machines and hypervisors
A hypervisor lets one physical server run many virtual machines (VMs), each with its own operating system.
- Type 1 (bare metal) runs directly on the hardware — VMware ESXi, Microsoft Hyper-V, KVM. Used in data centres.
- Type 2 (hosted) runs on top of a normal OS — VirtualBox, VMware Workstation. Used on laptops and in labs.
Each VM has virtual NICs connected to a virtual switch inside the hypervisor. The virtual switch connects to the physical network through the server's real NICs, usually as an 802.1Q trunk so each VM can sit in its own VLAN.
Containers
Containers package an application with its libraries but share the host's kernel. They start in seconds and use far less memory than VMs. Docker and Kubernetes are the common tools. Containers communicate over virtual networks managed by the container platform.
VRFs — virtual routing tables
A VRF (virtual routing and forwarding) instance gives one router several independent routing tables. Interfaces placed in different VRFs cannot reach each other unless you deliberately leak routes. Service providers use VRFs to keep customers apart; enterprises use them to separate, for example, management traffic or guest networks.
Key points
- Type 1 hypervisors run on hardware; type 2 run on an OS.
- VMs connect to virtual switches, usually trunked to the physical network.
- Containers share the host kernel and are lighter than VMs.
- VRFs create separate routing tables on one device.
Sign in to save your lesson progress across devices. You can read every published lesson without an account.