Citrix, Inc.
851 West Cypress Creek Road
Fort Lauderdale, FL 33309
United States of America
Disclaimers
This document is furnished "AS IS." Citrix, Inc. disclaims all warranties regarding the contents of this document,
including, but not limited to, implied warranties of merchantability and fitness for any particular purpose. This
document may contain technical or other inaccuracies or typographical errors. Citrix, Inc. reserves the right to
revise the information in this document at any time without notice. This document and the software described
in this document constitute confidential information of Citrix, Inc. and its licensors, and are furnished under a
license from Citrix, Inc.
Citrix Systems, Inc., the Citrix logo, Citrix XenServer and Citrix XenCenter, are trademarks of Citrix Systems, Inc.
and/or one or more of its subsidiaries, and may be registered in the United States Patent and Trademark Office
and in other countries. All other trademarks and registered trademarks are property of their respective owners.
Trademarks
Citrix®
XenServer ®
XenCenter ®
Contents
1. About this Document .................................................................................... 1
F. Troubleshooting VM Problems .................................................................... 70
F.1. VM Crashes ................................................................................................................ 70
F.1.1. Controlling Linux VM Crashdump Behaviour ...................................................... 70
F.1.2. Controlling Windows VM Crashdump Behaviour ................................................ 70
F.2. Troubleshooting Boot Problems on Linux VMs .............................................................. 71
vii
Chapter 1. About this Document
1.1. Overview
This is a guide to using Virtual Machines (VMs) with XenServer™, the platform virtualization solution from Citrix®.
It describes how to create, configure, and manage VMs running on XenServer hosts.
This section summarizes the rest of the guide so that you can find the information you need. The following topics
are covered:
• General information about preparing and creating VMs
• Creating Windows VMs
• Creating Linux VMs
• Updating VMs
• Migrating VMs
• Creating and using ISO images of vendor media for installing VMs
• Setting up a network repository of vendor media for installing VMs
• Troubleshooting VMs
1.2. XenServer Documentation
XenServer documentation shipped with this release includes:
• Release Notes cover known issues that affect this release.
• XenServer Quick Start Guide provides an introduction for new users to the XenServer environment and
components. This guide steps through the installation and configuration essentials to get XenServer and the
XenCenter management console up and running quickly. After installation, it demonstrates how to create a
Windows VM, VM template and pool of XenServer hosts. It introduces basic administrative tasks and advanced
features, such as shared storage, VM snapshots and XenMotion live migration.
• XenServer Installation Guide steps through the installation, configuration and initial operation of XenServer
and the XenCenter management console.
• XenServer Virtual Machine User's Guide describes how to install Windows and Linux VMs within a XenServer
environment. This guide explains how to create new VMs from installation media, from VM templates included
in the XenServer package and from existing physical machines (P2V). It explains how to import disk images and
how to import and export appliances.
• XenServer Administrator's Guide gives an in-depth description of the tasks involved in configuring a XenServer
deployment, including setting up storage, networking and pools. It describes how to administer XenServer
using the xe Command Line Interface.
• vSwitch Controller User's Guide is a comprehensive user guide to the vSwitch Controller for XenServer.
• Supplemental Packs and the DDK introduces the XenServer Driver Development Kit, which can be used to
modify and extend the functionality of XenServer.
• XenServer Software Development Kit Guide presents an overview of the XenServer SDK. It includes code
samples that demonstrate how to write applications that interface with XenServer hosts.
• XenAPI Specification is a reference guide for programmers to the XenServer API.
For additional resources, visit the Citrix Knowledge Center.
1
Chapter 2. Virtual Machines
This chapter provides an overview of how to create Virtual Machines (VMs) using templates. It also explains other
preparation methods, including physical to virtual conversion (P2V), cloning templates, and importing previouslyexported VMs.
What is a Virtual Machine?
A Virtual Machine (VM) is a software computer that, like a physical computer, runs an operating system and
applications. The VM is comprised of a set of specification and configuration files and is backed by the physical
resources of a host. Every VM has virtual devices that provide the same functionality as physical hardware, and
can have additional benefits in terms of portability, manageability, and security. In addition, you can tailor the
boot behavior of each VM to your specific requirements - for more information refer to Section 9.1, “VM Boot
Behavior”.
XenServer supports guests with any combination of IPV4 or IPv6 configured addresses.
2.1. Creating VMs
2.1.1. Using VM Templates
VMs are prepared from templates. A template is a "gold image" that contains all the various configuration settings
to instantiate a specific VM. XenServer ships with a base set of templates, which are "raw" VMs, on which you
can install an operating system. Different operating systems require different settings in order to run at their
best. Linux templates create ParaVirtualized (PV) guests, whereas Windows templates create Hardware Virtual
Machine (HVM) guests. XenServer templates are tuned to maximize operating system performance.
There are two basic methods by which you can create VMs from templates:
• Using a complete pre-configured template, for example the Demo Linux VM.
• Installing an operating system from a CD or an ISO image onto the appropriate provided template.
You install operating systems onto VMs from either a vendor installation CD, or from an ISO repository, or can
choose use a complete pre-configured OS instance.
Chapter 4, Creating Windows VMs describes how to install Windows operating systems onto VMs.
Chapter 5, Creating Linux VMs describes how to install Linux operating systems onto VMs.
2.2. Other Methods of VM Creation
In addition to creating VMs from the provided templates, there are 3 other methods that you can use to create
VMs.
1. Physical to Virtual Conversion (P2V)
2. Cloning an existing VM
3. Importing an exported VM
2.2.1. Physical to Virtual Conversion (P2V)
Physical to Virtual Conversion (P2V) is the process by which an existing Windows operating system on a physical
server — its file system, configuration, and so on — is converted to a virtualized instance of the operating system.
This is then is transferred, instantiated, and started as a VM on the XenServer host.
2.2.2. Cloning an Existing VM
You can make a copy of an existing VM by cloning from a template. Templates are ordinary VMs which are intended
to be used as master copies to instantiate VMs from. A VM can be customized and converted into a template;
2
be sure to follow the appropriate preparation procedure for the VM (see Section 9.9, “Preparing for Cloning a
Windows VM Using VSS” for Windows and Section 5.7, “Preparing to Clone a Linux VM” for Linux).
Note:
Templates cannot be used as normal VMs.
XenServer has two mechanisms for cloning VMs:
1. A full copy
2. Copy-on-Write (CoW)
The faster Copy-on-Write (CoW) mode only writes modified blocks to disk and is only supported for filebacked VMs. CoW is designed to save disk space and allow fast clones, but will slightly slow down normal disk
performance. A template can be fast-cloned multiple times without slowdown.
Note:
If a template is cloned into a VM and the clone converted back into a template, disk
performance can linearly decrease depending on the number of times this has happened. In
this event, the vm-copy CLI command can be used to perform a full copy of the disks and
restore expected levels of disk performance.
Notes for Resource Pools
If you create a template on a server where all VM virtual disks are on shared Storage Repositories (SR), the
template cloning operation will be forwarded to any server in the pool that can access the shared SRs. However,
if you create the template from a VM virtual disk that only has a local SR, then the template clone operation can
only execute on the server that can access that SR.
2.2.3. Importing an Exported VM
You can create a VM by importing an existing exported VM. Like cloning, exporting and importing a VM is fast way
to create additional VMs of a certain configuration so that you can increase the speed of your deployment. You
might, for example, have a special-purpose server configuration that you use many times. Once you have set up a
VM the way you want it, you can export it, and import it later to create another copy of your specially-configured
VM. You can also use export and import to move a VM to a XenServer host that is in another resource pool.
For details and procedures on importing and exporting VMs, see Chapter 11, Importing and Exporting VMs.
2.3. XenServer Tools
XenServer Tools must be installed for each Virtual Machine (Windows and Linux) in order for the VM to have a
fully supported configuration, and to be able to use the XenServer management tools (the xe CLI or XenCenter).
A Windows VM will function without them, but performance will be significantly hampered unless the tools are
installed.
Without the tools being installed, you cannot:
• Cleanly shut down a VM
• Cleanly reboot a VM
• Suspend a VM
• Migrate a running VM (XenMotion)
• Use the checkpoint and roll back feature
• Dynamically adjust the number of vCPUs assigned to a running Linux VM- Windows VMs require a reboot for
this to take effect
For further information about XenServer Tools see Section 9.3, “XenServer Tools”
3
Warning:
Running a VM without installing the XenServer Tools is not a supported configuration.
4
Chapter 3. Supported Guests and Allocating
Resources
This chapter describes how to allocate resources to your VMs, and the supported guest operating systems. It lists
virtual memory and virtual disk size minimums, and describes the differences in virtual device support for the
members of the XenServer product family.
3.1. Supported Guests, Virtual Memory, and Disk Size Limits
When installing VMs, follow the memory and disk space guidelines of the operating system and any relevant
applications, when allocating resources such as memory and disk space.
Note:
Individual versions of the operating systems may also impose their own maximum limits on
the amount of memory supported (for example, for licensing reasons).
Warning:
When configuring guest memory, do not to exceed the maximum amount of physical memory
addressable by your operating system. Setting a memory maximum that is greater than the
operating system supported limit may lead to stability problems within your guest.
Operating SystemMinimum
RAM
Windows 8 (32-bit)1GB4GB24GB (40GB or more
Windows 8 (64-bit)2GB128GB24GB (40GB or more
Windows 7, Windows 7 SP1 (32-bit)1GB4GB24GB (40GB or more
Windows 7, Windows 7 SP1 (64-bit)2GB128GB24GB (40GB or more
Windows Server 2012 (64-bit)512MB128GB24GB (40GB or more
Windows Server 2008 R2, Windows
Server 2008 R2 SP1 (64-bit)
Windows Server 2008 SP2 (32-bit)512MB64GB24GB (40GB or more
Windows Server 2008 SP2 (64-bit)512MB128GB24GB (40GB or more
512MB128GB24GB (40GB or more
Maximum
RAM
Minimum Disk Space
recommended)
recommended)
recommended)
recommended)
recommended)
recommended)
recommended)
recommended)
Windows Server 2003 SP2 (32-bit)256MB64GB8GB (16GB or more
recommended)
Windows Server 2003 SP2 (64-bit)256MB128GB8GB (16GB or more
recommended)
Windows Vista SP2 (32-bit)1GB4GB24GB (40GB or more
Red Hat Enterprise Linux 5.8, 5.9 (32-bit)512MB16GB8GB
Red Hat Enterprise Linux 5.8, 5.9 (64-bit)512MB128GB8GB
Red Hat Enterprise Linux 6.0, 6.1 (32-bit)512MB8GB8GB
512MB16GB8GB
256MB16GB8GB
512MB16GB8GB
Red Hat Enterprise Linux 6.0, 6.1 (64-bit)512MB32GB8GB
Red Hat Enterprise Linux 6.2, 6.3, 6.4
(32-bit)
Red Hat Enterprise Linux 6.2, 6.3, 6.4
(64-bit)
SUSE Linux Enterprise Server 10 SP1,
SLES 10 SP2, SLES 10 SP3, SLES 10 SP4
(32-bit)
SUSE Linux Enterprise Server 10 SP1,
SLES 10 SP2, SLES 10 SP3, SLES 10 SP4
(64-bit)
SUSE Linux Enterprise Server 11, SLES 11
SP1, SLES 11 SP2 (32-bit)
SUSE Linux Enterprise Server 11, SLES 11
SP1, SLES 11 SP2 (64-bit)
Oracle Enterprise Linux 5.0, 5.1, 5.2, 5.3,
5.4, 5.5, 5.6, 5.7 (32-bit)
512MB16GB8GB
512MB128GB8GB
512MB16GB8GB
512MB128GB8GB
512MB16GB8GB
512MB128GB8GB
512MB64GB8GB
6
Operating SystemMinimum
RAM
Maximum
RAM
Minimum Disk Space
Oracle Enterprise Linux 5.0, 5.1, 5.2, 5.3,
5.4, 5.5, 5.6, 5.7 (64-bit)
Oracle Enterprise Linux 5.8, 5.9 (32-bit)512MB16GB8GB
Oracle Enterprise Linux 5.8, 5.9 (64-bit)512MB128GB8GB
Oracle Enterprise Linux 6.0, 6.1 (32-bit)512MB8GB8GB
Oracle Enterprise Linux 6.0, 6.1 (64-bit)512MB32GB8GB
Oracle Enterprise Linux 6.2, 6.3, 6.4 (32bit)
Oracle Enterprise Linux 6.2, 6.3, 6.4 (64bit)
Debian Squeeze 6.0 (32-/64-bit)128MB32GB8GB
Debian Wheezy 7.0 (32-bit)512MB16GB8GB
Debian Wheezy 7.0 (64-bit)512MB128GB8GB
Ubuntu 10.04 (32-bit)128MB512MB8GB
Ubuntu 10.04 (64-bit)128MB32GB8GB
512MB128GB8GB
512MB16GB8GB
512MB128GB8GB
Ubuntu 12.04 (32-bit)128MB32GB8GB
Ubuntu 12.04 (64-bit)128MB128GB8GB
Important:
RHEL, OEL, and CentOS 5.0 guest operating systems with the original kernel will fail to boot on
XenServer 6.2.0. Before attempting to upgrade a XenServer host to version 6.2.0, customers
should update the kernel to version 5.4 (2.6.18-164.el5xen) or later. Customers running these
guests that have already upgraded their XenServer host to version 6.2.0, should refer to the
Citrix Knowledge Base article, CTX134845 for information on upgrading the kernel.
Note:
Some 32-bit Windows operating systems can support more than 4 GB of RAM through the
use of a special mode: physical address extension (PAE) mode. If you want to reconfigure a
VM with greater than 4 GB of RAM, you must use the xe CLI, not XenCenter, as the CLI does
not impose any upper bounds for memory-static-max.
For more information on how to set the memory static max, refer to the Dynamic Memory
Control chapter, in the XenServer Administrator's Guide.
3.2. Experimental Guests
The following table lists the experimental guest operating systems in XenServer 6.2.0.
Operating System
Ubuntu Maverick Meerkat 10.10 (32-bit)
7
Operating System
Ubuntu Maverick Meerkat 10.10 (64-bit)
Warning:
Experimental guest operating systems have received limited testing, may not be present
in future product releases and must not be enabled on production systems. Citrix may not
respond to support requests regarding experimental features.
3.3. Deprecated Guests
The following table lists the deprecated guest operating systems in XenServer 6.2.0.
Operating System
Debian Lenny 5.0 (32-bit)
SUSE Linux Enterprise Server 9 SP4 (32-bit)
Windows Server 2008 (base release) (32-bit)
Windows Server 2008 (base release) (64-bit)
Windows Server 2003 (base release), Windows Server 2003 SP1 (32-bit)
Windows Server 2003 (base release), Windows Server 2003 SP1 (64-bit)
Windows Vista (base release), Windows Vista SP1 (32-bit)
Note:
There will be no option to engage Citrix's product development resources, and technical
workarounds may be limited or not possible for customers on unsupported guest operating
systems. If the support incident requires escalation to development for further guidance,
requires a hotfix, or requires a security update, customers will be asked to upgrade to a
supported service pack.
3.4. XenServer Product Family Virtual Device Support
The current version of the XenServer product family has the following general limitations on virtual devices for
VMs. Note that specific guest operating systems may have lower limits for certain features. The individual guest
installation section notes the limitations.
Virtual deviceLinux VMsWindows VMs
Number of virtual CPUs32
*
16
Number of virtual disks7 (including virtual CD-ROM)7 (including virtual CD-ROM)
Number of virtual CD-ROM drives11
Number of virtual NICs7
*
A maximum of 16 vCPUs are supported by XenCenter.
†
except for SLES 10 SP1 and RHEL 4.x, which support 3. RHEL 5.0/5.1/5.2 support 3, but can support 7 when the kernel is patched with the
XenServer Tools. The same applies for Oracle and CentOS 5.0/5.1/5.2.
†
7
8
3.4.1. VM Block Devices
In the para-virtualized (PV) Linux case, block devices are passed through as PV devices. XenServer does not
attempt to emulate SCSI or IDE, but instead provides a more suitable interface in the virtual environment in the
form of xvd* devices. It is also sometimes possible (depending on the OS) to get an sd* device using the same
mechanism, where the PV driver inside the VM takes over the SCSI device namespace. This is not desirable so it
is best to use xvd* where possible for PV guests (this is the default for Debian and RHEL).
For Windows or other fully virtualized guests, XenServer emulates an IDE bus in the form of an hd* device. When
using Windows, installing the XenServer Tools installs a special PV driver that works in a similar way to Linux,
except in a fully virtualized environment.
9
Chapter 4. Creating Windows VMs
Warning:
Running a VM without installing the XenServer Tools is not a supported configuration. For
more information, see Section 2.3, “XenServer Tools”.
Installing Windows VMs on a XenServer host requires hardware virtualization support (Intel VT or AMD-V).
4.1. Basic Procedure for Creating a Windows VM
The process of installing a Windows on to a VM can be broken down into three steps:
• selecting the appropriate Windows template
• installing the Windows operating system
• installing the paravirtualized device drivers known as the XenServer Tools
4.2. Available Windows Templates
Windows operating systems are installed onto VMs by cloning an appropriate template using either XenCenter or
the xe CLI, and then installing the operating system. The templates for individual guests have predefined platform
flags set which define the configuration of the virtual hardware. For example, all Windows VMs are installed with
the ACPI Hardware Abstraction Layer (HAL) mode enabled. If you subsequently change one of these VMs to have
multiple virtual CPUs, Windows automatically switches the HAL to multi-processor mode.
The available Windows templates are listed below:
Template NameDescription
Citrix XenApp on Windows Server 2003
(32-bit)
Citrix XenApp on Windows Server 2003
(64-bit)
Citrix XenApp on Windows Server 2008
(32-bit)
Citrix XenApp on Windows Server 2008
(64-bit)
Citrix XenApp on Windows Server 2008
R2 (64-bit)
Used to install Windows Server 2003 SP2 (32-bit). The Server,
Enterprise, Data Centre, and SBS editions are supported. This
template is specially tuned to optimize XenApp performance.
Used to install Windows Server 2003 SP2 (64-bit). The Server,
Enterprise, Data Centre, and SBS editions are supported. This
template is specially tuned to optimize XenApp performance.
Used to install Windows Server 2008 SP2 (32-bit). All editions are
supported. This template is specially tuned to optimize XenApp
performance.
Used to install Windows Server 2008 SP2 (64-bit). All editions are
supported. This template is specially tuned to optimize XenApp
performance.
Used to install Windows Server 2008 R2 and Windows Server
2008 R2 SP1 (64-bit). All editions are supported. This template is
specially tuned to optimize XenApp performance.
Windows 7 (32-bit)Used to install Windows 7 and Windows 7 SP1 (32-bit).
Windows 7 (64-bit)Used to install Windows 7 and Windows 7 SP1 (64-bit).
Windows 8 (32-bit)Used to install Windows 8 (32-bit).
Windows 8 (64-bit)Used to install Windows 8 (64-bit).
10
Template NameDescription
Windows Server 2003 (32-bit)Used to install Windows Server 2003 SP2 (32-bit). The Server,
Enterprise, Data Centre, and SBS editions are supported.
Windows Server 2003 (64-bit)Used to install Windows Server 2003 SP2 (64-bit). The Server,
Enterprise, Data Centre, and SBS editions are supported.
Windows Server 2008 (32-bit)Used to install Windows Server 2008 SP2 (32-bit). All editions are
supported.
Windows Server 2008 (64-bit)Used to install Windows Server 2008 SP2 (64-bit). All editions are
supported.
Windows Server 2008 R2 (64-bit)Used to install Windows Server 2008 R2 and Windows Server 2008
R2 SP1 (64-bit). All editions are supported.
Windows Server 2012 (64-bit)Used to install Windows Server 2012 (64-bit).
Windows Vista (32-bit)Used to install Windows Vista SP2 (32-bit). The Enterprise edition
is supported.
Windows XP SP3 (32-bit)Used to install Windows XP SP3 (32-bit). Earlier service packs are
not supported.
Warning:
Experimental guest operating systems have received limited testing, may not be present
in future product releases and must not be enabled on production systems. Citrix may not
respond to support requests regarding experimental features.
4.2.1. Attaching an ISO Image Library
The Windows operating system can be installed either from an install CD in a physical CD-ROM drive on the
XenServer host, or from an ISO image. See Appendix C, Creating ISO Images for information on how to make an
ISO image from a Windows install CD and make it available for use.
4.3. Using XenCenter to Create a VM
To create a Windows 7 (32-bit) VM:
Note:
The following procedure provides an example of creating Windows 7 (32-bit) VM. The default
values may vary depending on the operating system that you choose.
1.On the XenCenter toolbar, click the New VM button to open the New VM wizard.
The New VM wizard allows you to configure the new VM, adjusting various parameters for CPU, storage and
networking resources.
2.Select a VM template and click Next.
Each template contains the setup information needed to create a new VM with a specific guest operating
system (OS), and with optimum storage. This list reflects the templates that XenServer currently supports.
Note:
If the OS that you intend to install on your new VM is compatible only with the original
hardware (for example, an OS installation CD that was packaged with a specific computer),
check the Copy host BIOS strings to VM box.
11
To copy BIOS strings using the CLI, see Section 9.8, “Installing a VM from Reseller Option Kit
(BIOS-locked) Media”
3.Enter a name and an optional description for the new VM.
4.Choose the source of the OS media to install on the new VM.
Installing from a CD/DVD is the simplest option for getting started. To do so, choose the default installation
source option (DVD drive), insert the disk into the DVD drive of the XenServer host, and choose Next to
proceed.
XenServer also allows you to pull OS installation media from a range of sources, including a pre-existing ISO
library. An ISO image is a file that contains all the information that an optical disc (CD, DVD, and so on) would
contain. In this case, an ISO image would contain the same OS data as a Windows installation CD.
To attach a pre-existing ISO library, click New ISO library and indicate the location and type of ISO library.
You can then choose the specific operating system ISO media from the drop-down list.
5.The VM will run on the installed host. Choose Next to proceed.
6.For a Windows 7 VM, the default is 1 virtual CPU and 2048 MB of RAM. You may also choose to modify the
defaults. Select Next to continue.
7.Allocate and configure storage for the new VM.
Click Next to select the default allocation (24 GB) and configuration, or you may wish to:
a.Change the name, description or size of your virtual disk by clicking Properties.
b.Add a new virtual disk by selecting Add.
8.Configure networking on the new VM.
Click Next to select the default network interface card (NIC) and configurations, including an automaticallycreated unique MAC address for each NIC, or you may wish to:
a.Change the physical network, MAC address or quality-of-service (QoS) priority of the virtual disk by
clicking Properties.
b.Add a new virtual NIC by selecting Add.
9.Review settings, and then click Finish to create the new VM and return to the Search tab.
An icon for your new VM appears under the host in the Resources pane.
On the Resources pane, select the VM, and then click the Console tab to see the VM console.
10. Follow the OS installation screens and make your selections.
11. Once the OS installation completes and the VM reboots, install the XenServer Tools.
XenServer Tools provide high-speed I/O for enhanced disk and network performance. XenServer Tools must
be installed on each VM in order for the VM to have a fully-supported configuration. A VM will function
without them, but performance will be significantly hampered. XenServer Tools also enable certain functions
and features, including cleanly shutting down, rebooting, suspending and live migrating VMs.
Warning:
You must install XenServer Tools for each VM. Running VMs without XenServer Tools is not
supported. For more information on XenServer Tools see Section 9.3, “XenServer Tools”.
Note:
To install XenServer Tools on a Windows VM, the VM must be running the Microsoft .NET
Framework Version 4.0 or later. If a VM is running Windows 2003, you need to install the
12
Windows Imaging Component (see your vendor documentation for details) before installing
XenServer Tools.
To install XenServer Tools:
a.On the Resources pane, select the XenServer host and then the Search tab.
The XenServer Tools not installed blue status text appears next to the new VM.
b.Click the text to open the XenServer Tools setup wizard on the VM console.
c.Click the Install XenServer Tools button, and then Run Xensetup.exe.
d.When prompted, click Yes to allow the program to make changes to the computer.
e.Accept the License Agreement, and click Next to continue.
f.Choose a destination folder and click Install.
g.Select Reboot now, and then Finish to complete the installation.
4.4. Using the CLI to Create a Windows VM
This section describes the procedure to create a Windows VM from an ISO repository using the xe CLI.
Installing a Windows VM from an ISO Repository Using the CLI
At this point, the VM console will now be visible in XenCenter.
For more information on using the CLI, see Appendix A, Command Line Interface, in the XenServer Administrator'sGuide.
13
Chapter 5. Creating Linux VMs
This chapter discusses how to create Linux VMs, either by installing them or cloning them. This chapter also
contains vendor-specific installation instructions.
When you want to create a new VM, you must create the VM using a template for the operating system you
want to run on the VM. You can use a template Citrix provides for your operating system, or one that you created
previously. You can create the VM from either XenCenter or the CLI. This chapter will focus on using the CLI.
You will need to install the XenServer Tools immediately after installing the operating system. For some operating
systems, the XenServer Tools includes a XenServer specific kernel, which replaces the kernel provided by the
vendor. Other operating systems, such as RHEL 5.x require you to install a specific version of a vendor provided
kernel.
Warning:
Running a VM without installing the XenServer Tools is not a supported configuration, so Citrix
recommends that you install the tools immediately after Operating System installation. For
more information, see Section 2.3, “XenServer Tools”.
The overview for creating a Linux VM is as following:
1. Create the VM for your target operating system using XenCenter or the CLI.
2. Install the operating system using vendor installation media.
3. Install the XenServer Tools.
4. Configure the correct time and time zone on the VM and VNC as you would in a normal non-virtual
environment.
XenServer supports the installation of many Linux distributions as VMs. There are three installation mechanisms:
1. Installing from an internet repository
2. Installing from a physical CD
3. Installing from an ISO library
Warning:
The Other install media template is meant for advanced users who want to attempt to install
VMs running unsupported operating systems. XenServer has been tested running only the
supported distributions and specific versions covered by the standard supplied templates,
and any VMs installed using the Other install media template are not supported.
Note that VMs created using the Other install media template will be created as HVM guests,
which means that the Linux VMs created using this template will not be able to use the native
high-performance drivers (PV drivers) included in modern kernels.
For information regarding specific Linux distributions, see Section 5.6, “Additional Installation Notes for Linux
Distributions”.
14
The supported Linux distributions are:
DistributionVendor
Install
from CD
Debian Squeeze 6.0 (32-/64-bit)XX
Debian Wheezy 7.0 (32-/64-bit)XX
Red Hat Enterprise Linux 4.5, 4.6, 4.7, 4.8 (32-bit)XXRequires installing
Red Hat Enterprise Linux 5.0, 5.1, 5.2, 5.3, 5.4, 5.5,
5.6, 5.7, 5.8, 5.9 (32-/64-bit)
Red Hat Enterprise Linux 6.0, 6.1, 6.2, 6.3, 6.4
(32-/64-bit)
SUSE Linux Enterprise Server 10 SP1, SLES 10 SP2,
SLES 10 SP4 (32-/64-bit)
SUSE Linux Enterprise Server 10 SP3 (32-bit)Supported only if
XXSupported provided you
XX
XX
Vendor Install
from network
repository
Notes
XenServer Tools after
installing RHEL to apply
the Citrix RHEL 4.8
kernel.
use the 5.4 or later
kernel.
upgrading from SLES 10
SP2
SUSE Linux Enterprise Server 10 SP3 (64-bit)XX
SUSE Linux Enterprise Server 11, SLES 11 SP1, 11
SP2 (32-/64-bit)
Oracle Enterprise Linux 5.0, 5.1, 5.2, 5.3, 5.4, 5.5,
5.6, 5.7, 5.8, 5.9 (32-/64-bit)
Oracle Enterprise Linux 6.0, 6.1, 6.2, 6.2, 6.3, 6.4
(32-/64-bit)
Ubuntu 10.04 (32-/64-bit)X
Ubuntu 12.04 (32-/64-bit)XX
Distributions not present in the above list are not supported. However, distributions that use the same installation
mechanism as Red Hat Enterprise Linux 5 (for example Fedora Core 6) might be successfully installed using the
same template.
XX
XX
XX
XX
Note:
Creating 32-bit Linux VMs on a host that has more than 128GB of memory is not supported.
15
5.1. Creating a Linux VM by Installing from an Internet Repository
This section shows the xe CLI procedure for creating a Linux VM, using a Debian Squeeze example, by installing
the OS from an internet repository.
Example: Installing a Debian Squeeze VM from a network repository
1.Create a VM from the Debian Squeeze template. The UUID of the VM is returned:
An example of a valid repository path is http://ftp.<xx>.debian.org/debian where <xx> is your
country code (see the Debian mirror list for a list of these). For multiple installations Citrix recommends using
a local mirror or apt proxy to avoid generating excessive network traffic or load on the central repositories.
Note:
The Debian installer supports only HTTP and FTP apt repos, NFS is NOT supported.
3.Find the UUID of the network that you want to connect to. For example, if it is the one attached to xenbr0:
xe network-list bridge=xenbr0 --minimal
4.Create a VIF to connect the new VM to this network:
6.Connect to the VM console using XenCenter or VNC and perform the OS installation.
5.3.1. Network Installation Notes
The XenServer guest installer allows you to install an operating system from a network-accessible ISO image onto
a VM. To prepare for installing from an ISO, make an exploded network repository of your vendor media (not ISO
images) and export it over NFS, HTTP or FTP so that it is accessible to the XenServer host administration interface.
See Appendix E, Setting Up a Red Hat Installation Server for information on how to copy a set of installation CDs
to a network drive.
17
Loading...
+ 54 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.