Kris Vassallo
2006-Feb-07 02:16 UTC
[Xen-users] No network connectivity for domU in SuSE 10, Xen 3
Hey everyone, I''m asking this question again because 1. I Read as much
as I could of the archives and still had no success, and 2. am not sure
if the posts that I was reading actually pertained to Xen 2 or Xen 3.
Here''s what I''m hoping for some help with:
I''m running SuSE 10 (updated) with a SuSE 10 xm with xen-3.0_8259-0.1.
The problem that I''m having is that I can get absolutely no network
traffic to go from dom0 to domU, or anywhere else for that matter. I
have tried using both DHCP and static addressing. The following
information will be in regards to the static address scheme I was
trying. Basically when domU boots, it doesn''t bother to bring up the
eth0 interface, bringing the interface up with an ifup will bring the
interface up (and with dhcp it fails acquiring an address and
backgrounds) but I am unable to ping any device on my network besides
the address that is assigned to the domU machine itself. Dom0 networking
is just fine. The bridge is up, the vif for the xm is up... something
just isn''t linking together here. I''ll include all of my
config
information below and would appreciate any help with this. I''ve been
working on this for days and am getting no where with it :(
On domainU I have the following:
linux:~ # brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif0.0
peth0
vif8.0
linux:~ # ifconfig
(loopback omitted)
eth1 Link encap:Ethernet HWaddr 00:40:D0:43:A3:DB
inet addr:192.168.1.35 Bcast:192.168.1.255
Mask:255.255.255.0
inet6 addr: fe80::240:d0ff:fe43:a3db/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6927 errors:0 dropped:0 overruns:0 frame:0
TX packets:4867 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2655951 (2.5 Mb) TX bytes:611617 (597.2 Kb)
Base address:0x3400 Memory:fc220000-fc240000
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST NOARP 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
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Base address:0x2000 Memory:fc100000-fc120000
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 MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:226 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:9780 (9.5 Kb)
vif8.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:37 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:5 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1554 (1.5 Kb) 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 MULTICAST MTU:1500 Metric:1
RX packets:217 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6076 (5.9 Kb) TX bytes:378 (378.0 b)
linux:~ # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0
eth1
My XM config file:
disk = [ ''file:/data/xen/otrs2/hda1,hda1,w'' ]
memory = 256
kernel = "/boot/vmlinuz-2.6.13-15.7-xen"
ramdisk = "/boot/initrd-2.6.13-15.7-xen"
name = "otrs"
nics=1
vif = [ ''mac=aa:00:00:00:39:01, bridge=xenbr0'' ] <-- I
HAVE TRIED:
excluding this line, using only the mac argument, and using only the
bridge argument... it''s no help
ip="192.168.1.39"
netmask="255.255.255.0"
gateway="192.168.1.1"
hostname="pieceofcrap"
root = "hda1"
On DomainU
(loopback omitted)
eth0 Link encap:Ethernet HWaddr AA:00:00:00:39:01
inet addr:192.168.1.39 Bcast:192.168.1.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:1554 (1.5 Kb)
linux:~ # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
lo
NOTE: doing a "route add default gw 192.168.1.1" here does not fix
the
problem.
linux:~ # cat /etc/sysconfig/network/ifcfg-eth0
IPADDR=192.168.1.39
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
STARTMODE=''auto'' <-- Have also tried
''onboot''
USERCONTROL=no
------------------------
-Kris
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Andy Repton
2006-Feb-07 09:13 UTC
Re: [Xen-users] No network connectivity for domU in SuSE 10, Xen 3
Are you using the Suse kernel/xen or one you rolled yourself? If you check the Suse sources, they back out one of the patches (I think 8246) with the note "it breaks networking". I found that it did indeed stop my Suse DomU from contacting the outside world, but strangely, the gentoo DomU was fine. Andy On 2/7/06, Kris Vassallo <kris@linuxcertified.com> wrote:> Hey everyone, I''m asking this question again because 1. I Read as much as I > could of the archives and still had no success, and 2. am not sure if the > posts that I was reading actually pertained to Xen 2 or Xen 3. Here''s what > I''m hoping for some help with: > > I''m running SuSE 10 (updated) with a SuSE 10 xm with xen-3.0_8259-0.1. The > problem that I''m having is that I can get absolutely no network traffic to > go from dom0 to domU, or anywhere else for that matter._______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thorolf Godawa
2006-Feb-08 13:22 UTC
Re: [Xen-users] No network connectivity for domU in SuSE 10, Xen 3
Hi, try to set STARTMODE=''onboot'' in the ifcfg-eth0.... in dom0 and domU. It also seems to be better to set the config of the domU to a static MAC-address, because with every boot (and new MAC-address if they are created random) SuSE creates a new eth-if! Check in the 30-net_persistent_names.rules that there is only one entry for eth0 for the wanted MAC-address! Maybe it helps! -- Chau y hasta luego, Thorolf _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Kris Vassallo
2006-Feb-08 22:33 UTC
Re: [Xen-users] No network connectivity for domU in SuSE 10, Xen 3
On Wed, 2006-02-08 at 14:22 +0100, Thorolf Godawa wrote:> Hi, > > try to set STARTMODE=''onboot'' in the ifcfg-eth0.... in dom0 and domU.As was in my last email, startmode is set to onboot and I have tried auto as well, but still the darn thing won''t come up on domU boot> > It also seems to be better to set the config of the domU to a static > MAC-address, because with every boot (and new MAC-address if they are > created random) SuSE creates a new eth-if! > > Check in the 30-net_persistent_names.rules that there is only one entry > for eth0 for the wanted MAC-address! >Same thing here, I already have the physical address set in the domU config and I only have 1 line (which I included in my previous posting) in my 30-net_persistent_names.rules which corresponds to the same mac as is set in the domU configuration file. Yet still the interface doesn''t come up at domU boot. Any other ideas on why SuSU 10 wont bring up eth0 on domU boot? -Kris> Maybe it helps!_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Lars Braeuer
2006-Feb-09 12:57 UTC
Re: [Xen-users] No network connectivity for domU in SuSE 10, Xen 3
Kris Vassallo wrote:> On Wed, 2006-02-08 at 14:22 +0100, Thorolf Godawa wrote: > >>Hi, >> >>try to set STARTMODE=''onboot'' in the ifcfg-eth0.... in dom0 and domU. >> > As was in my last email, startmode is set to onboot and I have tried > auto as well, but still the darn thing won''t come up on domU boot > >> >>It also seems to be better to set the config of the domU to a static >>MAC-address, because with every boot (and new MAC-address if they are >>created random) SuSE creates a new eth-if! >> >>Check in the 30-net_persistent_names.rules that there is only one entry >>for eth0 for the wanted MAC-address! >> > Same thing here, I already have the physical address set in the domU > config and I only have 1 line (which I included in my previous posting) > in my 30-net_persistent_names.rules which corresponds to the same mac as > is set in the domU configuration file. Yet still the interface doesn''t > come up at domU boot. > > Any other ideas on why SuSU 10 wont bring up eth0 on domU boot? > -Kris > >>Maybe it helps!I''m experiencing the same problem with xen 3 + suse 10 (kernel-xen 2.6.13). After Dom0 boot up the following interfaces are present (cable is attached to eth0): 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: vif0.0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff inet6 fe80::fcff:ffff:feff:ffff/64 scope link valid_lft forever preferred_lft forever 3: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc noqueue link/ether 00:e0:81:58:91:11 brd ff:ff:ff:ff:ff:ff inet 192.168.123.109/24 brd 192.168.123.255 scope global eth0 inet6 fe80::2e0:81ff:fe58:9111/64 scope link valid_lft forever preferred_lft forever 4: peth0: <BROADCAST,MULTICAST,NOARP,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff inet6 fe80::fcff:ffff:feff:ffff/64 scope link valid_lft forever preferred_lft forever 5: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000 link/ether 00:e0:81:58:91:10 brd ff:ff:ff:ff:ff:ff 6: sit0: <NOARP> mtu 1480 qdisc noop link/sit 0.0.0.0 brd 0.0.0.0 7: xenbr0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff inet 192.168.123.120 peer 192.168.123.254/32 brd 192.168.123.255 scope global xenbr0 inet6 fe80::200:ff:fe00:0/64 scope link valid_lft forever preferred_lft forever The script "network-bridge" runs completely till the last line (verified), but is hanging afterwards as a zombie. 6368 ? Z 0:00 [network-bridge] <defunct> Dom0 brctl show output is: bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif0.0 peth0 When a DomU system is started (suse) a new interface is added in Dom0: 8: vif1.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff The config of the DomU system looks like this: -------------------------------------- name ="domu1" kernel ="/boot/vmlinuz-2.6.13-15-xen" memory =1024 vif = [''mac=aa:00:00:01:01:00, bridge=xenbr0''] disk = [''phy:sda5,sda1,w''] root ="/dev/sda1 ro" # network nics=1 dhcp ="off" ip="192.168.123.90" netmask="255.255.255.0" gateway="192.168.123.254" hostname="domu1" extra="3" -------------------------------------- The following interfaces are present within domu1: 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: vif0.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 3: veth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 4: eth5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000 link/ether aa:00:00:01:01:00 brd ff:ff:ff:ff:ff:ff 5: sit0: <NOARP> mtu 1480 qdisc noop link/sit 0.0.0.0 brd 0.0.0.0 Although the vif-bridge script is stated as vif-script in the xend-config.sxp it is not run. (vif-script vif-bridge) ... so I tried to add the stuff manually: brctl addif xenbr0 vif1.0 ifconfig vif1.0 up (Didn''t add the iptables rules yet, because all chains are "ACCEPT") Leading to (Dom0): bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif0.0 peth0 vif1.0 When I configure eth5 (in domu1) with an ip address (192.168.123.90) and try to add a route to the net I get: # route add -net 192.168.123.0 netmask 255.255.255.0 eth5 SIOCADDRT: Network is down Is there another way to get it manually working? Why would''nt the vif-bridge script run (the script is executable)? Is there a bridge setup within the DomU required? The bridge userland tools are installed within the domu1. Best, Lars _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Bráulio Gergull
2006-Feb-09 13:35 UTC
Re: [Xen-users] No network connectivity for domU in SuSE 10, Xen 3
On Feb 09, 2006 10:57 AM, Lars Braeuer <lbraeuer@mpex.net> wrote: Hi Lars, Try updating your system (Yast Online Update). Maybe the default packages are buggy. I''m running SUSE10 (updated) and it''s working just fine, domU''s configured with dhcp. # uname -a Linux linux 2.6.13-15.7-xen #1 SMP Tue Nov 29 14:32:29 UTC 2005 i686 athlon i386 GNU/Linux # rpm -qa | grep xen | sort kernel-xen-2.6.13-15.7 kernel-xen-nongpl-2.6.13-15.7 xen-3.0_7608-2.1 xen-doc-html-3.0_7608-2.1 xen-doc-pdf-3.0_7608-2.1 xen-doc-ps-3.0_7608-2.1 xen-tools-3.0_7608-2.1> > Is there a bridge setup within the DomU required? The bridge userland > tools > are installed within the domu1.You don''t need neither bridge-utils nor xen-tools in domU''s. You don''t even need the xen kernel if you have statically compiled all needed modules or pass them through an initrd. rgrds, Braulio Gergull _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Lars Braeuer
2006-Feb-09 15:08 UTC
Re: [Xen-users] No network connectivity for domU in SuSE 10, Xen 3
Hi Braulio, thanks for the tip. After the update the system hangs with a kernel panic, right after the (XEN) stuff on top. Can''t exactly tell what it is, because the output of the kernel panic fills the screen an the panic itself locks up the keyboard. So I guess I''ll better use an older xen version. Thanks anyways. Best, Lars Bráulio Gergull wrote:> On Feb 09, 2006 10:57 AM, Lars Braeuer <lbraeuer@mpex.net> wrote: > > Hi Lars, > > Try updating your system (Yast Online Update). Maybe the default > packages are buggy. > > I''m running SUSE10 (updated) and it''s working just fine, domU''s > configured with dhcp. > > # uname -a > Linux linux 2.6.13-15.7-xen #1 SMP Tue Nov 29 14:32:29 UTC 2005 i686 > athlon i386 GNU/Linux > > # rpm -qa | grep xen | sort > kernel-xen-2.6.13-15.7 > kernel-xen-nongpl-2.6.13-15.7 > xen-3.0_7608-2.1 > xen-doc-html-3.0_7608-2.1 > xen-doc-pdf-3.0_7608-2.1 > xen-doc-ps-3.0_7608-2.1 > xen-tools-3.0_7608-2.1 > > >>Is there a bridge setup within the DomU required? The bridge userland >>tools >>are installed within the domu1. > > > You don''t need neither bridge-utils nor xen-tools in domU''s. You don''t > even need the xen kernel if you have statically compiled all needed > modules or pass them through an initrd. > > > rgrds, > Braulio Gergull > > > > > > _______________________________________________ > 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
Bráulio Gergull
2006-Feb-09 16:50 UTC
Re: [Xen-users] No network connectivity for domU in SuSE 10, Xen 3
Hi Lars, On Feb 09, 2006 01:08 PM, Lars Braeuer <lbraeuer@mpex.net> wrote:> Hi Braulio, > > thanks for the tip. After the update the system hangs with a kernel > panic, right after the (XEN) > stuff on top. > Can''t exactly tell what it is, because the output of the kernel panic > fills the screen > an the panic itself locks up the keyboard.Hmmm, in SuSE 9.3 there was a bug in mkinitrd that would insert a splash screen in initrd that would cause dom0 to crash when loading initrd. I thought it was corrected in SuSE 10.0, at least I don''t remember if I had to tune initrd myself in SuSE 10.0. Anyway, you can try the following: - Boot with the default kernel (not XEN); - Build a custom initrd without the splash screen: mkinitrd -k vmlinuz-2.6.13-15.7-xen -i initrd-xen.custom -s 0 This will a initrd without the splash screen (it wouldn''t be used with the xen kernel anyway). If you want to tweak the list of modules that will be included you can edit the parameter INITRD_MODULES in /etc/sysconfig/kernel before running mkinitrd. Then edit /boot/grub/menu.lst and change the initrd line accordingly. BTW, you may also want to run SuSEconfig, since it does some verifications and cleanup. Reboot into the xen kernel. I hope that it works. rgrds, Braulio Gergull _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Lars Braeuer
2006-Feb-10 10:38 UTC
Re: [Xen-users] No network connectivity for domU in SuSE 10, Xen 3
Hi Braulio, yesterday there''s been a new update to kernel-xen-2.6.13-15.8 / xen-3.0_8259-0.1 fixing a few problems. Now it''s working fine. I don''t think the splash screen problem is still present, because I didn''t have to fix the first initrd. Thanks, Lars Bráulio Gergull wrote:> Hi Lars, > > On Feb 09, 2006 01:08 PM, Lars Braeuer <lbraeuer@mpex.net> wrote: > > >>Hi Braulio, >> >>thanks for the tip. After the update the system hangs with a kernel >>panic, right after the (XEN) >>stuff on top. >>Can''t exactly tell what it is, because the output of the kernel panic >>fills the screen >>an the panic itself locks up the keyboard. > > > Hmmm, in SuSE 9.3 there was a bug in mkinitrd that would insert a splash > screen in initrd that would cause dom0 to crash when loading initrd. I > thought it was corrected in SuSE 10.0, at least I don''t remember if I > had to tune initrd myself in SuSE 10.0. > > Anyway, you can try the following: > > - Boot with the default kernel (not XEN); > > - Build a custom initrd without the splash screen: > > mkinitrd -k vmlinuz-2.6.13-15.7-xen -i initrd-xen.custom -s 0 > > This will a initrd without the splash screen (it wouldn''t be used with > the xen kernel anyway). > > If you want to tweak the list of modules that will be included you can > edit the parameter INITRD_MODULES in /etc/sysconfig/kernel before > running mkinitrd. > > Then edit /boot/grub/menu.lst and change the initrd line accordingly. > > BTW, you may also want to run SuSEconfig, since it does some > verifications and cleanup. > > Reboot into the xen kernel. > > I hope that it works. > > rgrds, > Braulio Gergull > > > _______________________________________________ > 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