Book/HelloXenProject/3-Chapter: Difference between revisions

From Xen
Jump to navigationJump to search
(Created page with "== Chapter 3: == == Dom(s) and Grub == Welcome to Chapter 3. We want to speak about Dom0 and DomU. I'm sure that currently you know what...")
 
(→‎Chapter 3: Dom(s) and Grub: Prettified Option Description)
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Chapter 3: ==
= Chapter 3: Dom(s) and Grub =

== Dom(s) and Grub ==






































Welcome to Chapter 3. We want to speak about Dom0 and DomU. I'm sure that currently you know what is Xen Domain but we want to speak about it more.
Welcome to Chapter 3. We want to speak about Dom0 and DomU. I'm sure that currently you know what is Xen Domain but we want to speak about it more.
Line 45: Line 7:
If DomU wants share hardware, then Dom0 must give it an interface for make requests for access to the hardware. This is done via Backend Driver. For access to the Hardware that shared between Domains, DomU must contact to Dom0. The Front-end Driver prepared for the OS in DomU and use XenBus, XenStore, Shared Pages and... for communicating with Backend Driver. I just want to tell you that “XenStore” is an information storage space that shred between domains and maintained by the Xenstored. The XenBus provides a bus abstraction for Paravirtualized drivers to communicate between domains.
If DomU wants share hardware, then Dom0 must give it an interface for make requests for access to the hardware. This is done via Backend Driver. For access to the Hardware that shared between Domains, DomU must contact to Dom0. The Front-end Driver prepared for the OS in DomU and use XenBus, XenStore, Shared Pages and... for communicating with Backend Driver. I just want to tell you that “XenStore” is an information storage space that shred between domains and maintained by the Xenstored. The XenBus provides a bus abstraction for Paravirtualized drivers to communicate between domains.


For more information about “XenStore” and “XenBus” Please see “http://wiki.xenproject.org/wiki/XenStore” and “http://wiki.xenproject.org/wiki/XenBus”.
For more information about “XenStore” and “XenBus” Please see [[XenStore]] and [[XenBus]].


In below Figure, You can see a cute photo about Dom0 and DomU :
In below Figure, You can see a cute photo about Dom0 and DomU :


[[Image:Figure_16-_DomU_and_Dom0.png|top|600px|none|thumb|Figure 16 : DomU and Dom0.]]

<div style="text-align:center;">[[Image:Figure_16-_DomU_and_Dom0.png|top|600px|none|thumb]]</div>

===== <span style="color:#00000a;">Figure 16 : DomU and Dom0.=====


I guess you are impatiently waiting for how you can configure Dom0 and DomU. The dome is used for configuration our Guest OS and we will configure it in the next chapter but we will Play with Dom0 here. I know that your thinking, that we want to hack Dom0 here, but your wrong, We just want to show you a way to manipulate:
I guess you are impatiently waiting for how you can configure Dom0 and DomU. The dome is used for configuration our Guest OS and we will configure it in the next chapter but we will Play with Dom0 here. I know that your thinking, that we want to hack Dom0 here, but your wrong, We just want to show you a way to manipulate:
Line 61: Line 20:
For change memory setting you must open /etc/default/grub with an editor like “nano” and apply your Arbitrary settings :
For change memory setting you must open /etc/default/grub with an editor like “nano” and apply your Arbitrary settings :


<syntaxhighlight lang="sh">
[root@localhost ~]# cat /etc/default/grub
[root@localhost ~]# cat /etc/default/grub


Line 76: Line 36:


GRUB_DISABLE_RECOVERY="true"
GRUB_DISABLE_RECOVERY="true"
</syntaxhighlight>



Find “GRUB_CMDLINE_LINUX” and add “dom0_mem=512M, max: 512M” at the end of this line. After it, Your Dom0 will use 512 megabyte memory and “max” parameter means the maximum memory usage:
Find “GRUB_CMDLINE_LINUX” and add “dom0_mem=512M, max: 512M” at the end of this line. After it, Your Dom0 will use 512 megabyte memory and “max” parameter means the maximum memory usage:


<syntaxhighlight lang="sh">

[root@localhost ~]# cat /etc/default/grub
[root@localhost ~]# cat /etc/default/grub


Line 96: Line 56:


GRUB_DISABLE_RECOVERY="true"
GRUB_DISABLE_RECOVERY="true"
</syntaxhighlight>



Then you must run “grub2-mkconfig -o /boot/grub2/grub.cfg” and reboot your system. After it, The Dom0 will use 512 Megabyte of memory. You can use B for bytes, K for kilobytes, M for megabytes, or G for gigabytes.
Then you must run “grub2-mkconfig -o /boot/grub2/grub.cfg” and reboot your system. After it, The Dom0 will use 512 Megabyte of memory. You can use B for bytes, K for kilobytes, M for megabytes, or G for gigabytes.
Line 104: Line 64:
Open “/etc/xen/xl.conf” file and find “#autoballoon="auto"” then remove “#” and change “auto” to “0”. After it, the “xl” can't adjust the amount of memory assigned to dom0 :
Open “/etc/xen/xl.conf” file and find “#autoballoon="auto"” then remove “#” and change “auto” to “0”. After it, the “xl” can't adjust the amount of memory assigned to dom0 :


<syntaxhighlight lang="sh">
[root@localhost ~]# cat /etc/xen/xl.conf
[root@localhost ~]# cat /etc/xen/xl.conf


<nowiki>## Global XL config file ##</nowiki>
## Global XL config file ##


<nowiki># Control whether dom0 is ballooned down when xen doesn't have enough</nowiki>

<nowiki># free memory to create a domain. </nowiki>"auto" means only balloon if dom0

<nowiki># starts with all the host's memory.</nowiki>

<nowiki>#autoballoon="auto"</nowiki>


# Control whether dom0 is ballooned down when xen doesn't have enough
# free memory to create a domain. "auto" means only balloon if dom0
# starts with all the host's memory.


#autoballoon="auto"
<nowiki># full path of the lockfile used by xl during domain creation</nowiki>


# full path of the lockfile used by xl during domain creation
<nowiki>#lockfile="/var/lock/xl"</nowiki>
#lockfile="/var/lock/xl"


...
...
</syntaxhighlight>




Change :
Change :


<syntaxhighlight lang="sh">
[root@localhost ~]# cat /etc/xen/xl.conf
[root@localhost ~]# cat /etc/xen/xl.conf


<nowiki>## Global XL config file ##</nowiki>
## Global XL config file ##


# Control whether dom0 is ballooned down when xen doesn't have enough

# free memory to create a domain. "auto" means only balloon if dom0
<nowiki># Control whether dom0 is ballooned down when xen doesn't have enough</nowiki>
# starts with all the host's memory.

<nowiki># free memory to create a domain. </nowiki>"auto" means only balloon if dom0

<nowiki># starts with all the host's memory.</nowiki>


autoballoon="0"
autoballoon="0"


# full path of the lockfile used by xl during domain creation


#lockfile="/var/lock/xl"
<nowiki># full path of the lockfile used by xl during domain creation</nowiki>

<nowiki>#lockfile="/var/lock/xl"</nowiki>


...
...
</syntaxhighlight>



You may ask yourself, Why you must dedicate the fixed amount of memory for Dom0. It is a good idea because :
You may ask yourself, Why you must dedicate the fixed amount of memory for Dom0. It is a good idea because :


●The Linux Kernel calculates various network parameters at the boot time and based on this memory.
* The Linux Kernel calculates various network parameters at the boot time and based on this memory.


●For store the memory metadata, The Linux need some amount of memory and this feature based on the memory on the boot time.
* For store the memory metadata, The Linux need some amount of memory and this feature based on the memory on the boot time.


For more information about “Ballooned”, Please look at “https://blog.xenproject.org/2014/02/14/ballooning-rebooting-and-the-feature-youve-never-heard-of/” and “http://xenbits.xen.org/people/liuw/xen-balloon-driver-improvement.pdf”.
For more information about “Ballooned”, Please look at “https://blog.xenproject.org/2014/02/14/ballooning-rebooting-and-the-feature-youve-never-heard-of/” and “http://xenbits.xen.org/people/liuw/xen-balloon-driver-improvement.pdf”.
Line 161: Line 115:
To dedicate “vcpu” to Dom0 you must use “dom0_max_vcpus=X” option and “X” is the number of vcpu that you need. You must open “grub.conf” via an editor like “nano” and add above option to it :
To dedicate “vcpu” to Dom0 you must use “dom0_max_vcpus=X” option and “X” is the number of vcpu that you need. You must open “grub.conf” via an editor like “nano” and add above option to it :


<syntaxhighlight lang="sh">

<nowiki># cat /etc/default/grub</nowiki>
# cat /etc/default/grub


GRUB_TIMEOUT=5
GRUB_TIMEOUT=5
Line 177: Line 131:


GRUB_DISABLE_RECOVERY="true"
GRUB_DISABLE_RECOVERY="true"
</syntaxhighlight>



As you see, I dedicated two VCPUs to my Dom0.
As you see, I dedicated two VCPUs to my Dom0.
Line 183: Line 137:
Let me guess your question! I guess you are thinking about dedicate a CPU core to Dom0. Am I right? I must tell you that you can. It is possible and sometime is a good idea and guarantee that Dom0 always has Free CPU time and can process the I/O requests from DomUs. For doing it, You must use “ dom0_max_vcpus=X dom0_vcpus_pin” option in your “grub.conf” file :
Let me guess your question! I guess you are thinking about dedicate a CPU core to Dom0. Am I right? I must tell you that you can. It is possible and sometime is a good idea and guarantee that Dom0 always has Free CPU time and can process the I/O requests from DomUs. For doing it, You must use “ dom0_max_vcpus=X dom0_vcpus_pin” option in your “grub.conf” file :


<syntaxhighlight lang="sh">
<nowiki># cat /etc/default/grub</nowiki>
# cat /etc/default/grub


GRUB_TIMEOUT=5
GRUB_TIMEOUT=5
Line 198: Line 153:


GRUB_DISABLE_RECOVERY="true"
GRUB_DISABLE_RECOVERY="true"
</syntaxhighlight>



After rebooting you can test it via “xl vcpu-list” command.
After rebooting you can test it via “xl vcpu-list” command.
Line 206: Line 161:
You can do more research and find some interested parameters that you like. We prepared a table that shows you some dom0 options :
You can do more research and find some interested parameters that you like. We prepared a table that shows you some dom0 options :


{| class="prettytable"
!colspan="2"|Option Description
|-
| dom0_mem = X
| Amount of Memory that allocated to Dom0.
|-
|apic=default
| Via this option you can manipulate interrupt controllers but it is detected automatically.
|-
| nolapic
| Don't use APIC even it is enabled by BIOS.
|-
| nosmp
| Disable SMP support.
|-
| watchdog
| It is using for debugging and can be helpful in reporting failures.
|-
| noreboot
| Don't reboot machine automatically when an error happened.
|-
| Vga
| Use VGA console.
|-
| com1
| Use serial Port COM1
|}


To be honest, these options that are said are important, But you can find a list of these hacking at [http://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html http://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html] and [[Tuning_Xen_for_Performance]].
'''OptionDescription'''

dom0_mem=XAmount of Memory that allocated to Dom0.

apic=defaultVia this option you can manipulate interrupt controllers but it is detected automatically.

nolapicDon't use APIC even it is enabled by BIOS.

nosmpDisable SMP support.

watchdogIt is using for debugging and can be helpful in reporting failures.

norebootDon't reboot machine automatically when an error happened.

VgaUse VGA console.

com1Use serial Port COM1.


To be honest, these options that are said are important, But you can find a list of these hacking at [http://wiki.xenproject.org/wiki/Xen_3.x_Configuration_File_Options http://wiki.xenproject.org/wiki/Xen_3.x_Configuration_File_Options] and [http://wiki.xenproject.org/wiki/Tuning_Xen_for_Performance http://wiki.xenproject.org/wiki/Tuning_Xen_for_Performance] .


Next we would like to talk about the Xen Project and Grub.
Next we would like to talk about the Xen Project and Grub.








Line 244: Line 203:


Now, The time is come to speak about Grub bootloader.
Now, The time is come to speak about Grub bootloader.







=== {{anchor|Toc476606912}} <span style="color:#00000a;">Grub2</span> ===
=== {{anchor|Toc476606912}} <span style="color:#00000a;">Grub2</span> ===
Line 263: Line 217:




<div style="text-align:center;">[[Image:Figure_17_-_Linux_Boot_Process.png|top|600px|none|thumb]]</div>
[[Image:Figure_17_-_Linux_Boot_Process.png|top|600px|none|thumb|Figure 17 : Linux Boot Process.]]


===== <span style="color:#00000a;">Figure 17 : Linux Boot Process.=====
What do think? We showed you some important information about Boot and Xen Project and recommended to read the articles that introduced. In the article from Xen project, You can see and Learn how to install “pvgrub2” but this article may be removed or moved to other places in the future and I just show you the installing process :
What do think? We showed you some important information about Boot and Xen Project and recommended to read the articles that introduced. In the article from Xen project, You can see and Learn how to install “pvgrub2” but this article may be removed or moved to other places in the future and I just show you the installing process :


Line 271: Line 224:
1- Git grub :
1- Git grub :


<nowiki># git clone git://git.savannah.gnu.org/grub.git</nowiki>
<syntaxhighlight lang="sh"># git clone git://git.savannah.gnu.org/grub.git</syntaxhighlight>


2- Compile :
2- Compile :


<nowiki># </nowiki>./autogen.sh
<syntaxhighlight lang="sh"># ./autogen.sh</syntaxhighlight>


3- Configure Grub to use Xen :
3- Configure Grub to use Xen :


<nowiki># ./configure --target=amd64 –with-platform=xen </nowiki>(For 64 bit)
<syntaxhighlight lang="sh"># ./configure --target=amd64 –with-platform=xen </syntaxhighlight>(For 64 bit)


<nowiki># ./configure --target=i386 –with-platform=xen </nowiki>(For 32 bit)
<syntaxhighlight lang="sh"># ./configure --target=i386 –with-platform=xen </syntaxhighlight>(For 32 bit)


4- make and install :
4- make and install :


<nowiki># make && make install</nowiki>
<syntaxhighlight lang="sh"># make && make install</syntaxhighlight>




Line 292: Line 245:
1- create a file with the name “grub.cfg” and open it via “nano” editor and write below text to it :
1- create a file with the name “grub.cfg” and open it via “nano” editor and write below text to it :


normal (xen/xvda,msdos1)/boot/grub/grub.cfg
<syntaxhighlight lang="sh">normal (xen/xvda,msdos1)/boot/grub/grub.cfg</syntaxhighlight>


2- Build grub image using “grub-mkimage” utility :
2- Build grub image using “grub-mkimage” utility :


<nowiki># grub-mkimage -O x86_64-xen -c grub.cfg -o grub-x86_64-xen.bin $prefix/lib/grub/x86_64-xen/*.mod</nowiki>
<syntaxhighlight lang="sh"># grub-mkimage -O x86_64-xen -c grub.cfg -o grub-x86_64-xen.bin $prefix/lib/grub/x86_64-xen/*.mod</syntaxhighlight>


3- Now, You can start a guest via “grub-x86_64-xen.bin” as a Kernel by writing below line in your guest configuration :
3- Now, You can start a guest via “grub-x86_64-xen.bin” as a Kernel by writing below line in your guest configuration :


<nowiki># kernel = "grub-x86_64-xen.bin"</nowiki>
<syntaxhighlight lang="sh"># kernel = "grub-x86_64-xen.bin"</syntaxhighlight>

[[Category:Users]] [[Category:HelloXenProjectBook]]

Latest revision as of 09:39, 18 April 2017

Chapter 3: Dom(s) and Grub

Welcome to Chapter 3. We want to speak about Dom0 and DomU. I'm sure that currently you know what is Xen Domain but we want to speak about it more.

Dom0 is the initial domain started by the Xen hypervisor on boot. Its mean “Domain0” and “Dom0” is an abbreviation for it. The Dom0 duty is a privilege domain that manages DomU domains. Without it our Hypervisor is useless and it is kind of “Host” OS, But have special and low level access to hardware. The Dom0 has Drivers for your Hardware but you must know something about the Backend Driver and Front-end Driver. These are two terms for Xen Project.

If DomU wants share hardware, then Dom0 must give it an interface for make requests for access to the hardware. This is done via Backend Driver. For access to the Hardware that shared between Domains, DomU must contact to Dom0. The Front-end Driver prepared for the OS in DomU and use XenBus, XenStore, Shared Pages and... for communicating with Backend Driver. I just want to tell you that “XenStore” is an information storage space that shred between domains and maintained by the Xenstored. The XenBus provides a bus abstraction for Paravirtualized drivers to communicate between domains.

For more information about “XenStore” and “XenBus” Please see XenStore and XenBus.

In below Figure, You can see a cute photo about Dom0 and DomU :

Figure 16 : DomU and Dom0.

I guess you are impatiently waiting for how you can configure Dom0 and DomU. The dome is used for configuration our Guest OS and we will configure it in the next chapter but we will Play with Dom0 here. I know that your thinking, that we want to hack Dom0 here, but your wrong, We just want to show you a way to manipulate:


Change Dom0 memory

For change memory setting you must open /etc/default/grub with an editor like “nano” and apply your Arbitrary settings : 

[root@localhost ~]# cat /etc/default/grub

GRUB_TIMEOUT=5

GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"

GRUB_DEFAULT=saved

GRUB_DISABLE_SUBMENU=true

GRUB_TERMINAL_OUTPUT="console"

GRUB_CMDLINE_LINUX="rd.lvm.lv=fedora/root00 rd.lvm.lv=fedora/swap rhgb quiet"

GRUB_DISABLE_RECOVERY="true"

Find “GRUB_CMDLINE_LINUX” and add “dom0_mem=512M, max: 512M” at the end of this line. After it, Your Dom0 will use 512 megabyte memory and “max” parameter means the maximum memory usage: 

[root@localhost ~]# cat /etc/default/grub

GRUB_TIMEOUT=5

GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"

GRUB_DEFAULT=saved

GRUB_DISABLE_SUBMENU=true

GRUB_TERMINAL_OUTPUT="console"

GRUB_CMDLINE_LINUX="rd.lvm.lv=fedora/root00 rd.lvm.lv=fedora/swap rhgb quiet dom0_mem=512M,max:512M"

GRUB_DISABLE_RECOVERY="true"

Then you must run “grub2-mkconfig -o /boot/grub2/grub.cfg” and reboot your system. After it, The Dom0 will use 512 Megabyte of memory. You can use B for bytes, K for kilobytes, M for megabytes, or G for gigabytes.

If you do some research the you will find a “ballooned” term. The Xen Project from version 3+ supporting memory “ballooning” that allow you to hot, add and remove memory from a running System. It is a technique that used to dynamically adjust the physical memory in use by a guest. Let me show you an example. I have a VM and give it 1024MB memory, but I notice that it just uses %50 of its memory and 512M of my memory wasted and The Xen Project let me to re-size my VM memory without any Downtime. Now that you are familiar with this Term, I want to show you that you can config it via “XL” command.

Open “/etc/xen/xl.conf” file and find “#autoballoon="auto"” then remove “#” and change “auto” to “0”. After it, the “xl” can't adjust the amount of memory assigned to dom0 : 

[root@localhost ~]# cat /etc/xen/xl.conf

## Global XL config file ##

# Control whether dom0 is ballooned down when xen doesn't have enough
# free memory to create a domain. "auto" means only balloon if dom0
# starts with all the host's memory.

#autoballoon="auto"

# full path of the lockfile used by xl during domain creation
#lockfile="/var/lock/xl"

...


Change : 

[root@localhost ~]# cat /etc/xen/xl.conf

## Global XL config file ##

# Control whether dom0 is ballooned down when xen doesn't have enough
# free memory to create a domain. "auto" means only balloon if dom0
# starts with all the host's memory.

autoballoon="0"

# full path of the lockfile used by xl during domain creation

#lockfile="/var/lock/xl"

...

You may ask yourself, Why you must dedicate the fixed amount of memory for Dom0. It is a good idea because :

  • The Linux Kernel calculates various network parameters at the boot time and based on this memory.
  • For store the memory metadata, The Linux need some amount of memory and this feature based on the memory on the boot time.

For more information about “Ballooned”, Please look at “https://blog.xenproject.org/2014/02/14/ballooning-rebooting-and-the-feature-youve-never-heard-of/” and “http://xenbits.xen.org/people/liuw/xen-balloon-driver-improvement.pdf”.


Limit the number of vcpus

To dedicate “vcpu” to Dom0 you must use “dom0_max_vcpus=X” option and “X” is the number of vcpu that you need. You must open “grub.conf” via an editor like “nano” and add above option to it : 

# cat /etc/default/grub

GRUB_TIMEOUT=5

GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"

GRUB_DEFAULT=saved

GRUB_DISABLE_SUBMENU=true

GRUB_TERMINAL_OUTPUT="console"

GRUB_CMDLINE_LINUX="rd.lvm.lv=fedora/root00 rd.lvm.lv=fedora/swap rhgb quiet dom0_max_vcpus=2"

GRUB_DISABLE_RECOVERY="true"

As you see, I dedicated two VCPUs to my Dom0.

Let me guess your question! I guess you are thinking about dedicate a CPU core to Dom0. Am I right? I must tell you that you can. It is possible and sometime is a good idea and guarantee that Dom0 always has Free CPU time and can process the I/O requests from DomUs. For doing it, You must use “ dom0_max_vcpus=X dom0_vcpus_pin” option in your “grub.conf” file : 

# cat /etc/default/grub

GRUB_TIMEOUT=5

GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"

GRUB_DEFAULT=saved

GRUB_DISABLE_SUBMENU=true

GRUB_TERMINAL_OUTPUT="console"

GRUB_CMDLINE_LINUX="rd.lvm.lv=fedora/root00 rd.lvm.lv=fedora/swap rhgb quiet dom0_max_vcpus=2 dom0_vcpus_pin"

GRUB_DISABLE_RECOVERY="true"

After rebooting you can test it via “xl vcpu-list” command.

After it, The next step is to configure your Guests. You must configure them because they must not use those same physical CPUs. This can do via the guest configuration file under “/etc/xen/<guest>.cfg” file. We will talk about it in the future.

You can do more research and find some interested parameters that you like. We prepared a table that shows you some dom0 options :

Option Description
dom0_mem = X Amount of Memory that allocated to Dom0.
apic=default Via this option you can manipulate interrupt controllers but it is detected automatically.
nolapic Don't use APIC even it is enabled by BIOS.
nosmp Disable SMP support.
watchdog It is using for debugging and can be helpful in reporting failures.
noreboot Don't reboot machine automatically when an error happened.
Vga Use VGA console.
com1 Use serial Port COM1

To be honest, these options that are said are important, But you can find a list of these hacking at http://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html and Tuning_Xen_for_Performance.

Next we would like to talk about the Xen Project and Grub.


Xen Project and Grub

If you remember, we briefly talked about PvGrub and PyGrub. The PyGrub enable you to start DomU with a Kernel that inside of DomU instead of Kernel that lies in the filesystem of the Dom0. As you see, this cause easier management and each DomU manage its own kernel and if you manipulate DomU kernel then it can't affect on Dom0 Kernel. The PyGrub have a behavior like Grub and read the standard Grub configuration file (grub.cfg).

The PyGrub, use libfsimage for support Ext2/3/4, FAT, ISO9660, REISERFS, UFS and ZFS File Systems. If you want your DomU use PyGrub then you must add “bootloader = "/usr/bin/pygrub"” in your DomU config file. The PyGrub just support Grub 1 & Grub 2, LILO and ExtLinux bootloaders. Don't forget, Use it is not as easy we said and some Linux Distros need special configuration for it. For example, For Configure it for Debian Please see “https://tipstricks.itmatrix.eu/using-pygrub-on-squeeze-to-boot-a-domu-kernel/”.

The PvGrub or ParaVirtual Grub is a boot manager for Xen Vms. It is a safer alternative for PyGrub to boot DomU images. We can say that the PvGrub is an adapted version of the grub boot loader. The PvGrub require Xen 3.3 or higher. It is provided by the Xen source and you don't need to install grub in DomU. PvGrub Compared with PyGrub has less bugs and is more secure. PvGrub is not scripted and is binary that has less dependencies. For a good How to about it, Please see “http://backdrift.org/xen-pvgrub-howto”.

Now, The time is come to speak about Grub bootloader.

Grub2

A boot loader is the first program that runs when a computer start. The boot loader is responsible for loading and transferring control to an operating system kernel like Linux and then the Kernel initialize the rest of the OS. Grub2 is a powerful boot loader that support modern OS. One the important feature of Grub is flexibility. GNU Grub can offer you a command-line interface and a menu interface. Via CLI you can type the drive and the kernel file manually, but via Menu you select an OS via arrow Keys.

Grub2 is a rewrite version of Grub and have some changes. For example, In the previous version of Grub, The config file name was “menu.lst” or “grub.conf” but in Grub2, It changed to “grub.cfg”. A good advantage of Grub2 is that it can support many file systems and not limited to ext4, HFS+, and NTFS. The “grub.conf” automatically generated by “grub-mkconfig” and it help you to handle various Kernel easier. I'm sure you can remember “grub-mkconfig” in recent chapter and worked with it for generating your Kernel.

If you like to have a good knowledge about Grub2 then IBM has a good article about it that can be found at “http://www.ibm.com/developerworks/library/l-grub2/”. We recommended to see “https://blog.xenproject.org/2015/01/07/using-grub-2-as-a-bootloader-for-xen-pv-guests/” for more information about Grub and Xen.

We showed you some important parameters that you can use them via Grub and the good point is that the GNU Grub is part of Xen by default.

In below Figure, You can see a diagram about The Linux Boot process:


Figure 17 : Linux Boot Process.

What do think? We showed you some important information about Boot and Xen Project and recommended to read the articles that introduced. In the article from Xen project, You can see and Learn how to install “pvgrub2” but this article may be removed or moved to other places in the future and I just show you the installing process :


1- Git grub : 

# git clone git://git.savannah.gnu.org/grub.git

2- Compile : 

# ./autogen.sh

3- Configure Grub to use Xen : 

# ./configure --target=amd64 –with-platform=xen

(For 64 bit) 

# ./configure --target=i386 –with-platform=xen

(For 32 bit)

4- make and install : 

# make && make install


Now, Grub installed and you must create “pvgrub2” image :

1- create a file with the name “grub.cfg” and open it via “nano” editor and write below text to it : 

normal (xen/xvda,msdos1)/boot/grub/grub.cfg

2- Build grub image using “grub-mkimage” utility : 

# grub-mkimage -O x86_64-xen -c grub.cfg -o grub-x86_64-xen.bin $prefix/lib/grub/x86_64-xen/*.mod

3- Now, You can start a guest via “grub-x86_64-xen.bin” as a Kernel by writing below line in your guest configuration : 

# kernel = "grub-x86_64-xen.bin"
Retrieved from "https://wiki.xenproject.org/index.php?title=Book/HelloXenProject/3-Chapter&oldid=17848"