Hello, Despite of reading a lot of descriptions I don''t understand the network configuration. I simply have too little experience. I work remote with the machine via ssh. My dom0 is running. I copied an existing installation into a LV and created the following file: # cat /etc/xen/domu-sarge # -*- mode: python; -*- kernel = "/boot/vmlinuz-2.6.18-4-xen-686" #kernel = "/boot/vmlinuz-2.6.8-3-686-smp" memory = 128 name = "domu-sarge" vif = ['' bridge=xen-br0'' ] disk = [''phy:/dev/system/sarge,hdb1,w'',''phy:/dev/system/sarge-swap,hdb2,w''] ip="192.168.0.10" netmask="255.255.255.0" gateway="192.168.0.1" hostname = "server1" root = "/dev/hdb1 ro" extra = "4" The domU interfaces looks like that: # cat /mnt/sarge/etc/network/interfaces auto lo iface lo inet loopback auto xen-br0 iface xen-br0 inet static name Ethernet LAN card address 192.168.0.10 netmask 255.255.255.0 broadcast 192.168.0.255 network 192.168.0.0 gateway 192.168.0.1 If that is correct how do I have to configure the dom0 interfaces? I think I have to create the bridge interface. But I don''t know how exactly. I am worried that if I make a mistake here I will loose my ssh connection. Please help me with this critical step. Regards, Marco _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, 2007-04-20 at 00:36 +0200, Marco Mandl wrote:> Hello, > > Despite of reading a lot of descriptions I don''t understand the network > configuration. I simply have too little experience. > > I work remote with the machine via ssh. My dom0 is running. > > I copied an existing installation into a LV and created the following file: > # cat /etc/xen/domu-sarge > # -*- mode: python; -*- > kernel = "/boot/vmlinuz-2.6.18-4-xen-686" > #kernel = "/boot/vmlinuz-2.6.8-3-686-smp" > memory = 128 > name = "domu-sarge" > vif = ['' bridge=xen-br0'' ]You may want to put a static mac= directive here, but that shouldn''t prevent it from working.> disk = [''phy:/dev/system/sarge,hdb1,w'',''phy:/dev/system/sarge-swap,hdb2,w''] > ip="192.168.0.10" > netmask="255.255.255.0" > gateway="192.168.0.1" > hostname = "server1" > root = "/dev/hdb1 ro" > extra = "4"Rest Looks good. I usually don''t specify ip/netmask/gateway in the config, I just do it in the dom-u.> The domU interfaces looks like that: > # cat /mnt/sarge/etc/network/interfaces > auto lo > iface lo inet loopback >You don''t want to make a bridge xen-br0 inside of the guest, this should just be eth0.> auto xen-br0 > iface xen-br0 inet static > name Ethernet LAN card > address 192.168.0.10 > netmask 255.255.255.0 > broadcast 192.168.0.255 > network 192.168.0.0 > gateway 192.168.0.1 > > If that is correct how do I have to configure the dom0 interfaces?Just change xen-br0 to eth0 inside of the dom-u. It goes : [ internet ] -> -> [ xen-br0 ] -> -> [ eth0-in-domU ]> I think I have to create the bridge interface. But I don''t know how > exactly. I am worried that if I make a mistake here I will loose my ssh > connection. > > Please help me with this critical step.You should be fine, provided xen-br0 was setup correctly on dom-0. Do this via ifconfig xen-br0 on dom-0 and ensure it shows the right IP / etc.> Regards, > MarcoBest, --Tim> > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, 20 Apr 2007 11:48:35 +0800, Tim Post wrote:> You should be fine, provided xen-br0 was setup correctly on dom-0. Do > this via ifconfig xen-br0 on dom-0 and ensure it shows the right IP / > etc.Tim, Thank you very much for your answer. Just to make sure I understand it correctly. I replace eth0 with xen-br0 in interfaces of dom0 and add a disabling entry for eth0 (adresse 0.0.0.0) Then xen-br0 works like eth0 for dom0 like before but also provides the eth0 for the domUs. /m _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, 2007-04-20 at 10:47 +0200, Marco Mandl wrote:> On Fri, 20 Apr 2007 11:48:35 +0800, Tim Post wrote: > > > You should be fine, provided xen-br0 was setup correctly on dom-0. Do > > this via ifconfig xen-br0 on dom-0 and ensure it shows the right IP / > > etc. > > Tim, > > Thank you very much for your answer. > > Just to make sure I understand it correctly. I replace eth0 with xen-br0 > in interfaces of dom0 and add a disabling entry for eth0 (adresse 0.0.0.0)Opposite. In the dom-u, you replace xen-br0 with eth0. On dom-0, you ensure that xen-br0 has the IP of whatever network interface normally talks to the Internet, typically eth0. If your install is typical, xend will run /etc/xen/scripts/network-bridge targeting eth0 to make it xen-br0 when it starts on boot. Likewise, if you stop xend, network-bridge should restore eth0 to an un-bridged (not enslaved) state, putting it back the way it was. You should not need to worry about dom-0.> > Then xen-br0 works like eth0 for dom0 like before but also provides the > eth0 for the domUs.Exactly. On dom-0, eth0 becomes br0, which backs eth0 on guests who have vifs attached to it. Hope this helps. --Tim _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, 20 Apr 2007 17:58:46 +0800, Tim Post wrote:> Opposite. In the dom-u, you replace xen-br0 with eth0.Which IP adresse this eth0 should have - the one of the physical eth0 of dom0?> > On dom-0, you ensure that xen-br0 has the IP of whatever network > interface normally talks to the Internet, typically eth0. > > If your install is typical, xend will run > /etc/xen/scripts/network-bridge targeting eth0 to make it xen-br0 when > it starts on boot. Likewise, if you stop xend, network-bridge should > restore eth0 to an un-bridged (not enslaved) state, putting it back the > way it was. You should not need to worry about dom-0.The start of xend does not create an interface. I am not aware of having changed anything except in xend-config: (network-script ''network-bridge netdev=eth0'') (vif-script vif-bridge) # /etc/init.d/xend restart Restarting XEN control daemon: xend. # ifconfig -s Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg eth0 1500 0 19065 0 0 0 13558 0 0 0 BMRU lo 16436 0 0 0 0 0 0 0 0 0 LRU # xm create domu-sarge -c Using config file "/etc/xen/domu-sarge". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. # ifconfig -a eth0 Protokoll:Ethernet Hardware Adresse 00:0E:7F:FD:8D:37 inet Adresse:192.168.17.10 Bcast:192.168.17.255 Maske:255.255.255.0 inet6 Adresse: fe80::20e:7fff:fefd:8d37/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:19143 errors:0 dropped:0 overruns:0 frame:0 TX packets:13607 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:1000 RX bytes:4343478 (4.1 MiB) TX bytes:3498739 (3.3 MiB) Interrupt:19 lo Protokoll:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine 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 Kollisionen:0 Sendewarteschlangenlänge:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) sit0 Protokoll:IPv6-nach-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth0 Protokoll:Ethernet Hardware Adresse 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth1 Protokoll:Ethernet Hardware Adresse 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth2 Protokoll:Ethernet Hardware Adresse 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth3 Protokoll:Ethernet Hardware Adresse 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.0 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.1 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.2 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.3 Protokoll:Ethernet Hardware Adresse FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) /m _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, 20 Apr 2007 17:30:48 +0200, Marco Mandl wrote:> On Fri, 20 Apr 2007 17:58:46 +0800, Tim Post wrote: > >> Opposite. In the dom-u, you replace xen-br0 with eth0. > > Which IP adresse this eth0 should have - the one of the physical eth0 of > dom0? >> > > The start of xend does not create an interface. I am not aware of having > changed anything except in xend-config: > (network-script ''network-bridge netdev=eth0'') > (vif-script vif-bridge) >I found the problem - bridge-utils where not installed. Now I get # ifconfig -s Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg eth0 1500 0 486 0 0 0 344 0 0 0 BMRU lo 16436 0 0 0 0 0 0 0 0 0 LRU peth0 1500 0 481 0 0 0 343 0 0 0 BORU vif0. 1500 0 344 0 0 0 486 0 0 0 BORU xenbr 1500 0 10 0 0 0 0 0 0 0 BORU But still the domU is not started. I get the following error:> > # xm create domu-sarge -c > Using config file "/etc/xen/domu-sarge". > Error: Device 0 (vif) could not be connected. Hotplug scripts not working. >/m _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> But still the domU is not started. I get the following error: >> >> # xm create domu-sarge -c >> Using config file "/etc/xen/domu-sarge". >> Error: Device 0 (vif) could not be connected. Hotplug scripts not working. >>Solved it by re-creating the image with the copy option. /m _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users