The download file is an ISO image called XenServer-6.0.0-install-cd.iso. Its a 509 MB file, so it might take a while.
After downloading the ISO, burn a CD/DVD and pop it in the DVD tray of the server and restart the server. Please ensure that the first boot device is the DVD drive so that after restart the server boots from the CD/DVD.
This is the screen we see when we boot from the CD/DVD
Enter the keyboard information
XenServer installation is about to start – Please note that all data on the disk selected for the XenServer installation will be deleted
Accept the EULA
Select the primary disk where the XenServer will be installed
Select the disk where VMs will be stored – We choose the same disk as the one where the XenSever is installed for storage of VMs. We will change it later in XenCenter
Selected the installation source – We choose ‘Local Media’
Select if you want to install Supplemental Packs – We choose ‘No’
Verify Installation Source – We choose to ‘Skip Verification’
Set Password – Type and then retype the root password
Networking – Choose which of the network interface you want to use for connecting to the management server
Networking – Choose whether you wish to use DHCP or enter static configuration. We use static configuration with
IP Address – 10.0.0.32
Subnet Mask – 255.255.255.0
Gateway – 10.0.0.1
Hostname and DNS – Enter the name of the server and DNS server – We choose to name the server as ‘xenserver-1′ and the DNS the same as the gatweay i.e. 10.0.0.1
Time settings – Choose which geographical area you are located in – We choose ‘Asia’
Then select the city nearest to you – We choose ‘Calcutta’
System Time – Choose whether you will manually enter the time or use NTP – We choose ‘Manual Time entry’
Confirm Installation – If all the setup information you have entered is correct, choose to ‘Install XenServer’. Again note that XenServer installation will delete all data on the disk where it is being installed.
Enter the local date and time
You should see this XenServer configuration screen after the server restarts
XenServer is a bare metal hypervisor. We will use XenCenter running on a Windows PC to manage our server ‘xenserver-1′. You can download Citrix XenCenter from here
First, start XenCenter
Click on ‘Add a server’ and a dialog box will appear
Enter the IP address, username and password of the server you wish to add to XenCenter.
Server : 10.0.0.32 (this is IP address we gave during installation)
User name : root
Password : ******* (this is the root password we entered during installation)
XenCenter adds the server ‘xenserver-1′. Now we can use XenCenter to manage the server on which we installed XenServer.
The live migration process moves a running VM from the source physical host to a destination physical host as quickly as possible. A live migration is initiated by an administrator through one of the methods listed below. The speed of the process is partially dependent on the hardware used for the source and destination physical computers, as well as the network capacity.
Three methods can initiate a live migration:
Any guest operating system supported by Hyper-V will work with the live migration process.
After initiating a live migration, the following process occurs:
1. Live migration setup
During the live migration setup stage , the source physical host creates a TCP connection with the destination physical host. This connection transfers the VM configuration data to the destination physical host. A skeleton VM is set up on the destination physical host and memory is allocated to the destination VM.
2. Memory pages are transferred from the source node to the destination node
In the second stage of a live migration, the memory assigned to the migrating VM is copied over the network to the destination physical host. This memory is referred to as the working set of the migrating VM. A page of memory is 4 kilobytes.
For example, suppose that a VM named SERVER2 configured with 1024MB of RAM is migrating to another Hyper-V physical host. The entire 1024MB of RAM assigned to this VM is the working set of SERVER2. The utilized pages within the SERVER2 working set are copied to the destination Hyper-V physical computer.
In addition to copying the working set of SERVER2 to the destination physical host, Hyper-V on the source physical host monitors the pages in the working set for SERVER2. As memory pages are modified by SERVER2, they are tracked and marked as being modified. The list of modified pages is simply the list of memory pages SERVER2 has modified after the copy of its working set has begun.
During this phase of the migration, the migrating VM continues to run. Hyper-V iterates the memory copy process several times, each time a smaller number of modified pages will need to be copied to the destination physical computer.
After the working set is copied to the destination physical host, the next stage of the live migration begins.
3. Memory pages transferred
Stage three is a memory copy process that duplicates the remaining modified memory pages for SERVER2 to the destination physical host. The source physical host transfers the register and device state of the VM to the destination physical host.
During this stage, the network bandwidth available between the source and destination physical hosts is critical to the speed of the live migration and using a 1 Gigabit Ethernet or faster is important. The faster the source physical host transfers the modified pages from the migrating VMs working set, the more quickly the live migration will complete.
The number of pages transferred in this stage is dictated by how actively the VM is accessing and modifying memory pages. The more modified pages, the longer the VM migration process takes for all pages to be transferred to the destination physical host.
After the modified memory pages are copied completely to the destination physical host, the destination physical host has an up-to-date working set for SERVER2. The working set for SERVER2 is present on the destination physical host in the exact state it was in when SERVER2 began the migration process.
Note: You can cancel the live migration process at any point before this stage of the migration.
4. Move the storage handle from source to destination
During the fourth stage of a live migration, control of the storage associated with SERVER2, such as any VHD files or pass-through disks, is transferred to the destination physical host.
5. The VM is brought online on the destination server
In stage five of a live migration, the destination server now has the up-to-date working set for SERVER2 as well as access to any storage used by SERVER2. At this point SERVER2 is resumed.
6. Network cleanup occurs
The migrated VM is running on the destination server in the final stage of a live migration. At this point a message is sent to the physical network switch causes it to re-learn the MAC addresses of the migrated VM so that network traffic to and from SERVER2 can use the correct switch port.