Software Configuration for running xen

This article is based on the relevant content in chapter 3 of Hagen's "xen virtualization alization.

Software packages are divided into required software packages and required software packages for runtime. For example, for Java applications, JDK must be installed during compilation and the Java Virtual Machine must be installed during runtime. The former is the software required for compilation, and the latter is the software required for runtime. The software described here is required for xen runtime.

Because xen has domain0 and domainu, the software requirements of domain0 and domainu are different. Domainu is a virtual computer system. Therefore, the software installed by domainu is only for users and does not require any other support. Of course, domainu must have the network communication capability, because domain0 controls it through the network. Domain0 is different. It requires more software, which is related to its tasks. Domain0 acts as an intermediary (glue) between the xen hypervisor and domainu, so it requires more software configurations, mainly including:

(1) Bridge utilities: Provides the communication capability between the physical and virtual network interfaces, http://sourceforge.net/projects/bridge;

(2) GRUB: Support for guiding xenhypervisor;

(3) SSL cryptographic libraries: www.openssl.org;

(4) iproute: Network Manager, http://linux-net.osdl.org/index.php/iproute2;

(5) Python: the version of www.python.org should be later than 2.4;

(6) pyxml: the data format tool used by xen,: http://pyxml.sourceforge.net;

(7) pyhoon logging:

(8) udev: Device Manager, http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html;

(9) zlib: the compression tool used by xen;: www.zlib.net