The Xen kernel runs on top of Linux kernel and is responsible for launching Dom0 default and first virtual machine , the only VM that interacts directly with the system hardware. The above command will install Xen server, Xen-kernel and virt-manager.
The Xen-server xend would have started by default. Because of this abstraction logical volumes can be created, deleted, resized and even snapshotted without affecting other logical volumes. LVM creates logical volumes within what is called a volume group, which is simply a set of logical volumes that share the same physical storage, known as physical volumes. The process of setting up LVM can be summarized as allocating a physical volume, creating a volume group on top of this, then creating logical volumes to store data.
Because of these features and superior performance over file backed virtual machines we recommend the use of LVM if you are going to store VM data locally. Ok, now LVM has somewhere to store its blocks known as extents for future reference. Now LVM is setup and initialized so that we can later create logical volumes for our virtual machines.
More on LVM on Debian here. If you already have a volume setup that you would like to copy, LVM has a cool feature that allows you to create a CoW copy on write clone called a snapshot. This means that you can make an "instant" copy that will only store the changes compared to the original.
There are a number of caveats to this that will be discussed in a yet unwritten article. The most important thing to note is that the "size" of the snapshot is only the amount of space allocated to store changes. So you can make the snapshot "size" a lot smaller than the source volume. Next we need to set up our system so that we can attach virtual machines to the external network. This is done by creating a virtual switch within dom0.
The switch will take packets from the virtual machines and forward them on to the physical network so they can see the internet and other machines on your network. The piece of software we use to do this is called the Linux bridge and its core components reside inside the Linux kernel. In this case, the bridge acts as our virtual switch. The Debian kernel is compiled with the Linux bridging module so all we need to do is install the control utilities:.
Management of the bridge is usually done using the brctl command. Open this file with the editor of your choice. If you selected a minimal installation, the nano text editor should already be installed. Open the file:. If you get nano: command not found , install it with apt-get install nano.
If you are using static addressing you probably know how to set that up. As well as adding the bridge stanza, be sure to change dhcp to manual in the iface eth0 inet manual line, so that IP Layer 3 is assigned to the bridge, not the interface.
Now restart networking for a remote machine, make sure you have a backup way to access the host if this fails :. If all is well, the bridge will be listed and your interface will appear in the interfaces column:. If the bridge isn't operating correctly, go back and check the edits to the interfaces file very carefully. Reboot before continuing. During the reboot, note the list of OS choices and check to see what the default start-up choice is.
If both the start-up default is fine, skip the next section and go directly to Basic Xen Project Commands. GRUB, the bootloader installed during installation, tells the computer which operating system to start and how. To use the hypervisor, Xen must be started before the operating system.
So, if Xen was, say, the third OS choice, change the line to. Before we dive into creating some guest domains we will quickly cover some basic commands. In the examples below, we use xl command line tool.
Older versions of the Xen Project software used the xm command line tool. If, for example, you come across "xm" while reading old documentation, say, just substitute "xl".
This can be used to visualize CPU, memory usage and block device access. Debian contains a number of tools for creating Xen Project guests, the easiest of which is known as xen-tools. In this guide we are going to use xen-tools to prepare a Debian paravirtualized domU.
This however is bad for maintainability guests cannot upgrade their kernels without access to the dom0 and is not as flexible in terms of boot options as they must be passed via the config file.
The Xen Project community wrote a utility known as pygrub which is a python application for PV guests that enables the dom0 to parse the GRUB configuration of the domU and extract its kernel, initrd and boot parameters.
This allows for kernel upgrades etc inside of our guest machines along with a GRUB menu. Using pygrub or the stub-dom implementation known as pv-grub is best practice for starting PV guests. We can now create a guest operating system with this tool. It effectively automates the process of setting up a PV guest from scratch right to the point of creating config files and starting the guest. The process can be summarized as follows:.
These 9 steps can be carried out manually but the manual process is outside the scope of this guide. We instead will execute the below command for --dist you could in place of Wheezy e. The installer presents the option to upgrade when it detects a previously installed version of Citrix Hypervisor. The upgrade process follows the first-time installation process, but several setup steps are bypassed.
The existing settings are retained, including networking configuration, system time and so on. You can install any required supplemental pack after installing Citrix Hypervisor. Download the supplemental pack filename. Throughout the installation, quickly advance to the next screen by pressing F Use Tab to move between elements and Space or Enter to select. Press F1 for general help. If necessary, see your hardware vendor documentation for information on changing the boot order.
Following the initial boot messages and the Welcome to Citrix Hypervisor screen, select your key map keyboard layout for the installation. If a System Hardware warning screen is displayed and hardware virtualization assist support is available on your system, see your hardware manufacturer for BIOS upgrades. Citrix Hypervisor ships with a broad driver set that supports most modern server hardware configurations.
However, if you have been provided with any additional essential device drivers, press F9. The installer steps you through installing the necessary drivers. Only update packages containing driver disks can be installed at this point in the installation process.
However, you are prompted later in the installation process to install any update packages containing supplemental packs.
Press F10 and follow the instructions displayed on the screen to set up FCoE. For information about configuring the physical switch and the array to support FCoE, see the documentation provided by the vendor. This issue is caused by a temporary link disruption in the host initialization phase. If the host fails to respond for a long time, you can restart the host to work around this issue.
Use the Page Up and Page Down keys to scroll through and read the agreement. Upgrade : If the installer detects a previously installed version of Citrix Hypervisor or XenServer, it offers the option to upgrade. For information about upgrading your Citrix Hypervisor server, see Upgrading from an existing version. Restore : If the installer detects a previously created backup installation, it offers the option to restore Citrix Hypervisor from the backup.
If you have multiple local hard disks, choose a Primary Disk for the installation. Select OK. Choose which disks you want to use for virtual machine storage. Information about a specific disk can be viewed by pressing F5.
If you want to use thin provisioning to optimize the use of available storage, select Enable thin provisioning. Citrix Virtual Desktops users are recommended to select this option for local caching to work properly. For more information, see Storage. If the computer has multiple NICs, select one of them to be used to access the Citrix Hypervisor installation media files. Choose OK to proceed. If you choose Static configuration , enter details as appropriate. Indicate if you want to verify the integrity of the installation media.
If you select Verify installation source , the SHA checksum of the packages is calculated and checked against the known value. Verification can take some time. Make your selection and choose OK to proceed. Set and confirm a root password, which XenCenter uses to connect to the Citrix Hypervisor server. If you select Manually specify , enter the hostname for the server in the field provided.
If you manually specify the hostname, enter a short hostname and not the fully qualified domain name FQDN. If you select Manually specify , enter the IP addresses of your primary required , secondary optional , and tertiary optional DNS servers in the fields provided. Select your time zone by geographical area and city. You can type the first letter of the desired locale to jump to the first entry that begins with this letter.
Specify how you want the server to determine local time: using NTP or manual time entry. Make your selection, and choose OK to proceed. The next screen asks if you want to install any supplemental packs. If you plan to install any supplemental packs provided by your hardware supplier, choose Yes.
If you choose to install supplemental packs, you are prompted to insert them. Eject the Citrix Hypervisor installation media, and insert the supplemental pack media. Choose OK. After the server reboots, Citrix Hypervisor displays xsconsole , a system configuration console. Make note of the IP address displayed.
0コメント