An Overview of Citrix XenServer Architecture and Management

Previously we introduced VMware and Hyper‑V, two of the three major server virtualization platforms; today we continue with Citrix’s XenServer.

XenServer is built on the widely deployed and powerful open‑source Xen hypervisor. Xen is an open industry‑standard virtualization technology that serves as the engine for many commercial virtualization products from companies such as Cisco, Symantec, Oracle, Red Hat, Novell, Sun, Stratus, Marathon, Egenera, FusionSphere, Neocleus, and Phoenix Technology. The world’s largest public cloud provider, Amazon EC2, also uses the Xen hypervisor, confirming Xen’s scalability and robustness.

XenServer delivers a complete virtual infrastructure solution, including a hypervisor with live‑migration capabilities, a full‑featured management console, and tools for migrating applications, desktops, and servers from physical to virtual environments. Advanced management, high availability, integration, automation, data‑center automation, and performance features are also provided.

XenServer Architecture

Similar to the Hyper‑V overview, we first examine the XenServer architecture and introduce the components shown in the diagram.

Control Domain (also called Domain0) is a privileged Linux virtual machine that manages networking and storage I/O for all guest VMs. Because it uses Linux device drivers, it supports a wide range of physical devices, similar to Hyper‑V’s architecture.

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

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

Linux virtual machines include a paravirtualized kernel and drivers (guest OS must be modified). They access storage and network resources via the Control Domain and the Xen control interface on the hardware for CPU and memory.

Windows virtual machines use paravirtualized drivers to access storage and network resources through the Control Domain. Xen is designed to fully exploit Intel VT and AMD‑V virtualization extensions, enabling high‑performance Windows virtualization without traditional emulation.

XenServer Management Architecture

Just as Microsoft System Center and VMware vCenter provide management tools, XenServer offers the XenCenter management console.

Since XenServer 4.0 Enterprise Edition, a resource‑pool concept has been introduced. Users can group multiple virtualization servers into a single entity for centralized management, sharing common networking and storage frameworks.

The pool uses a master/slave high‑availability model; configuration data is synchronized to all slave servers, ensuring business continuity if the master fails without causing fatal disruptions.

XenCenter can manage multiple servers and resource pools; the XenCenter Client provides a graphical console for managing virtual machines on XenServer.

XenServer Storage Architecture

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

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

XenServer Network Architecture

After installing XenServer on a physical server, the system creates a network for each physical NIC, allowing connections to external physical networks, a single server, or all virtualized networks within a pool.

Virtual NIC (vNIC)

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 the Apache‑licensed Open vSwitch. Other virtualization platforms such as KVM, VirtualBox, OpenStack, OpenQRM, and OpenNebula also use Open vSwitch.

Virtual NICs can connect to a virtual switch that provides network isolation. Each virtual switch can either connect to a physical NIC for external network access or be configured as a fully virtual network, delivering VM‑to‑VM traffic speeds comparable to memory.

VLAN Support

Virtual machines can be bound to separate VLANs, isolating VM traffic from other physical servers, reducing network load, improving 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 virtual machines. The distributed virtual switch supports ACLs, NetFlow, and network‑status monitoring.

Warm Tip:

Please search for “ICT_Architect” or “Scan” below the QR code to follow the public account and get more great content.