Warning that network will not work during DomU creation

[vtapas]

Originally Posted by Mark_NL

sham:/etc/xen# grep -v '#' xend-config.sxp
(network-script 'network-bridge netdev=eth0')
(vif-script vif-bridge)
(dom0-min-mem 196)
(dom0-cpus 0)
(vncpasswd '')

sham:/etc/xen# cat myvm
kernel      = '/boot/vmlinuz-2.6.26-2-xen-686'
ramdisk     = '/boot/initrd.img-2.6.26-2-xen-686'
memory      = '4096'
root        = '/dev/hda1 ro'
disk        = [
		'phy:/dev/drbd0,hda1,w',
		'file:/swapfiles/myvm.swp,hda2,w',
	      ]
name        = 'myvm.domain.tld'
vif         = [ 'ip=213.207.x.x' ]
on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'restart'

Thanks for staying so long.Finally it is working.I have changed the name to eth2.

I am trying to understand I have to route traffic from my 4VMs through this LAN interface which I call as eth2.I have to do NAT but I am a bit confusing in bridges.Can you give me some link here may be on howtoforge itself which makes me clear of routing on Xen.


I am pasting the output of ifconfig it does not shows me any where brdige
while brctl show does show

openworld:/etc/xen# brctl show
bridge name	bridge id		STP enabled	interfaces
eth2		8000.0026b9824238	no		peth2
							vif1.0
							vif2.0
							vif3.0
							vif5.0

and ifconfig

openworld:/etc/xen# ifconfig
eth2      Link encap:Ethernet  HWaddr 00:26:b9:82:42:38  
          inet addr:192.21.100.147  Bcast:192.21.255.255  Mask:255.255.0.0
          inet6 addr: fe80::226:b9ff:fe82:4238/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3436 errors:0 dropped:0 overruns:0 frame:0
          TX packets:233 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2460960 (2.3 MiB)  TX bytes:34543 (33.7 KiB)

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:15 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1141 (1.1 KiB)  TX bytes:1141 (1.1 KiB)

peth2     Link encap:Ethernet  HWaddr 00:26:b9:82:42:38  
          inet6 addr: fe80::226:b9ff:fe82:4238/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:4277 errors:0 dropped:0 overruns:0 frame:0
          TX packets:244 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2669261 (2.5 MiB)  TX bytes:36485 (35.6 KiB)
          Interrupt:32 Memory:da000000-da012100 

vif1.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff  
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3594 errors:0 dropped:34 overruns:0 carrier:0
          collisions:0 txqueuelen:32 
          RX bytes:28 (28.0 B)  TX bytes:2583658 (2.4 MiB)

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 PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3545 errors:0 dropped:52 overruns:0 carrier:0
          collisions:0 txqueuelen:32 
          RX bytes:28 (28.0 B)  TX bytes:2549186 (2.4 MiB)

vif3.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff  
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:176 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3624 errors:0 dropped:74 overruns:0 carrier:0
          collisions:0 txqueuelen:32 
          RX bytes:10475 (10.2 KiB)  TX bytes:2529692 (2.4 MiB)

vif5.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff  
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:7 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1172 errors:0 dropped:13 overruns:0 carrier:0
          collisions:0 txqueuelen:32 
          RX bytes:412 (412.0 B)  TX bytes:864715 (844.4 KiB)

All the above entries are after I have restarted and I did a reboot also to the machine.

Here is my /etc/xen/xend-config.sxp

 Your default ethernet device is used as the outgoing interface, by default.
# To use a different one (e.g. eth1) use
#
# (network-script 'network-bridge netdev=eth1')
#
#### Tapas edited following line
 (network-script 'network-bridge netdev=eth2')

[Mark_NL]

You can use bridge mode, so the interfaces inside the vm will act like they're directly connected to the network ..

I wouldn't use NAT, since then you need to route your traffic from to your vm server ..
We always use bridge, it's way easier and no firewall / routing rules to take care of ..

info @ http://wiki.xensource.com/xenwiki/XenNetworking

I've been playing with some virtualization techniques, though since i found proxmox i want nothing else

webbased management of KVM / Openvz vm's .. very nice .. I'm migrating all my Xen servers to proxmox :P

[vtapas]

Originally Posted by Mark_NL

proxmox

Well thanks for that link. I have a doubt I changed the name of bridge from default
I can
ping to each of them after I do an SSH inside Dom0.
In the file /etc/xen/xend-config.sxp
I tried to have a bridge of my name so I edited them as follows

# The bridge is named xenbr0, by default. To rename the bridge, use
#
# (network-script 'network-bridge bridge=<name>')
#### Tapas made changes
(network-script 'network-bridge bridge=<tapas>')

I did rebooted my server but then when I do brctl show

I get following
bridge name bridge id STP enabled interfaces
eth2 8000.0026b9824238 no peth2

eth2 is not the default name why is this happening? What should I
check in? I want to have bridges renamed and want the bridges to have
desired name.

[Mark_NL]

Hehe, your just trial and error right now and that messes things up ..

(network-script 'network-bridge bridge=tapas')

NOT

(network-script 'network-bridge bridge=<tapas>')

anyway, i would leave the bridge=<name> alone, and keep it default (comment the line), just use netdev=eth2

should work ..

[vtapas]

Originally Posted by Mark_NL

(network-script 'network-bridge bridge=tapas')

Well it did not worked.

openworld:~# brctl show
bridge name	bridge id		STP enabled	interfaces
eth2		8000.0026b9824238	no		peth2

The entry in /etc/xen/xend-config.sxp is

# The bridge is named xenbr0, by default.  To rename the bridge, use
#
# (network-script 'network-bridge bridge=<name>')
#### Tapas made changes
  (network-script 'network-bridge bridge=tapas')
# It is possible to use the network-bridge script in more complicated

?

[Mark_NL]

as i said before, don't use bridge .. comment it!

you should only use:

(network-script 'network-bridge netdev=eth2')

[vtapas]

I got your point.Up to here. I want each DomU to connect to separate LAN Card.
I found this article http://www.debian-administration.org/articles/470
which is a bit helpful.Any ways thanks for your help.