XenServer optimization

1.5 XenServer optimization

Principle 1.5.1 N + 1

Each physical machine pool at least 3, in line with the principle of N + 1

1.5.2 The principle of separation of the three networks

1) management network, service network, storage network phase separation

2) XenServer address configuration management, network and service phases were separated.

3) 6 NIC bindings do:

   Bond1 (NIC 1 + 4), for managing

  Bond2 (NIC 2 + 5), for traffic

  Bond3 (NIC 3 + 6), if the IP storage used; the HBA optical memory card is not used

1.5.3 hard disk optimization

1) Only hardware servers installed XenServer, do RAID1 hard disk or RAID 1/0

2) After the first delete the original configuration when RAID configuration, save, restart the configuration

3) If the hard drive previously installed VMWare or other operating systems, re-initialize into RAID10, and then restart to take effect configured to Raid1 or RAID1 / 0

4) use LVM format, enhance management flexibility

Installation uncheck thin provisioning (thin provisioning), that Local SR try to use LVM

n checked thin provisioning: Ext3 format after installation

n unchecked thin provisioning: LVM format after installation

n LVM: Logical Volume Manager (Logical Volume Manager ) shorthand, it is the Linux environment disk partitioning carried out a mechanism for managing, LVM is built on the hard disk and partition a logical layer to increase the flexibility of partition management .

1.5.4 BIOS optimization settings

1) Restore Default Settings

2) adjust the BIOS system clock

3) open the CPU virtualization support: Processor-> Virtulization Technology

4) Close CPU C-State: C-State saving CPU power is provided

5) Close CPU Turbo Mode: Turbo mode is the automatic overclocking CPU / down adjustment mode

6) Close Execute Lock Bit

7) IBM server is turned on Remote Console:

  【System Settings->Devices and I/O Ports->Console Redirection Settings->Remote Console】

8) IBM server add Legacy support:

  XenServer6.2 installation due to Unified Extensible Firmware Interface (UEFI) reason, Legacy support, otherwise it will cause an infinite restart

  Step a: System Settings-> Legacy Support> Infinite boot retry set to Enable

  Step two: BootManager-> Add BootOption-> Legacy Only, select it, Boot order to ensure the highest priority Legacy Only

9) Open the CPU Multi-Core: Multi-Thread Hyper-Threading Technology, opened Multi-Core double the number of vCPUs

  If the number of open Hyper-Threading vCPUs> 48, before installing XenServer Multi-Core = Disabled, after installation Open Multi-Core = Enabled

  Virtual Desktop project to open Multi-Core = Enabled

10) Close BIOS power settings:

    Some servers BIOS power setting is enabled by default, will reduce the power saving CPU frequency, is not applicable in XenServer

    Cancel power energy-saving settings set to maximum performance priority: BIOS Power Regulator for Maximum Performance

1.5.5 installation manually tune

1) What is the Dom0:

Dom0 running a virtual machine monitor and management of I / O privilege domain optimized Linux kernel, the configuration of the set XenServer dom0, allocation of more memory to dom0. This can enable a large amount of processing can XenServer virtual machine.

2) Why do we need a system partition expansion

Default [4G], optimized for [20G (20480)], can provide more log space.

After installing xenserver, the default system partition only 4G size, under normal circumstances is enough, but if time is running high density of virtual machines on a physical server, will produce more of the log, when the log is full accounts for space, may will produce a variety of problems, such as xapi dead and other services, you need to adjust the partition size to 20480 (20G).

3) adjust the dom0 vCPU

After XenServer5.6 FP1, Dom0 a multiple virtual (logical) control domain of the CPU, there will be 4 by default assigned to DomO vCPU, in the case where the number is less than 4, the number of vCPU DomO used by the actual physical CPU core decision. By default, the maximum vcpu in xenserver VM is 8, the maximum number of allocated vCPU give Dom0 also eight. In order to improve performance or provide stability, we may need to increase or decrease the number of vCPU Dom0;

4) Manual tuning

XenServer6.2 following versions require manual tuning, the following steps:

   When the installation start screen appears press [F2]

   Shell command input into single-user mode, waiting for the system to load

  Enter the command line vi /opt/xensource/installer/constants.py

  [Ins] key is inserted into the rewrite mode editable character; [x] command to delete the current character; [del] key to enter the command mode

  Disable GPT:

    GPT, UEFI partition in the case of certain server does not support, you need to use the MBR partition for installation.

    Find GPT_SUPPORT = TRUE, FALSE to TRUE revised to

  Adjust the default partition size is 20G (20480): store more log files

    Found ROOT_SIZE = 4096, 4096 to modify 10240 (10G) or 20480 (20G)

  Adjust the memory size to 2940MB:

    Find DOM0_MEM = 752, the 2940 revised to 752

  Adjust the number vCPUS:

    Find dom0_max_vcpus = 2

 Save and exit vi: press [del] to exit edit mode [ins] key, enter the command mode

Method 1: Continuous press twice uppercase [Z] key to save and exit vi;

Method 2:

a) Press ESC

b) Enter [:]

c) Enter wq [Enter] to complete the file is saved,

     Enter the exit command to exit the shell mode, start the installation system

1.5.6 Optimization XenDesktop Setup

  If you just do XenDesktop server application, check the "Enable thin provisioning (Optimize Storage for XenDesktop)" option, so you can make intelligent local disk caching capabilities, and can greatly improve the performance of XenDesktop system during the installation of XenServer.

1.5.7 Optimization card

  If the installation is completed after all cards have found physical packet loss or error, and slow network transmission, the need to modify the offload network adapter; offload NIC is dependent on the operating system, the offload network adapter xenserver virtual machines need to enter the system changes:

1 ) Windows Modify NIC offload configuration

Method 1: Access the [Local Area Connection] à choose the right card [configuration] button à select [Advanced] tab

[Device Manager] or [Network adapters] à à à [Property] [Senior]

   The verification data [] = Disable checksum Offload

  The Flow Control Flow Control [] = Disable

   The segment [IP] = Disable segmentation Offload

 Method 2: Modify the registry to disable TCP offload: offload

  (A) Run regedit, and then click OK.

  (B) Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ Tcpip \ Parameters

  (C) Click [Edit], point to [New], and then click DWORD] value.

  (D) Type DisableTaskOffload as the entry name, and then press ENTER.

  (E) Right-click DisableTaskOffload, and then click Modify.

  (F) the value in the Value data box, type 1, and then click OK.

  (Vii) Exit the Registry Editor.

  (Viii) to restart the computer.

2 ) Linux Offload modify the network card under

   Offload property View card information: ethtool -k eth0

  offload attribute information modification card: ethtool -K eth0 tx off

1.5.8 Storage Optimization

Enable multi-path storage support: XenCenter Check stored in multi-path] [Multipath

Reproduced in: https: //www.cnblogs.com/rongweifeng/p/Xenserver.html

Guess you like

Origin blog.csdn.net/weixin_33860147/article/details/94678048