Once xend is running, it will start Domain0, which is the privileged domain.
Check to see that Domain0 has been created and is up and running by using
the xm command.
7. Check to see that all the network interfaces are up. This will include the
normal network interfaces such as eth0 and lo, and the Xen related interfaces.
The name of the network interface peth0 that we can see in the following
screenshot has changed to eth0 in the newer versions of Fedora 7.0 and above.
8. You are now running Xen!
Chapter 2
[ 15 ]
What Just Happened?
We used yum to install the following:
Xen hypervisor
dom0 kernel
Xen libraries and Python modules
User space tools for interacting with Xen from dom0
The configuration for grub was modified automatically by the installation to add an
entry for booting the Xen hypervisor and the dom0 kernel. Let us examine each line
that was added as it will give a good insight into the process of what happens when
a Xen system boots up. Here is the section that was added for the Xen kernel in the
/boot/grub/grub.conf (Line numbers have been added and are not actually
present in the file):
1. title Fedora Core (2.6.19-1.2911.6.5.fc6xen)
2. root (hd0,1)
3. kernel /xen.gz-2.6.19-1.2911.6.5.fc6
4. module /vmlinuz-2.6.19-1.2911.6.5.fc6xen ro root=/dev/VolGroup00/
LogVol00 rhgb quiet
5. module /initrd-2.6.19-1.2911.6.5.fc6xen.img
Line 1 defines the title for this kernel and is displayed in the grub menu on boot,
which allows you to select a kernel.
Pages:
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29