 
	
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] Xen and the art of network configuration
 Hi Everyone,
It's been quite a long time since I mucked around with Xen, and I don't
remember setting up the networking for DomU being such a PITA.  I'm hoping
someone will see what I'm doing wrong and point out a solution (or maybe an
example).
I have a server with a singe NIC and I want to use bridging over Dummy0.  
I built xen from source xen-3.0.4_1; Dom0 is Debian etch as is DomU.
Dom0 network configuration:
auto lo
iface lo inet loopback
auto eth0
        address 209.16.216.213
        netmask 255.255.255.0
        network 209.16.216.0
        broadcast 209.16.216.255
        gateway 209.16.216.1
auto dummy0/vif
iface dummy0 inet static
        address 209.16.216.250
        netmask 255.255.255.0
I can ping my dummy0 ip address from anywhere inside the LAN.
domU config:
name=bart
kernel="/boot/vmlinuz-2.6.16.33-xen"
root="/dev/hda1"
memory=128
disk=['phy:hda7,hda1,w']
vif=[ 'ip=209.16.216.6' ]
hostname="bart.simutronics.com"
I made the following changes to xend-config.sxp and scripts/network-bridge
scripts:
Xend-config.sxp I uncommended and set the netdev to dummy0:
(network-script 'network-bridge netdev=dummy0')
I also tried changing network-bridge (but w/out success):
# netdev=${netdev:-eth${vifnum}} 
netdev=${netdev:-dummy0${vifnum}}
Before starting a domU here's what I get with 'brctl show'
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              vif0.0
                                                                pdummy0
                And after I start domU
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              vif0.0
                                                                pdummy0
                                                                vif2.0
When I start domU I get the following on Dom0:
ADDRCONF(NETDEV_UP): vif2.0: link is not ready
ADDRCONF(NETDEV_CHANGE): vif2.0: link becomes ready
xenbr0: port 3(vif2.0) entering learning state
xenbr0: topology change detected, propagating
xenbr0: port 3(vif2.0) entering forwarding state
Ifconfig on dom0 after starting domU:
dummy0    Link encap:Ethernet  HWaddr 12:7C:64:7A:67:98  
          inet addr:209.16.216.250  Bcast:209.16.216.255  Mask:255.255.255.0
          inet6 addr: fe80::107c:64ff:fe7a:6798/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:369 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:15714 (15.3 KiB)  TX bytes:468 (468.0 b)
eth0      Link encap:Ethernet  HWaddr 00:30:48:41:D6:50  
          inet addr:209.16.216.63  Bcast:209.16.216.255  Mask:255.255.255.0
          inet6 addr: fe80::230:48ff:fe41:d650/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3747 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2327 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:369497 (360.8 KiB)  TX bytes:345668 (337.5 KiB)
          Base address:0xa000 Memory:ec000000-ec020000 
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
pdummy0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:374 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:16092 (15.7 KiB)
vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:369 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:468 (468.0 b)  TX bytes:15714 (15.3 KiB)
vif2.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:369 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32 
          RX bytes:10548 (10.3 KiB)  TX bytes:0 (0.0 b)
xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:375 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:10932 (10.6 KiB)  TX bytes:0 (0.0 b)
Thank you all for your help.
--Jim
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
 
 | 
|  | Lists.xenproject.org is hosted with RackSpace, monitoring our |