Categories
Interior

How to network boot (pxe) an automated installation of citrix xen

Have you ever wished your Hypervisor could be installed at the push of a button, without the tedious searching for the install CD and answering the same boring installation questions? HTG explains how to PXE an automated installation of Citrix-Xen.

Overview

We’ve shown you what is PXE and how you can easily install a server for it with FOG. In this guide, we will again extend on the excellent FOG foundation and add a menu entry to install an automated Citrix-Xen server.

Like in the Ubuntu live from FOG tutorial, the installation procedure isn’t purely PXE. It starts as PXE, as we provide the base “kernel”, “initial ram disk” (initrd) & other required files over PXE, but the rest of the procedure pulls the required files via HTTP.

This procedure is mentioned in the Citrix-Xen knowledge base/instillation guide, but isn’t really a copy & paste type of a recipe, like the one that we will try to give you today.

In general, the components to this guide will be:

  1. Make the install CD files available via HTTP.
  2. Create an automated answers file.
  3. Add the PXE files + menus entry.

Don’t worry, because we are building upon the FOG foundation, this will be easy…

Let’s get cracking.

Installation CD via HTTP

One of the nice things with building upon the FOG foundation is that we already have a web-server up and running and ready to serve the required installation files.

We will copy the installation files over and not “loopback mount” the ISO like we did in the Ubuntu guide, because we want to keep the option of slip-streaming supplemental packs into the installation process.

Create the directory that will hold the install files:

Copy the entirety of the install CD into this directory.

Note: you may create as many directories as you wish. For example, I’ve had a directory for every major version of Citrix-Xen since v5.0.

Automated answers file (Optional)

This stage is marked as optional, because you may wish to not automate the installation. If you opt to not automate the procedure, you will have to answer the installation questions on your own with one noticeable difference: when prompted for the installation source, you would have to choose “HTTP” instead of “local media” and provide the address manually.

Just to keep the option of having the install CD mounted as a loopback device, we will put the answer file in the root of the webserver.

Create the answer-file by issuing:

Make its content look like:

Where you would need to change the “timezone”, “root-password and “source url” to suit your requirements.

PXE Files

As mentioned in the overview, we need some files from the install CD to be available in our TFTP directory.

To do this, create the TFTP directory that will hold the files by issuing:

mkdir -p /tftpboot/howtogeek/xenserver/xen61

Copy the files from the CD or the www directory by issuing:

cp -av /var/www/xenserver61/boot/xen.gz /tftpboot/howtogeek/xenserver/xen61/
cp -av /var/www/xenserver61/boot/vmlinuz /tftpboot/howtogeek/xenserver/xen61/
cp -av /var/www/xenserver61/install.img /tftpboot/howtogeek/xenserver/xen61/
cp -av /var/www/xenserver61/boot/pxelinux/mboot.c32 /tftpboot/howtogeek/xenserver/xen61/

Note: The last file we copied, the “mboot.c32” module, needs to be compatible with your FOG’s version of PXElinux, If it isn’t, the boot procedure will fail. The module is easily obtainable from the Syslinux package.

PXE Menus

In the original FOG guide, we’ve hinted that we may be adding sub-directories in the future and have left a “template” menu file just for that. Let’s spawn another menu by copying the template file:

cp -av /tftpboot/howtogeek/menus/template.cfg /tftpboot/howtogeek/menus/xen.cfg

Edit it by issuing:

Append to its content to include the below:

label Citrix XenServer 6.1
#MENU DEFAULT
#MENU PASSWD
kernel xenserver/xen61/mboot.c32
append howtogeek/xenserver/xen61/xen.gz dom0_max_vcpus=4 dom0_mem=1024M console=vga — howtogeek/xenserver/xen61/vmlinuz xencons=hvc console=hvc0 console=tty0 answerfile=http://192.f.o.g/xen-answerfile-61 install — howtogeek/xenserver/xen61/install.img

Where you would have to edit the IP to get the answer file to be your FOG’s IP.

Note: The “DEFAULT” and “PASSWD” directives are commented out because they don’t suit every situation. With that said, consider enabling them, because installing an OS could be really destructive if users get their hands on it…

Now add to the default menu entry, the newly created menu by issuing:

Append to its content to include the below:

Applicable Products

  • XenServer 6.1.0
  • XenServer 6.2.0

Objective

This article describes how to perform automated installation of XenServer 6.1. This procedure works also with the earlier versions of XenServer.

This article is based on and in some details extends to the data available in “Citrix XenServer ® 6.1.0 Installation Guide” Appendix C. PXE Boot Installations.

Environment

Physical server dedicated for XenServer 6.1 hypervisor.

Physical server or virtual machine dedicated for Dynamic Host Configuration Protocol (DHCP), Trivial File Transfer Protocol (TFTP), and HTTP services, (in this article it refers to infrastructure server).

DHCP server installation and configuration. Ensure to avoid conflict with existing running DHCP service.

Network File Share (NFS) server or any NAS with NFS available.

Following is the diagram of environment:

Instructions

Complete the following procedures to install XenServer 6.1:

Installing Infrastructure Server

Linux Debian 6 can be chosen as the system for infrastructure server.
Install base system and enable SSH access. No other configurations are required.

Installing and Configuring XenServer Network Installation Repository

There are three types of supported installation repositories for XenServer – HTTP, FTP, and NFS. Here, HTTP can be chosen as the installation repository because it is popular and easy to configure.

Complete the following procedure for installing and configuring the installation repository:

Install lighttpd server. This HTTP server is very easy to configure and has minimal resource requirement, what makes it perfect for our demonstration purpose.
aptitude install lighttpd
insserv –default lighttpd

/etc/init.d/lighttpd start
By default configuration lighttpd serves content from /var/www directory. Create a dedicated subdirectory and copy the entire contents of the XenServer installation CD to the newly created directory.
mount /dev/xvdd /media/
mkdir -pv /var/www/xenserver/
cp -rv /media/* /var/www/xenserver/

Verify the new HTTP repository. Though it is not mandatory, it is strongly recommended to verify the repository.

Edit /etc/lighttpd/lighttpd.conf file and add the following line at the end of the file:
dir-listing.activate = “enable”

Restart the HTTP server by using the following command:
/etc/init.d/lighttpd restart

Using web browser, navigate to the new XenServer installation repository.

XenServer installation repository is ready to use. Note the URL of newly created HTTP repository.

Installing PXE Environment for XenServer Installation

Unattended network installation requires working DHCP, TFTP services. Here the basic setup and the basic configuration of these services are explained.

For purpose of this article Linux dnsmasq server has been selected as a provider for DHCP and TFTP. The main advantage of this choice is that Linux dnsmasq can provide both DHCP and TFTP so there is no need to have separate daemons for every service.

Complete the following procedure:

Install base Linux system on your infrastructure server. Linux Debian 6 (64 bit) can be chosen as an example

Install all required components, dnsmasq server, syslinux PXE bootstrap files, and TFTP client for troubleshooting and testing purposes.
aptitude install dnsmasq tftp syslinux
insserv –default dnsmasq
/etc/init.d/dnsmasq start

Prepare directories and boot files to be served from TFTP. At this point TFTP service has not started functioning. Directory /srv/tftp/xenserver contain all necessary files.
mkdir -p /srv/tftp/xenserver
cp -v /usr/lib/syslinux/mboot.c32 /usr/lib/syslinux/pxelinux.0 /srv/tftp/xenserver/

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 /srv/tftp/xenserver directory on the TFTP server.
mount /dev/xvdd /media/
cp -v /media/install.img /srv/tftp/xenserver/
cp -v /media/boot/ /srv/tftp/xenserver/

Create a backup for /etc/dnsmasq.conf file and edit it as the following:
domain-needed
filterwin2k
interface=eth1
dhcp-range=192.168.5.50,192.168.5.99,2h
dhcp-option=option:router,192.168.5.2
dhcp-option=option:netmask,255.255.255.0
dhcp-option=option:dns-server,192.168.5.4
dhcp-option=option:domain-name,pxeinstall.example.xyz
dhcp-option=option:ntp-server,192.168.5.4
dhcp-option=option:tftp-server,192.168.5.4
dhcp-option=option:bootfile-name,xenserver/pxelinux.0
enable-tftp
tftp-root=/srv/tftp/
log-queries
log-dhcp
Note
: The preceding example is fully functional minimal set of options required for PXE(Preboot Execution Environment).
This configuration has been made on the following assumptions:
network address 192.168.5.0/24
Interface eth1 is use for DHCP and TFTP
eth1 IP address is 192.168.5.4
TFTP root directory is /srv/tftp/

Verify the newly created TFTP server. Though it is not mandatory, verification is strongly recommended. Successful verification result displays the following:

Creating New PXE Configuration

Complete the following procedure for creating new PXE configuration:

Create a directory for PXE configuration file.
mkdir -p /srv/tftp/xenserver/pxelinux.cfg/

Create and edit default PXE config file /srv/tftp/xenserver/pxelinux.cfg/default
Example:

default xenserver
label xenserver
kernel mboot.c32
append xen.gz noreboot com1=115200,8n1 console=com1,vga — vmlinuz xencons=hvc console=hvc0 console=tty0 — install.img

Troubleshooting

Complete the following procedure for troubleshooting:

Check if DHCP server is working, by deploying to the same network any other DHCP client.

Check if TFTP service is available, by referring the step 6,of Installing PXE Environment for XenServer Installation

Check if installation repository is available, by referring the step 3, of Installing and Configuring XenServer Network Installation Repository.

Refer step 5 of Installing PXE Environment for XenServer Installation for configuring of dnsmasq server. This enables logging to syslog.
The following is an example for a successful PXE boot:

Відео: Citrix XenServer Master Class – XenServer 101 (Липень 2022).

Ви коли-небудь хотіли, щоб ваш гіпервізор був встановлений одним натисненням кнопки, без нудного пошуку встановлювального компакт-диска і відповіді на ті ж нудні питання установки? HTG пояснює, як PXE – це автоматизована установка Citrix-Xen.

Фото: Рожева фотографія Шербета через Compfight cc

Огляд

Ми показали вам, що таке PXE і як ви легко можете встановити для нього сервер за допомогою FOG. У цьому посібнику ми знову поширимося на чудову основу FOG і додамо пункт меню для встановлення автоматизованого сервера Citrix-Xen.

Як і в Ubuntu в реальному часі з підручника FOG, процедура встановлення не є чисто PXE. Починається як PXE, оскільки ми надаємо базове «ядро», «початковий диск» (initrd) та інші необхідні файли через PXE, але решта процедури тягне потрібні файли через

Ця процедура згадується в базі знань Citrix-Xen / керівництві з інстиляції, але насправді це не тип копіювання та вставки рецепту, як той, який ми спробуємо дати вам сьогодні.

Загалом, компоненти цього посібника будуть такими:

  1. Зробіть доступні файли встановлених компакт-дисків через
  2. Створіть файл автоматизованих відповідей.
  3. Додайте запис PXE + меню.

Не хвилюйтеся, тому що ми будуємо фундамент FOG, це буде легко …

Інсталяційний компакт-диск через

Одна з приємних речей, пов’язаних із створенням фундації FOG, полягає в тому, що ми вже маємо веб-сервер і готовий обслуговувати необхідні інсталяційні файли.

Ми будемо копіювати інсталяційні файли, а не “закріплювати” ISO, як це робилося в керівництві Ubuntu, тому що ми хочемо зберегти опцію додаткових пакунків з потоковим потоком у процесі встановлення.

Створіть каталог, у якому будуть розміщені файли встановлення:

mkdir -p / var / www / xenserver61 /

Скопіюйте весь інсталяційний компакт-диск у цей каталог.

Примітка: ви можете створити стільки каталогів, скільки бажаєте. Наприклад, у мене є каталог для всіх основних версій Citrix-Xen з версії 5.0.

Файл автоматизованих відповідей (необов’язково)

Цей етап позначено як необов’язковий, оскільки ви можете не автоматизувати інсталяцію. Якщо ви вирішили не автоматизувати процедуру, вам доведеться самостійно відповісти на запитання щодо встановлення з однією помітною різницею: коли вам буде запропоновано джерело інсталяції, вам доведеться вибрати “HTTP” замість “місцеві носії” і вказати адресу вручну.

Щоб зберегти опцію встановлення встановленого компакт-диска у вигляді пристрою для зворотного зв’язку, ми розмістимо файл відповідей у ​​кореневій папці веб-сервера.

Створіть файл відповідей:

nano / var / www / xen-answerfile-61

Bạn đã bao giờ ước Hypervisor của bạn có thể được cài đặt chỉ bằng cách ấn nút, mà không cần tìm kiếm CD cài đặt và trả lời các câu hỏi cài đặt nhàm chán tương tự? HTG giải thích cách PXE cài đặt tự động Citrix-Xen.

Tín dụng hình ảnh: Pink Sherbet Photography qua Compfight cc

Tổng quan

Chúng tôi đã chỉ cho bạn PXE là gì và cách bạn có thể dễ dàng cài đặt máy chủ cho nó với FOG. Trong hướng dẫn này, một lần nữa chúng tôi sẽ mở rộng trên nền tảng FOG tuyệt vời và thêm một mục menu để cài đặt máy chủ Citrix-Xen tự động.

Giống như trong Ubuntu trực tiếp từ hướng dẫn FOG, quy trình cài đặt không hoàn toàn là PXE. Nó bắt đầu là PXE, khi chúng tôi cung cấp cơ sở dữ liệu cơ sở dữ liệu, đĩa ram ban đầu, dữ liệu ram ban đầu (initrd) và các tệp cần thiết khác qua PXE, nhưng phần còn lại của quy trình kéo các tệp cần thiết qua HTTP.

Quy trình này được đề cập trong hướng dẫn cơ sở / thấm nhuần kiến ​​thức Citrix-Xen, nhưng thực sự không phải là một loại bản sao và dán của một công thức, giống như công thức mà chúng tôi sẽ cố gắng cung cấp cho bạn ngày hôm nay.

Nói chung, các thành phần của hướng dẫn này sẽ là:

  1. Cung cấp các tệp CD cài đặt có sẵn qua HTTP.
  2. Tạo một tệp trả lời tự động.
  3. Thêm tập tin PXE + mục menu.

Đừng lo lắng, vì chúng tôi đang xây dựng trên nền tảng FOG, điều này sẽ dễ dàng

Chúng ta hãy nứt.

CD cài đặt qua HTTP

Một trong những điều tuyệt vời khi xây dựng trên nền tảng FOG là chúng tôi đã có một máy chủ web hoạt động và sẵn sàng phục vụ các tệp cài đặt cần thiết.

Chúng tôi sẽ sao chép các tệp cài đặt qua chứ không phải là loopback mount mount ISO như chúng tôi đã làm trong hướng dẫn Ubuntu, vì chúng tôi muốn giữ tùy chọn gói bổ sung trượt trực tuyến vào quá trình cài đặt.

Tạo thư mục chứa các tệp cài đặt:

mkdir -p / var / www / xenserver61 /

Sao chép toàn bộ đĩa CD cài đặt vào thư mục này.

Lưu ý: bạn có thể tạo nhiều thư mục như bạn muốn. Ví dụ: tôi đã có một thư mục cho mọi phiên bản chính của Citrix-Xen kể từ phiên bản 5.0.

Tệp trả lời tự động (Tùy chọn)

Giai đoạn này được đánh dấu là tùy chọn, vì bạn có thể không muốn tự động cài đặt. Nếu bạn chọn không tự động hóa quy trình, bạn sẽ phải tự trả lời các câu hỏi cài đặt với một điểm khác biệt đáng chú ý: khi được nhắc về nguồn cài đặt, bạn sẽ phải chọn HTTP HTTP HTTP thay vì phương tiện truyền thông địa phương và cung cấp địa chỉ thủ công.

Chỉ cần giữ tùy chọn cài đặt CD cài đặt như một thiết bị loopback, chúng tôi sẽ đặt tệp trả lời vào thư mục gốc của máy chủ web.

Tạo tệp trả lời bằng cách phát hành:

nano / var / www / xen-answerfile-61

Làm cho nội dung của nó trông giống như:

sda
chúng tôi
mật khẩu
http: //192.f.o.g/xenserver61/
192.n.t.p

Trường hợp bạn cần thay đổi múi giờ của chanh, mật khẩu gốc và mật khẩu url mã nguồn phù hợp với yêu cầu của bạn.

Tập tin PXE

Như đã đề cập trong phần tổng quan, chúng tôi cần một số tệp từ đĩa CD cài đặt có sẵn trong thư mục TFTP của chúng tôi.

Để thực hiện việc này, hãy tạo thư mục TFTP sẽ giữ các tệp bằng cách phát hành:

mkdir -p / tftpboot / howtogeek / xenserver / xen61

Sao chép các tệp từ đĩa CD hoặc thư mục www bằng cách phát hành:

cp -av /var/www/xenserver61/boot/xen.gz / tftpboot / howtogeek / xenserver / xen61 /
cp -av / var / www / xenserver61 / boot / vmlinuz / tftpboot / howtogeek / xenserver / xen61 /
cp -av /var/www/xenserver61/install.img / tftpboot / howtogeek / xenserver / xen61 /
cp -av /var/www/xenserver61/boot/pxelinux/mboot.c32 / tftpboot / howtogeek / xenserver / xen61 /

Lưu ý: Tệp cuối cùng mà chúng tôi đã sao chép, mô-đun của mboot.c32, cần phải tương thích với phiên bản PXElinux của FOG, nếu không, quy trình khởi động sẽ thất bại. Mô-đun có thể dễ dàng lấy được từ gói Syslinux.

Thực đơn PXE

Trong hướng dẫn FOG ban đầu, chúng tôi đã gợi ý rằng chúng tôi có thể sẽ thêm các thư mục con trong tương lai và đã để lại một tệp menu kiểu mẫu của Cameron chỉ cho điều đó. Hãy sinh ra một menu khác bằng cách sao chép tệp mẫu:

cp -av /tftpboot/howtogeek/menus/template.cfg /tftpboot/howtogeek/menus/xen.cfg

Chỉnh sửa nó bằng cách phát hành:

Nối vào nội dung của nó để bao gồm những điều dưới đây:

nhãn Citrix XenServer 6.1
#MENU DEFAULT
#MENU PASSWD
nhân xenserver / xen61 / mboot.c32
chắp thêm howtogeek / xenserver / xen61 / xen.gz dom0_max_vcpus = 4 dom0_mem = 1024M console = vga — howtogeek / xenserver / xen61 / vmlinuz xencons = hvc console = hvc0 console = tty0 answerfile-61 cài đặt — howtogeek / xenserver / xen61 / install.img

Nơi bạn sẽ phải chỉnh sửa IP để lấy tệp trả lời thành IP của FOG của bạn.

Lưu ý: Các chỉ thị của DE DEULTULT và PASSWD ‘được bình luận bởi vì chúng không phù hợp với mọi tình huống. Như đã nói, hãy cân nhắc việc kích hoạt chúng, bởi vì việc cài đặt một hệ điều hành có thể thực sự phá hoại nếu người dùng chạm tay vào nó.

Bây giờ thêm vào mục menu mặc định, menu vừa tạo bằng cách phát hành:

Nối vào nội dung của nó để bao gồm những điều dưới đây:

Xen
DANH MỤC Xen
KernEL vesamothy.c32
PHỤ LỤC howtogeek / menu / xen.cfg

Lưu ý: Vị trí, trong trường hợp này, vấn đề. Tôi đề nghị bạn không đặt nó bên dưới nhãn sương mù.localocal.

Thế là xong, bạn nên cài đặt Thưởng thức 🙂

Содержание

  • 1 PXE Install Server for XenServer
    • 1.1 Why do I need this?
    • 1.2 Ingredients
    • 1.3 On your Ubuntu 11.10 machine
      • 1.3.1 Install the following packages
      • 1.3.2 Edit /etc/network/interfaces
      • 1.3.3 Edit /etc/dhcp/dhcpd.conf and add the following
      • 1.3.4 tftpboot
      • 1.3.5 pxelinux.cfg/default
      • 1.3.6 Edit /var/lib/tftpboot/pxelinux.cfg/default and paste the following
      • 1.3.7 The Answer File
      • 1.3.8 Copy packages* and XS-REPOSITORY-LIST to your webserver
      • 1.3.9 Start services
    • 1.4 Ready to run
  • 2 Further Reading

Why do I need this?

If you choose to use XenServer as the hypervisor for your OpenStack deployment, you probably want the install to be automatic. At Citrix, we find it useful to have a PXE server around, even in a simple development environment. It makes it much easier to start automating tests later on.

Ingredients

This guide was written using:

However, it should be equally applicable to modern versions of both XenServer and Ubuntu.

On your Ubuntu 11.10 machine

Install the following packages

Edit /etc/network/interfaces

The interface eth1 on my machine is on a network called “Network 1”. Please change the instructions below to match your network setup.

Caution: Ensure that your “Network 1” is isolated from any corporate network, to avoid any interference from our DHCP, PXE server.

Edit /etc/dhcp/dhcpd.conf and add the following

tftpboot

Mount the iso you downloaded and copy over the following to your /var/lib/tftpboot folder:

pxelinux.cfg/default

First you need to add the menu UI file handler.

Edit /var/lib/tftpboot/pxelinux.cfg/default and paste the following

The Answer File

You may use the sample answerfile below. This must be placed in /var/www/answerfile.

Copy packages* and XS-REPOSITORY-LIST to your webserver

Start services

Ready to run

On your target machine, ensure that boot sequence is set to boot from network. Reboot your machine. Ensure it acquires a DHCP address from your PXE server. At the boot prompt, enter install-xenserver and take a deep breath.

Ви коли-небудь хотіли, щоб ваш гіпервізор був встановлений одним натисненням кнопки, без нудного пошуку встановлювального компакт-диска і відповіді на ті ж нудні питання установки? HTG пояснює, як PXE – це автоматизована установка Citrix-Xen.

Фото: Рожева фотографія Шербета через Compfight cc

Огляд

Ми показали вам, що таке PXE і як можна легко встановити сервер для нього за допомогою FOG. У цьому посібнику ми знову поширимося на чудову основу FOG і додамо пункт меню для встановлення автоматизованого сервера Citrix-Xen.

Як і в Ubuntu в реальному часі з підручника FOG, процедура встановлення не є чисто PXE. Починається як PXE, оскільки ми надаємо базове “ядро”, “початковий диск” (initrd) та інші необхідні файли через PXE, але решта процедури тягне потрібні файли через HTTP.

Ця процедура згадується в базі знань Citrix-Xen / керівництві інстиляцій, але насправді не є копією та вставкою рецепту, подібно до того, що ми спробуємо дати вам сьогодні.

Загалом, компоненти цього посібника будуть такими:

  1. Зробіть доступні файли встановлених компакт-дисків через HTTP.
  2. Створіть файл автоматизованих відповідей.
  3. Додайте запис PXE + меню.

Не хвилюйтеся, адже ми будуємо фундамент FOG, це буде легко .

Інсталяційний компакт-диск через HTTP

Одна з приємних речей, пов’язаних із створенням фонду FOG, полягає в тому, що ми вже маємо веб-сервер і готовий обслуговувати необхідні інсталяційні файли.

Ми будемо копіювати інсталяційні файли, а не “loopback mount” ISO, як це робилося в керівництві Ubuntu, тому що ми хочемо зберегти опцію додаткових пакунків для ковзання в процесі установки..

Створіть каталог, у якому будуть розміщені файли встановлення:

mkdir -p / var / www / xenserver61 /

Скопіюйте весь інсталяційний компакт-диск у цей каталог.

Примітка: ви можете створити стільки каталогів, скільки бажаєте. Наприклад, у мене була директорія для всіх основних версій Citrix-Xen з версії 5.0.

Файл автоматизованих відповідей (необов’язково)

Цей етап позначено як необов’язковий, оскільки ви можете не автоматизувати інсталяцію. Якщо ви вирішили не автоматизувати процедуру, вам доведеться самостійно відповісти на запитання щодо встановлення з однією помітною різницею: коли вам буде запропоновано джерело інсталяції, вам доведеться вибрати “HTTP” замість “місцеві носії” і вказати адресу вручну.

Щоб зберегти опцію встановлення встановленого компакт-диска у вигляді пристрою для зворотного зв’язку, ми розмістимо файл відповідей у ​​кореневій папці веб-сервера.

Створіть файл відповідей:

nano / var / www / xen-answerfile-61

Зробіть його вміст таким:

Де потрібно змінити “часовий пояс”, “кореневий пароль” і “вихідний URL” відповідно до ваших вимог.

Файли PXE

Як згадувалося в огляді, нам потрібно, щоб деякі файли з інсталяційного компакт-диска були доступні в каталозі TFTP.

Для цього створіть каталог TFTP, в якому будуть зберігатися файли, видавши:

mkdir -p / tftpboot / howtogeek / xenserver / xen61

Скопіюйте файли з компакт-диска або каталогу www, видавши:

cp -av /var/www/xenserver61/boot/xen.gz / tftpboot / howtogeek / xenserver / xen61 /
cp -av / var / www / xenserver61 / boot / vmlinuz / tftpboot / howtogeek / xenserver / xen61 /
cp -av /var/www/xenserver61/install.img / tftpboot / howtogeek / xenserver / xen61 /
cp -av /var/www/xenserver61/boot/pxelinux/mboot.c32 / tftpboot / howtogeek / xenserver / xen61 /

Примітка: Останній файл, який ми скопіювали, модуль “mboot.c32”, повинен бути сумісним з версією PXElinux вашого FOG, якщо це не так, процедура завантаження не вдасться. Модуль можна легко отримати з пакета Syslinux.

Меню PXE

У оригінальному посібнику FOG, ми натякнули, що ми можемо додавати підкаталоги в майбутньому і залишили файл шаблону меню тільки для цього. Давайте створимо інше меню, скопіювавши файл шаблону:

cp -av /tftpboot/howtogeek/menus/template.cfg /tftpboot/howtogeek/menus/xen.cfg

Відредагуйте його, видавши:

Додайте до його вмісту, щоб включити нижче:

етикетку Citrix XenServer 6.1
#MENU DEFAULT
#MENU PASSWD
ядро xenserver / xen61 / mboot.c32
додати howtogeek / xenserver / xen61 / xen.gz dom0_max_vcpus = 4 dom0_mem = 1024M консоль = vga — howtogeek / xenserver / xen61 / vmlinuz xencons = hvc console = hvc0 console = tty0 answerfile = http: //192.fog/xen- answerfile-61 встановити — howtogeek / xenserver / xen61 / install.img

Де б вам не довелося редагувати IP, щоб отримати файл відповідей, щоб бути вашим FOG’s IP.

Примітка: Директиви “DEFAULT” і “PASSWD” прокоментовані, оскільки вони не відповідають кожній ситуації. З урахуванням сказаного, розглянути можливість їх використання, тому що встановлення ОС може бути дійсно руйнівним, якщо користувач отримає свої руки .

Тепер додайте до меню за замовчуванням, щойно створене меню, видавши:

Додайте до його вмісту, щоб включити нижче:

LABEL Xen
ЕТИКЕТ МЕНЮ Xen
KERNEL vesamenu.c32
APPEND howtogeek / меню / xen.cfg

Примітка: Розташування, в даному випадку, має значення. Я пропоную вам не ставити його нижче позначки “fog.local”.

Ось і все, ви повинні бути все налаштовані . Насолоджуйтесь 🙂

Applicable Products

  • XenServer 7.0

Objective

Instructions

1. Place the bootable media into the system that XenServer should be installed. If the bootable media creation step was successful, the system should display the XenServer splash screen.

2. From this screen, simply hit enter to boot into the installer. The first screen, once the installer has started successfully, will ask the user to select their language.

Select XenServer-7 Installation Language

3. The next screen will ask the user to confirm that an upgrade or install should be done as well as ask for any other special drivers that may need to be loaded in order to install XenServer.

XenServer 7 Install or Upgrade Setup

4. The next screen is the obligatory EULA (End User License Agreement). Use the keyboard arrows to move the cursor to the ‘Accept EULA‘ button.

XenServer 7 Accept License

5. This is where the installation can take one of two paths if the installer detects a prior install. The next screen will prompt the user for a clean install or an upgrade to an existing XenServer install. The first set of instructions here will walk through a clean install. If an upgrade is needed skip ahead to step 15.

XenServer 7 Install or Upgrade Selection

6. The next screen will prompt for the installation device. In this case it will be ‘sda’.

Select XenServer 7 Installation Drive

7. Once the installation path has been chosen, XenServer will need to know where the installation files reside. In this case, the installer was booted from local media and that is the option that should be chosen.

Select XenServer 7 Installation Source

8. The next step will allow the user to install supplemental packs at the same time as this installer. At the time of this writing, there aren’t any supplemental packs for XenServer 7 so ‘no’ can be selected here.

Select XenServer 7 Supplemental Packs

9. The next screen will allow the user to confirm the integrity of the source files before installing. Running this test is not required but can help detect installation issues before trying to write files.

Verify XenServer 7 Installation Source

10. Once the verification is completed, if selected during install, the XenServer installer will ask the user to setup some system information.

The first prompt will be to set the root user’s password. Now, since XenServer will be the underlying system to potentially several important virtualized servers, it is imperative that the password be secured as well as sufficiently complex!

Important: Do not forget this password either as there will not be any other users on the system once the installer finishes!

Set XenServer 7 Root Password

11. The next couple of steps will ask how the management network interface should be configured (Static address or DHCP) as well as hostname and DNS information. This will be dependent on the environment.

Select XenServer 7 Networking

Set XenServer 7 Hostname and DNS

12. This step covers several screens for setting time zone information and NTP (Network Time Protocol).

Select XenServer 7 Timezone

Set XenServer System Time

Configure NTP for XenServer 7

13. At this point in the installer, all of the initial configuration information for a clean install has been provided and the installer is ready to install all the necessary files.

WARNING – Continuing at this point WILL ERASE ALL DATA on the target disks!

I wanted to write about automating a Citrix Hypervisor aka XenServer installation for a long time but never had the time to put all the information together. If you are looking for a guide how to silent install a XenServer with the latest updates and NVIDIA vGPU driver you came to the right place. This deployment is only working with XenServer 7.1 and later. Citrix changed the hotfix format from ‘.xsupdate’ to ‘.ISO’. If there should be any reason for deploying XenServer 7.0 (EOL – May 2021) feel free to edit the provided bash script.

Table of Contents

General

Before installing and configuring the needed components we need to understand the procedure for an unattended installation.

  1. Server is powered on
  2. Server is getting an ip address from a DHCP server with PXE boot information
  3. PXELINUX is started and a boot menu is presented (TFTP)
  4. Citrix Hypervisor base installation is triggered with an answer configuration file (FTP)
  5. After the first boot of the server a post script action is triggered

This is a screenshot of the the PXELinux boot menu.

Now lets get started with setting up the deployment server. Im using a Windows Server 2019 machine in my environment but it could be any other Windows Server release. There is no need to join the machine to a domain it can be member of a local workgroup. Its up to you.

Please download the following sources:

Setup the DHCP Server

The first thing we need to do is to install the DHCP server role and configure a scope for our deployment network. Im using the subnet 192.168.2.0/24 and the ip address of my deployment server is 192.168.2.149.

PVS and MCS are designed for delivery of the gold image, they are not a replacement for automating the creation of that image. What’s going to happen in those environments where the gold image has been built manually and it either needs to be recreated or the delivery mechanism needs to be changed? That manual image has become a black box that will be difficult to reverse engineer.

My Automation Framework 3.0 was released last week, but unfornatly it doesn’t have support for Windows 10. The reason is that Microsoft have not yet released Microsoft Deployment Toolkit 2013 Update 1 (ETA August 2015) which will fully support Windows 10 deployments.

Now, while I wait for that I have some time to test the upcoming Citrix Provisioning Services 7.7 Tech Preview and something called Base Image Script Framework (BIS-F).

I was tipped about BISF at Citrix Synergy / E2EVC 2015 by Jonathan Pitre which is a customer and a big fan of the Automation Framework.

Like the amazing App-V Scheduler replaced my custom App-V Powershell script, I wanted to support BISF in my Automation Framework because it’s way more powerful, feature rich and has much better logging. Let’s get started!

First of, there’s a big bug with licensing so you need to install the Citrix Licensing Server on the Citrix Provisioning Server 7.7 itself. Thanks to Carl Webster for pointing that out.

在本教程中,我们将指导您如何通过PXE服务器安装最新版本的Debian 9服务器,并使用Debian归档镜像提供的Internet远程HTTP镜像源。 我们将在本教程中使用的DHCP服务器设置PXE环境为ISC-DHCP服务器,netboot Debian文件将由TFTPD-HPA服务器在本地网络上提供。 通过PXE安装系统可以提高安装速度,以及在短时间内部署多个Debian安装的情况下,或者在机器未配备CD / DVD ROM单元的情况下。

  • Debian 9安装在裸机或虚拟机上。
  • 为网段配置静态IP地址的网络接口,用于动态分配IP地址和其他相关的DHCP和PXE设置。
  • 具有root权限的本地或远程帐户到Debian服务器,或通过服务器控制台直接访问root帐户或通过SSH远程访问。
  • 需要通过网络安装Debian的互联网连接。

为了手动配置您的网络接口卡,打开网络接口文件并使用您喜欢的文本编辑器(如nano)编辑以下行。 替换下面介绍的IP设置行以匹配您自己的网络配置。

sudo nano /etc/network/interfaces

接口文件摘录:

apt install wget bash-completion unzip

安装并配置ISC-DHCP服务器

为了设置DHCP服务器和PXE配置,请使用root帐户或具有root权限的帐户登录系统,并通过发出以下命令安装Debian 9存储库提供的isc-dhcp-server软件包。

apt install isc-dhcp-server

mv /etc/dhcp/dhcpd.conf /etc/dhcp/dhcpd.conf.backup

dhcpcd.conf文件摘录:

选项路由器 =设置您的网关IP

选项broadcast-address =设置你的网络广播地址

选项subnet-mask =设置您的网络子网掩码地址

选项ntp-servers

选项time-servers =设置您的网络NTP服务器IP地址

选项domain-name =设置你的网络域名,如果有的话

选项domain-name-servers =设置您的网络DNS服务器IP地址

如果选项arch = 00:07或选项arch = 00:09 =如果最终设备是基于UEFI的计算机,请使用bootnetx64.efi文件启动设备,或使用不是基于UEFI的任何其他计算机启动pxelinux.0文件。 这些机器通常是较旧的BIOS系统。

next-server 192.168.1.102 =这是TFTP服务器的IP地址,可以在网络中找到文件pxelinux.0bootnetx64.efi 。 在这种情况下,TFTP服务器位于同一台机器上。

default-lease-time =默认授予IP地址的时间,以秒为单位。

max-lease-time =授予IP地址的最大时间,以秒为单位。

这是如何在DHCP服务器中声明一个静态IP地址。 具有由硬件以太网语句定义的MAC地址的设备将始终获得相同的IP地址。 声明的主机名不重要。 您可以使用任何字符串作为主机名。

然后打开/ etc / default /目录下的 isc-dhcp-server文件进行编辑,导航到文件末尾,并将配置了静态IP地址的网络接口卡添加到IPv4接口行,如下面的示例所述。 确保您添加适当的网络接口卡名称。 使用ipifconfig命令列出您的机器网络接口并找到正确的名称。

systemctl restart isc-dhcp-server.service

systemctl status isc-dhcp-server.service

另外,执行ssnetstat命令列出所有由DHCP服务器打开的套接字。

如果系统中未安装netstat实用程序,请发出以下命令进行安装。

apt install net-tools

安装TFTP服务器

为了提供客户端通过PXE和TFTP远程启动Debian所需的网络文件,您还需要在系统中安装一个TFTP服务器。 tftpd-hpa服务器是可用于局域网的最常见和安全的TFTP服务器之一。 TFTP-HPA软件包可以从Debian 9提供的官方软件库中安装。执行以下命令在Debian 9中安装tftpd-hpa服务器。

apt install tftpd-hpa

tftpd-hpa文件摘录:

如果TFTP_OPTIONS行有以下内容,请确保删除–create标志以保护TFTP服务器。

创建标志允许远程客户端上传文件到tftp服务器。 此选项是危险的,因为任意用户可以从TFTP服务器根路径上载或删除文件。

systemctl enable tftpd-hpa

systemctl start tftpd-hpa

systemctl status tftpd-hpa

您还应该执行netstatss命令,以便列出系统中所有处于监听状态的开放网络套接字。 DHCP和TFTP服务器所需的以下UDP端口应该在您的网络中打开:67和69.您应该通过发出以下命令在防火墙中打开这些端口:

ufw allow 67/udp

ufw allow 69/udp

如果您使用iptables原始规则管理Debian服务器中的防火墙策略,请添加以下规则,以允许端口67和69 UDP入站流量通过防火墙,以便客户端可以访问DHCP和TFTP服务器。

apt-get install iptables-persistent

iptables -A INPUT -p udp –dport 67 -j ACCEPT

iptables -A INPUT -p udp –dport 69 -j ACCEPT

systemctl iptables-persistent save

systemctl iptables-persistent reload

apt install syslinux-utils syslinux

部署Debian 9 Netboot文件

接下来,进入Debian netinstall网页 https://www.debian.org/distrib/netinst 并使用wget命令行工具下载最新版本的Debian netboot archive tarball。

下载Debian netinstall tarball之后,通过运行以下命令将归档内容直接提取到TFTP根路径。

tar xfz netboot.tar.gz -C /srv/tftp/

同时将Syslinux软件包提供的memdisk文件复制到TFTP根路径,并通过执行以下命令列出TFTP目录的内容。 / srv / tftp目录的内容应该如下图所示。

cp /usr/lib/syslinux/memdisk /srv/tftp/

接下来,通过发出以下命令为Debian netinstall软件包提供的UEFI引导加载程序文件创建一个符号链接到TFTP根路径。 此外,请长时间列出TFTP目录以查看软链接是否正确指向UEFI网络文件。

ln -s /srv/tftp/debian-installer/amd64/bootnetx64.efi /srv/tftp/

PXE服务器按以下顺序从TFTP根路径读取并执行位于pxelinux.cfg目录中的配置文件:GUID文件,MAC文件和默认文件。 目录pxelinux.cfg已经创建并填充了所需的PXE默认配置文件,因为我们之前已经将所需的netboot文件从Debian netinstall归档文件解压到/ srv / tftp sirectory。 没有必要从pxelinux.cfg目录进一步修改PXE默认配置文件。 但是,实际控制Debian的初始引导菜单的文件名为txt.cfg ,位于/ srv / tftp / debian-installer / amd64 / boot-screens /目录中。 pxelinux.cfg中的默认pxe配置文件 目录实际上是一个指向txt.cfg文件的软链接。 为了在网络启动过程中更改或添加其他选项以传递给内核,或者通过PXE服务器添加其他条目或启动其他Linux发行版,您应该使用以下命令打开默认的txt.cfg PXE配置文件,并使适当的变化。

t xt.cfg 文件摘录:

另外,通过检查这个文件的内容,你会发现在初始PXE菜单之后,通过TFTP网络协议加载到客户端RAM内存的内核initrd.gz映像位于/ srv / tftp / debian卸载器/ AMD64 / 目录。 您只能更改这两个文件,以便将来更新Debian内核和initrd.gz。

就这样! 现在可以通过网络启动客户机,使用通过DVD映像启动Debian时显示的所有条目,并开始通过PXE服务器安装Debian 9。

为了看到在客户端和服务器之间实时交换的DHCP日志消息,使用tail命令对系统日志文件。 DHCP服务器将其所有日志消息丢弃到系统日志文件。 可以通过daemon.log文件观察TFTP服务器日志消息。 以下屏幕截图显示了由DHCP和TFTP服务器发布的日志消息的摘录。

journalctl -fu tftpd-hpa

要显示有关DHCP服务器授予其客户端的租约的扩展信息,请使用cat命令显示dhcpd.leases文件的内容,如下例所示。

就这样! 您已经在网络中成功部署了PXE服务器。 您现在可以通过指示客户机通过PXE启动来开始在网络上安装Debian。 在机器POST初始化期间,您可以通过按特殊功能键来联网启动客户机。 请查阅您的机器主板供应商文档以找出正确的网络启动密钥。

Contents

  1. Installation Citrix Xen Server
  2. Here are the steps in images:
  3. Locate the file you you downloaded
  4. Choose a pool, or accept the default (next):
  5. Choose a storage location for the VM:
  6. Choose the network to connect the VM to:
  7. All finished!
  8. Login to the VM Console:
  9. Configure a static IP address:
  10. Change the default credentials for the VM

Installation Citrix Xen Server

Once you download the virtual appliance file, take following steps:

  1. Use 7zip to unzip the downloaded file.
  2. From XenCenter, Right Click on server > Import
  3. Choose Source
  4. Choose Server
  5. Choose Storage
  6. Choose the network card and Finish.
  7. Once powered on, go to the console, choose option 1 to configure networking [Please use a STATIC IP for all production Device42 Installations to avoid connectivity issues]. Default login for console is device42 and default password is adm!nd42 (NOTE: Use (ubuntu/default) for the power appliance). You can change the password using option 10.
  8. Go to https://New_IP or add the IP of the new VM to DNS (recommended) and go via dns(https://FQDN(Fully Qualified Domain Name)).
  9. The default credential is admin/adm!nd42this password should be changed once you login.

Here are the steps in images:

Locate the file you you downloaded

Choose a pool, or accept the default (next):

Choose a storage location for the VM:

Choose the network to connect the VM to:

All finished!

Login to the VM Console:

Default username: device42
Default password: adm!nd42
(NOTE: Use credentials (ubuntu/default) for the power appliance)
(NOTE: Much Older <32bit, unsupported>versions may have the default login “ubuntu” rather than “device42”. If you have an appliance that uses these credentials, UPGRADE it if at all possible!)

You can change the password with option 10 below.

Configure a static IP address:

Use this option to configure an IP address for the Device42 appliance.

Change the default credentials for the VM

The default password for user device42 can now be changed from the console menu using option# 10. The default username/password is admin/adm!nd42. Please be sure to change it after you login.

You can apply updates and do other menu-related work using ssh. Please note that root login has been disabled via ssh.

Last, point your browser to the address at the top of the console menu and you’re ready to go…

WINDOWS 7 GOLD IMAGE FOR XENDESKTOP
Citrix XenDesktop 7.6 Citrix Studio Configure New Site, discusses XenDesktop Site and creating a hosting connection to VMware vSphere using the SDK (Software Development Kit). The underlying platform VMware vSphere consists of VMware vCenter Server and VMware ESX(i).

This article assumes the following prerequisites;

  1. Citrix XenDesktop 7.6 Core Software Install
  2. Citrix XenDesktop 7.6 VMware SDK Certificate
  3. Citrix XenDesktop 7.6 Citrix Studio Configure New Site
  4. Citrix XenDesktop 7.6 Citrix Studio Configure VMware Connection
  5. Business applications installed in XenApp
  6. Latest version of Citrix StoreFront installed
  7. Latest version of Citrix Receiver deployed as required by Citrix StoreFront versioning
  8. Latest Virtual Desktop Agent (VDA) installed to correspond with XenApp Site Controller versioning

Now that we have a XenDesktop proof-of-concept site and connection to vSphere the next step is the creation of the gold image for Windows 7. The proof-of-concept image is Windows 7 32 Bit. This is a standard VMWare VMDK file format which is best suited for Citrix Machine Creation Services (MCS). This procedure can work for Citrix Provisioning Server by adding an additional step to reverse-image the virtual machine to VHD format then running the Citrix Provisioning Server Optimization tool.

This section uses vCenter and vSphere client to build a clean Windows 7 image with no hardware dependencies and create a master or gold image to use in XenDesktop for MCS or PVS.

First, log in to the vSphere server and create a Windows 7 image from scratch. This image, VMDK, will become the “Gold Image” for Citrix Machine Creation Services.

VM Version
Virtual Machine Version 8

CPUs
A number of virtual sockets translates to the number of virtual processors (sockets) followed by the number of “cores.”
ASSIGN MEMORY – 4 GB
As this is a 32-bit operating system 4GB is the maximum. We will use Machine Creation Services (MCS) to create multiple clones of this image after installing the Citrix Client and VDA Software.

ONE NIC – WORKSTATION VDI NETWORK
Take care to define a Virtual Desktop Infrastructure network ID. The proof-of-concept is the time to start the discussion with Network Engineering on some of the requirements in case this progresses to Pilot and then Production. We use MCS because it does not require PXE Boot, TFTP or custom DHCP options.
NIC TO VMXNET3 AND CHECK POWER ON
This is the correct driver to use with Citrix. Don’t forget to check “Connect at power on.”
NEXT

CHANGE TO LSI LOGIC PARALLEL
This has to do with my choice of storage/hardware platform. This will differ depending on hardware options, but this is a common option.
CREATE NEW VIRTUAL DISK
Create a new virtual disk for purposes of installing Windows 7 32 or 64-bit operating system. For now, we just need a base operating system, the latest service pack and the latest patches.

Allocate storage to the new C: Drive, 30 GB and choose THICK PROVISION LAZY ZEROED. The VDI image is a conduit for XenApp published applications. All the applications reside in XenApp. The drive is large enough to allow for current and future OS patching. We have no plans to install any applications other than Citrix Receiver and the VMware software.

This should be SCSI 0

This assumes the Windows 7 ISO is copied to a datastore. Click CD/Drive 1 > Select “Datastore ISO File” > Click “Browse. ” > Locate the Windows 7 Installation ISO > Check the box “Connected” > Check the box “Connect at power on” > Click OK

Choose “Custom” and choose ALL options. Install all components and APIs.
Click “Install.”
Click “Yes” to reboot.
SUMMARY
Citrix is a conduit for the business application. Citrix XenApp is installed on a Windows server designed to host centralized applications on shared systems. Citrix XenDesktop provides;

  • Virtual Windows Desktops – Client or server
  • A centralized conduit to business applications hosted in Citrix XenApp
  • Access to servers and workstations internal of FMA versus RDP

This image will become the “cloned” image that Machine Creation Services uses to spin up virtual desktops. No business applications are installed to the desktop image. Citrix XenApp is the preferred platform for hosting business applications.

Citrix MCS is designed for a dedicated and shared pool scenario with 25 users or less. It is generally faster to set up in regard to proof-of-concept and has no relationship to Citrix Provisioning Services.

Machine Creation and Provisioning Services work with VMware ESX, XenServer and Hyper-V hypervisor. Citrix Provisioning Services requires other infrastructure components such as TFTP and PXE among others.

ACKNOWLEDGEMENT
Does this shared knowledge provide value? If this article has value, please click on “Good Article” button to your right. Knowing this knowledge is valued by others is motivation to continue sharing. Your support is greatly appreciated.

Basics

Scripted builds for Xenserver 6.2 is outlined in http://support.citrix.com/servlet/KbServlet/download/34970-102-706044/installation.pdf. Xenserver build scripts run in the bash shell so are a bit more flexible than in ESXi. The following scripts allow for host specific dynamic zero touch builds – mainly for larger environments but can be used for any number of hosts.

PXE boot process

The PXE boot process for Xenserver builds is as follows:

  1. Host is PXE booted from pxelinux.cfg menu, each host specific menu entry specifies host specific XML answer file.
  2. Host specific XML answer file specifies hostname and post build script.
  3. Post build script preloads actual build script, patches and drivers as well as host specific configuration file.
  4. Upon reboot build script configures host.

I.e. for each host we require a XML answer file and a host configuration file.

The menu config for Xenserver 6.2 is as follows:

Answer file

The answer file specifies (see install guide for all options):

  • Install location
  • Keyboard mapping
  • Install file location
  • Root password
  • Post install script
  • NIC used during installation
  • Timezone
  • Hostname

As most things are configured by the actual build script later on the main things required here is the hostname – which is required to download the host specific configuration file during the post install phase, as well as the path / location to the post install script itself. The format of the answer file is as follows:

Post install script

The post install script runs with the newly installed root filesystem mounted as /tmp/root/root/. The script prepopulates the filesystem as follows:

  • Downloads host specific answer file based on hostname.
  • Downloads (but does not yet install) patches. These are simply packaged up in a .tgz file containing all *.xsupdate files required installed.
  • Downloads hardware specific drivers based on dmidecode return.
  • Tweaks the boot splash screen during install to highlight the build process is still ongoing.
  • Downloads the build script to /etc/init.d and configures this to run as a service on reboot.
  • Reboots the host.

Host config files

The host configuration file can take any format – ideally something like XML, JSON, YAML, etc – as long as this can be parsed. Using any of these would allow for easier integration with CMDB backends.

In this case I’ve just used standard shell script variable assignment – the advantage being the variables can easily be read with a “source” or “.” include statement. The host configuration files can also be easily knocked up in large quantities with some simple shell scripting or an Excel macro.

The format for the template file is as follows – all relatively self explanatory:

Or a complete example – in this case knocked up for a CloudStack compute node installation:

Main build script

The main build script follows fairly standard format for linux /etc/init.d scripts, in this case it will run under run level 3 with priority 99. This script will kick off on first reboot following the post script run, and configure the host according to the host configuration file .cfg. All build actions are logged in

Citrix VM Tools 9.2.1 is crashing my VDAs. At random VDAs suddenly drop their network connection and lose connectivity with PVS and crash. It happens on different hypervisors (XenServer 8.2) but not on all machines at the same time so it’s no hardware issue.

Reverting back to 9.1.5 resolves the problem. I wonder if Citrix is aware of the issue and if it will be fixed.

Share this post

Link to post

7 answers to this question

  • Sort by votes
  • Sort by date

7 Replies

Recommended Posts

Please sign in to comment

You will be able to leave a comment after signing in

Welcome to the Citrix Discussions. Our site does not support outdated browser (or earlier) versions. To use our site, please take one of the following actions:

  • Upgrade your version of Internet Explorer. You can find more information here
  • Install the Google browser. You can find more information here
  • Install the Firefox browser. You can find more information here

Thank you,
The Citrix Discussions Team.

Need more help?

PRODUCT ISSUES

LICENSING, RENEWAL, OR GENERAL ACCOUNT ISSUES

OTHER SUPPORT OPTIONS

  • Citrix Product Documentation
  • Citrix Knowledge Center
  • FAQs
  • View Support numbers

HOW CAN WE HELP?

Share this page

© 1999 – 2022 Citrix Systems, Inc. All Rights Reserved.

本教程将指导您如何添加Ubuntu 14.10服务器,Ubuntu 14.04服务器和Debian 7 Wheezy发行版到PXE网络启动环境设置

本教程将指导您如何到Ubuntu 14.10服务器 ,Ubuntu的14.04服务器Debian 7Wheezy分布添加到PXE网络引导环境安装在RHEL / CentOS 7。

虽然本教程的目的,我将只演示了如何添加64位网络安装映像,同样的程序也可以适用于Ubuntu或Debian的32位或其它架构的图像。 此外,添加Ubuntu 32位源的过程将解释,但在我的前提下没有配置。

从PXE服务器安装UbuntuDebian的要求,您的客户机必须有一个有效的Internet连接,最好是通过NAT配置了DHCP动态地址分配,以便安装拉所需的软件包,并完成安装过程。

第1步:将Ubuntu 14.10和Ubuntu 14.04服务器添加到PXE菜单

1.添加网络安装源的Ubuntu 14.10Ubuntu 14.04到PXE菜单可以通过两种方式实现:一是通过下载的Ubuntu光盘ISO映像,并以访问Ubuntu的网络启动文件,将其安装PXE服务器的机器上,另一种是由直接下载Ubuntu Netboot存档并解压到系统上。 另外,我将讨论这两种方法:

使用Ubuntu 14.10和Ubuntu 14.04 CD ISO映像

为了使用此方法,您的PXE服务器需要一个功能CD / DVD驱动器。 在任意计算机上访问的Ubuntu 14.10下载和Ubuntu的14.04下载页面,抢在64位服务器安装映像 ,它刻录到CD,将CD映像PXE服务器DVD / CD驱动器,并使用它安装在系统上以下命令。

如果您的PXE服务器计算机没有CD / DVD驱动器,你可以下载的Ubuntu 14.10Ubuntu 14.04 ISO映像本地使用wget命令行并发出以下命令将其安装在服务器上的同上述路径(下载并安装CD) 。

在Ubuntu 14.10
在Ubuntu 14.04

使用Ubuntu 14.10和Ubuntu 14.04 Netboot镜像

对于这种方法用下面的命令下载Ubuntu的启动镜像到PXE服务器上。

在Ubuntu 14.04
在Ubuntu 14.04

对于其他处理器架构,请访问以下位置的Ubuntu 14.10和Ubuntu 14.04 Netboot官方页面,并选择您的架构类型并下载所需的文件。

2.你下载后,ISO映像网络启动安装程序归档发出取决于您选择的方法如下命令复制整个Ubuntu的安装文件夹复制到PXE TFTP服务器的位置。

A)。 对于这两种光盘ISO映像(32位 或64位 ),使用以下命令你安装的具体架构上的CD PXE服务器的/ mnt系统路径之后。

B)。 对于Netboot存档,根据特定的Ubuntu体系结构运行以下命令。

如果你想使用PXE服务器,先下载两个Ubuntu的服务器架构,安装或提取物,视情况而定,32位架构和复制Ubuntu的安装目录到/ var / lib中的/ tftpboot,然后卸载CD或删除和netboot归档和提取的文件和文件夹,重复使用64位架构相同的步骤,从而使最终TFTP路径应具有以下结构。

3.在下一步通过发出以下命令添加了Ubuntu 14.10Ubuntu 14.04菜单标签PXE服务器默认的配置文件。

重要提示 :这不是我能够显示双方的Ubuntu版本的说明,这对演示用途的原因,我添加的Ubuntu 14.04菜单标签,可以PXE服务器,但同样的下面的说明也适用于Ubuntu的14.10,只有轻微的变化到版本号,只需根据您的Ubuntu发行版更改版本号和到OS体系结构的路径。

对于Ubuntu 14.04 32位
对于Ubuntu 14.04 64位

注 :如果您想包括其他Ubuntu的架构,遵循同样的上述说明,并相应地对PXE默认菜单配置文件替换标签号码和Ubuntu的安装/ $ architecture_name /目录。

4.在配置PXE菜单配置文件,清理取决于所用方法的来源和使用客户端安装PXE进行测试配置。