PyGrub enables you to start Linux domUs with a kernel inside the DomU instead of a kernel that lies in the filesystem of the dom0. This means easier management - each domU manages its own kernel and initrd, meaning you can use the built-in package manager to update the kernels, instead of having to track and update kernels stored in your dom0. It also allows easy migration of HVM'ed Linuxes - there's no need to extract the installed kernel & initrd.
It is used as a Bootloader and provided with Xen Project. PyGrub behaves like Grub and reads the standard Grub menu.lst (or Grub2's grub.cfg) to provide the xen create process with the required parameters and SXP stanzas.
Therefore usage is quite easy.
PyGrub accesses the guest filesystem using a userspace filesystem library (derived in part from grub's filesystem modules as well as libe2fs) which it uses to extract the necessary configuration, kernel and initrd for use by the domain builder. This means that reading the guest filesystem does not require mounting the filesystem and runs with userlevel privileges which means that a malicious or corrupt guest filesystem cannot crash or otherwise compromise your domain 0.
In your domU
- Install Grub
- Install a linux-image-xen of your choice.
- Create the /boot/grub directory if it is not present.
- Let it create its default menu.lst (update-grub in Debian)
In your dom0
Change your domU.cfg:
- remove kernel and initrd stanza
- add bootloader stanza, e.g.
bootloader = 'pygrub'
Note: For older versions of Xen Project software (4.1 or earlier) you need to know where in the filesystem pygrub lies. For example, debian uses /usr/lib/xen-$version/bin/pygrub or something like this, instead of the path reflected above. Newer versions of the toolstack know how to look for the path themselves.
Important Tip / Caveat
On your disk line, e.g.
disk = ['file:/vserver/mail/guest_base2G.img,hda1,w','file:/vserver/mail/guest_swap256M.img,hda2,w','phy:data/mail,hda3,w']
make sure that the partition/lvm/container that contains the kernel and initrd comes first. Xend passes the *first* entry to pyGrub. (At least for Version 3.2.1) If the first disk entry does not contain a kernel you will most likely get
Error: Boot loader didn't return any data
If you get this error have a look at /var/log/xen/xend.log . You can read here which parameters were given to pyGrub, try them by hand and see if pyGrub outputs the right stanzas for domU startup. (They look a little like grub entries LISPified, SXP-Format).
Thanks to (The following is taken from http://lists.xensource.com/archives/html/xen-users/2007-09/msg00524.html and own experience) for first pyGrub Reference.
Supported File Systems
PyGrub supports the following filesystems via libfsimage:
Supported Bootloader Configuration Files
PyGrub supports the configuration file syntax of the following native bootloaders:
- Grub 1 & Grub 2
|Language:||English • Deutsch • Español • Français • 日本語 • 한국어 • Português do Brasil • Русский • 中文|