Citrix Systems 6.1.0 manual Appendix C. PXE Boot Installations, To configure your Tftp server

Page 46

Appendix C. PXE Boot Installations

This appendix describes how to configure your PXE environment for XenServer installation. It steps through setting up your TFTP and NFS, FTP or HTTP servers to enable PXE booting of XenServer host installations. It then describes how to create an XML answer file, which allows you to perform unattended installations.

C.1. Configuring your PXE Environment for XenServer Installation

Before you set up the XenServer installation media, you need to configure your TFTP and DHCP servers. For general setup procedures, see the Citrix Knowledge Base article PXE Boot Environment: Generic TFTP and DHCP Configuration.

Note:

XenServer 6.0 moved from MBR disk partitioning to GUID Partition Table (GPT). Some third- party PXE deployment systems may attempt to read the partition table on a machine's hard disk before deploying the image to the host.

If the deployment system has not been updated to be compatible with GPT partitioning scheme, and the hard disk has previously been used for a version of XenServer (or any other Operating System) that uses GPT, the PXE deployment system may fail. If this happens, a workaround is to delete the partition table on the disk.

In addition to the TFTP and DHCP servers, you need an NFS, FTP, or HTTP server to house the XenServer installation files. These servers can co-exist on one, or be distributed across different servers on the network.

Additionally, each XenServer host that you want to PXE boot needs a PXE boot-enabled Ethernet card.

The following steps assume that the Linux server you are using has RPM support.

To configure your TFTP server:

1.In the /tftpboot directory, create a new directory called xenserver.

2.Copy the mboot.c32 and pxelinux.0 files from the /usr/lib/syslinux directory to the / tftboot directory.

Note:

Citrix strongly recommends using mboot.c32 and pxelinux.0 files from the same source (for example, from the same XenServer ISO).

3.From the XenServer installation media, copy the files install.img (from the root directory), vmlinuz and xen.gz (from the /boot directory) to the new /tftpboot/xenserver directory on the TFTP server.

4.In the /tftboot directory, create a new directory called pxelinux.cfg.

5.In the pxelinux.cfg directory, create your new configuration file called default.

The content of this file depends on how you want to configure your PXE boot environment. Two sample configurations are listed below. The first example configuration starts an installation on any machine that boots from the TFTP server and leaves you to manually respond to the installation prompts. The second performs an unattended installation.

Note:

The following examples show how to configure the installer to run on the physical console, tty0. To use a different default, ensure that the console you want to use is the rightmost.

41

Image 46
Contents Citrix XenServer 6.1.0 Installation Guide Trademarks Contents Using Scvmm and Scom with XenServer Boot From SAN Environments Welcome Benefits of Using XenServerAdministering XenServer About This DocumentNew Features in XenServer XenServer EditionsXenServer Documentation Guest EnhancementsReferences System Requirements System RequirementsXenServer Host System Requirements XenCenter System Requirements Supported Guest Operating SystemsInstalling XenServer and XenCenter Installation Media and MethodsInstalling the XenServer Host To install or upgrade the XenServer hostPage To install XenCenter Installing XenCenterHost Partition Format Connecting XenCenter to the XenServer Host To connect XenCenter to the XenServer hostXenServer Hosts with Local Storage Installation and Deployment ScenariosHigh-level procedure Basic hardware requirementsPools of XenServer Hosts with Shared Storage XenServer Hosts with Shared NFS StorageConfiguring your iSCSI storage XenServer Hosts with Shared iSCSI StorageConfiguring an iSCSI IQN for each XenServer host Xe pool-param-set uuid=pooluuid default-SR=iscsisharedsruuid XenServer and IntelliCache Enabling on Host InstallationIntelliCache Deployment To enable local caching, enter the following commands Converting an Existing Host to Use Thin ProvisioningVM Boot Behavior Implementation Details and TroubleshootingXe sr-list params=local-cache-sr,uuid,name-label How to install the Integration Suite Supplemental Pack Using Scvmm and Scom with XenServerIntegration Requirements for Scvmm Integration Requirements for Scom Rolling Pool Upgrades Upgrading XenServerPage Before You Upgrade Before you begin your rolling pool upgrade Upgrading XenServer Hosts Using the xe CLITo upgrade a pool of XenServer hosts using the xe CLI Upgrading a Single XenServer Host Using the xe CLI Before You Upgrade a Single XenServer HostTo empty the CD/DVD drive of a VM using the xe CLI Upgrading a Single XenServer Host Using the xe CLITo upgrade a single XenServer host using the xe CLI Page Upgrading LVM-based SRs using the xe CLI Upgrading LVM Storage from XenServer 5.0 or EarlierBefore You Apply an Update or Hotfix Applying Updates and Hotfixes to XenServerBefore you begin updating To update individual hosts using the xe CLI To update individual hosts using XenCenterUpdating Individual XenServer Hosts To update a pool of hosts using XenCenter Updating a Pool of XenServer HostsTo update a pool of XenServer hosts using the xe CLI Activating a Free XenServer Product Licensing XenServerTo activate a free XenServer product Licensing XenServer Editions To license XenServer Advanced editions and higherTo configure licensing for XenServer hosts using the xe CLI To configure licensing for XenServer hosts using XenCenterAdditional Licensing Information Grace Period Appendix A. Troubleshooting To capture and save the log fileAppendix B. Boot From SAN Environments Configuring your PXE Environment for XenServer Installation Appendix C. PXE Boot InstallationsTo configure your Tftp server Creating an answer file for unattended PXE installation Preparing the destination systemElement Description Required? Element Description Required? Element Proto dhcp or static