Change the xen configuration file - /etc/xen/xend-config.sxp so we can
use routed networking. Comment out the two lines related to the bridged
networking and uncomment the two lines related to routed networking. If
you don't happen to have the routed networking lines in your configuration
file, add them:
(network-script network-route)
(vif-script vif-route)
Chapter 5
[ 81 ]
3. Start xend again so that it starts up with the new settings:
# xend start
4. Modify the configuration file for the domU we used earlier so that it can use
routed networking.
kernel = "/boot/vmlinuz-2.6.16.38-xenU"
memory = 32
name = "routed_domU"
disk = ['tap:aio:/home/pchaganti/xen-
images/ttylinux_domU.img,hda,w']
vif = [ 'ip=192.168.1.165' ]
root = "/dev/hda1 ro"
5. Start up the domU.
# xm create /home/pchaganti/xen-images/ttylinux_domU.cfg ??“c
6. Check to make sure the domU is up and running.
What Just Happened?
Here is the sequence of events that happens when xend starts up with a routed
network configuration (only dom0 is started up in this instance. I have only one
physical network interface on my server and it is named eth0);
1. Enable IP forwarding within dom0.
2. That is essentially all that xend does to get the network configured. Check
the network configuration and list the interfaces created by running the
ifconfig command.
Networking
[ 82 ]
3. Display the contents of the routing table used by the Xen server by running
the route command.
Pages:
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82