| |||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||
| How to Buy | ||||||||||||||||||||||||||||||||||||||||
Table of Contents
XenServer supports the installation of many Linux distributions into paravirtualized VMs. There are three installation mechanisms at present: complete distributions provided as built-in templates, Physical-to-Virtual (P2V) of an existing native install (see Section 2.4, “Physical to Virtual Conversion (P2V)”), and using the vendor media to perform a network installation. All use of Linux VMs requires the Linux Pack to be installed onto the XenServer Host. The supported Linux distributions are:
Distributions which use the same installation mechanism as Red Hat Enterprise Linux 5 (e.g. Fedora Core 6) may successfully install using the same template. However, use of distributions not present in the above list is unsupported. This is the simplest way of installing a VM. The template provided with XenServer can be used to directly create a VM running version 3.1 (Sarge) or 4.0 (Etch) of the Debian Linux distribution without need for vendor installation media and without performing a P2V conversion of an existing physical server. The VMs are instantiated by using the vm-install from the CLI, or by cloning the template using XenCenter. For example, using the CLI on Linux: # xe vm-install template=Debian\ Etch\ 4.0 new-name-label=ExampleVM f21cd819-5b7d-002d-7a1e-861a954e770 When the VM is first booted, it will prompt you for a root password, a VNC password (for graphical use), and a hostname. After values are entered for these, it will finish at a standard login prompt, ready for use. You will need to add a network interface if installed via the CLI. | |||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||
