XenServer Architecture Overview

Architecture Section

Earlier we introduced VMware and Hyper‑V among the three major server virtualization platforms; today we continue with Citrix’s XenServer.

XenServer uses the widely deployed and powerful open‑source Xen hypervisor. Xen is an industry‑standard virtualization technology that powers many commercial products from companies such as Cisco, Symantec, Oracle, Red Hat, Novell, Sun, and is also the foundation of Amazon’s Elastic Compute Cloud, demonstrating its scalability and robustness.

XenServer delivers a complete virtual infrastructure solution, offering a hypervisor with live migration, a full‑featured management console, and tools for migrating applications, desktops, and servers from physical to virtual environments, providing advanced automation, integration, and data‑center management capabilities.

XenServer Architecture

Similar to the Hyper‑V introduction, we start with XenServer’s architecture, describing each component shown in the diagram.

Control Domain (Domain0) is a privileged Linux VM that manages network and storage I/O for all guest VMs, using Linux drivers to support a wide range of physical devices, similar to Hyper‑V’s architecture.

The Xen hypervisor is a thin software layer running directly on hardware, allowing one or more virtual servers to be created on a physical server, separating the OS and applications from the underlying hardware.

The hardware layer consists of the physical server components such as memory, CPU, and disk drives.

Linux virtual machines include a paravirtualized kernel and drivers; they access storage and network resources via the Control Domain and the Xen control interface for CPU and memory.

Windows virtual machines use paravirtualized drivers to access storage and network resources through the Control Domain. Xen leverages Intel VT and AMD‑V hardware virtualization to deliver high‑performance Windows virtualization without traditional emulation.

XenServer Management Architecture

Like Hyper‑V’s System Center and VMware’s vCenter, XenServer provides the XenCenter management tool.

Enterprise XenServer 4.0 and later introduce the concept of resource pools, allowing multiple virtualization servers to be managed as a single entity, enabling centralized management without logging into each XenServer individually. All servers share common networking and storage frameworks.

Resource pools use a master/slave high‑availability model; pool configuration is synchronized to all slave servers, ensuring business continuity if the master fails without causing fatal errors.

XenCenter can connect to and manage multiple servers and resource pools; the XenCenter Client serves as a graphical console for managing VMs and resources on XenServer.

Storage Architecture

Supports local storage (IDE, SATA, SCSI, SAS) and shared storage such as iSCSI, Fibre Channel, and NFS through an open storage management interface.

StorageLink technology integrates with NetApp, Dell/EqualLogic, IBM, and other storage solutions, providing direct API access to external SAN/NAS systems and enabling advanced services like fast cloning, LUN zeroing, thin provisioning, snapshots, and replica deletion.

Network Architecture

XenServer’s networking can connect to external physical NICs, a single server, or all virtual networks within a pool. After installing XenServer on a physical server, the system creates a network for each physical NIC.

Virtual NIC (NIC)

Each virtual machine can be configured with one or more virtual NICs, each having its own IP and MAC address, making the VM appear as an independent physical system on the network.

Virtual Switch

Since XenServer 6.0, the default virtual switch is Open vSwitch, released under the Apache license. Open vSwitch is also used by KVM, VirtualBox, OpenStack, OpenQRM, OpenNebula, and other virtualization platforms.

Virtual NICs connect to the virtual switch for network isolation. Each virtual switch can link to a physical NIC to reach the external network or operate as a fully virtual network, providing VM‑to‑VM traffic at memory‑speed performance.

VLAN Support

Virtual machines can bind to separate VLANs, isolating VM traffic from other physical servers, reducing network load, enhancing security, and simplifying reconfiguration.

Distributed Switch

With a distributed switch, users can create and manage a multi‑tenant, isolated, and flexible network, providing a secure, stateful‑migration environment for VMs. The distributed virtual switch supports ACLs, NetFlow, and network‑status monitoring.

Please search “ICT_Architect” or scan the QR code below to follow the public account for more content.

Reader Benefits

From now until 31 December 2015, the ICT Architect public account and the Best Taobao store are cooperating; by following the public account you can enjoy 88‑95% discounts on all Best Taobao store products. See the public account → Friendly Recommendations → Best Taobao Store for details.

Scan the QR code below or click “Read Original” to browse the Best Taobao store.