Start up the domU by using xm:
# xm create /home/pchaganti/xenimages/ttylinux_domU.cfg ??“c
4. Check to make sure that the domU is up and running:
Networking
[ 76 ]
What Just Happened?
The default dom0 configuration file??”/etc/xen/xend-config.sxp is set up to use
bridged networking so that all domains appear on the network as individual hosts.
This default bridge created by the dom0 on startup is named xenbr0. On some older
systems it is called xen-br0. On the newer Fedora systems, the bridge is actually
called eth0, and the physical hardware is called peth0. In our domU configuration
file, we specified that we want to connect the network interface for this domU to the
bridge named xenbr0.
When using bridged networking, Xen creates a network bridge and then connects
the actual physical network interface to this bridge. Virtual network interfaces are
then created for dom0 and each of the guest domains; these are all attached to the
network bridge. In this manner, all the domains can connect to any address to which
the physical network interface can connect.
Let us take a detailed look at what all these different terms mean and what actually
happens when your dom0 is set up to use bridged networking and you create a
domU that uses that bridge.
Here is the sequence of events that happen when you boot up your Xen server and
xend starts up (only dom0 is started and no guest domains set to auto start by xend. I
only have one physical network interface on my server and it is named eth0).
Pages:
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78