We used one of these
tools??”xm, the Xend Manager??”to check whether any Xen domains were running. xm
is the main interface provided for managing the various Xen guest domains. It can
be used to create, pause, and shutdown domains. It can also be used, as we did, to
list current domains. We are going to look in detail at all the things you can do with
xm in Chapter 4. Finally we check to make sure that our network interfaces are up.
The topic of Xen networking will be covered in detail in Chapter 5. We successfully
installed and got Xen running by using the pre-built binary packages provided by
Fedora Core 6.
Installing Xen from Source
In the previous section we installed Xen using binary packages. It was quite simple
and quick, and enabled us to get Xen running easily especially because the hard
job of matching the hypervisor/host/guest kernel options was done by RedHat.
However, this means that you depend on the Xen pre-built packages, keeping up
with the changes taking place in Xen, which is a fast moving target with bug fixes
and features. You cannot take advantage of a brand new feature or a bug fix that
was added recently and which is quite crucial for your use. The binary packages
usually track the release versions of Xen, so there is no way for you to try out the
development versions or the pre-release versions. Here are some reasons why you
should get comfortable building Xen from the source code in the Xen revision control
repository hosted by Xensource (http://xenbits.
Pages:
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31