WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Network card not available in domU

To: "'xen-users@xxxxxxxxxxxxxxxxxxx'" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Network card not available in domU
From: "Carleski, Benjamin" <benjamin.carleski@xxxxxxxxxxxxxxxxx>
Date: Thu, 4 May 2006 16:53:35 -0700
Delivery-date: Thu, 04 May 2006 16:54:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I am running Xen 3.0.2.  I am able to boot into Xen, and can use the network
fine from dom0, but when I create a domU, there is no network set up.  I
have not modified the network-bridge, vif-bridge, or xend-config.sxp.  I am
running this on a SuSE 10 install, with all the updates from Yast Online
Updates installed.  The SuSE kernel is 2.6.13-15.8-smp.  When I try to
install Xen using the SuSE packages, I get a hypervisor error anytime I
start up our Java application.  When I submitted a bug report for this, I
was told that it was a known bug that was fixed in Xen 3.0.2.  I then tried
applying 3.0.2 on top of my current SuSE install, and was not able to access
the network from within the domU.  I could access the network just fine from
dom0 however.  I then tried a fresh install of SuSE 10, without any SuSE Xen
packages.  I did the YOU update just like before, and then installed 3.0.2
on top of that.  Same problem, I could create a domU, and boot fine into it,
but I couldn't access the network from within the domU, and could access it
fine from the dom0.


I am using the following configuration file for domU.  I have tried both
explicitly specifying the MAC address and bridge in the vif command, as well
as shown below.
---------------------------
--------------------------------------------------------
----------------------------------------------------------------------------
#  -*- mode: python; -*-
kernel = "/boot/vmlinuz-xen"
ramdisk = "/boot/initrd-xen"
memory = 1984
name = "ISPECTRUMUI2"
vcpus = 2

disk = [ 'phy:vg01/vserver2,sda1,w' ]
vif = [ '' ]
#dhcp="dhcp"
ip="192.168.253.232"
netmask="255.255.255.0"
gateway="192.168.253.164"
hostname= "ispectrum-ui2"

root = "/dev/sda1"
extra ="3"
----------------------------------------------------------------------------
--------------------------------------------------------
---------------------------


When I start the domain, I receive the following boot messages
(abbreviated):
---------------------------
--------------------------------------------------------
----------------------------------------------------------------------------
Bootdata ok (command line is 
ip=192.168.253.232:1.2.3.4:192.168.253.164:255.255.255.0:ispectrum-ui2:eth0:
off
root=/dev/sda1 3)
Kernel command line: 
ip=192.168.253.232:1.2.3.4:192.168.253.164:255.255.255.0:ispectrum-ui2:eth0:
off
root=/dev/sda1 3
NET: Registered protocol family 16
netfront: Initialising virtual ethernet driver.
NET: Registered protocol family 2
IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Setting up hostname 'ispectrum-ui2'                                   done
Setting up loopback interface     lo
    lo        IP address: 127.0.0.1/8
                                                                      done
Setting current sysctl status from /etc/sysctl.conf
net.ipv4.icmp_echo_ignore_broadcasts = 1
net.ipv4.conf.all.rp_filter = 1
                                                                      done
Enabling syn flood protection                                         done
Disabling IP forwarding                                               done
                                                                      done
NET: Registered protocol family 10
Welcome to SUSE LINUX 10.0 (X86-64) - Kernel 2.6.16-xen (tty1).
----------------------------------------------------------------------------
--------------------------------------------------------
---------------------------



When I run ifconfig and try to ping from within the domU, these are the
results I get:
---------------------------
--------------------------------------------------------
----------------------------------------------------------------------------
ispectrum-ui2:~ # ping 192.168.253.230
connect: Network is unreachable
ispectrum-ui2:~ # ifconfig
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)
----------------------------------------------------------------------------
--------------------------------------------------------
---------------------------


I get the following messages when checking the network status from dom0
---------------------------
----------------------------------------------------------
----------------------------------------------------------------------------
peterrabbit:~ # xm vnet-list
Error: method "xend_vnets" is not supported
peterrabbit:~ # /etc/xen/scripts/network-bridge status
============================================================
3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether 00:14:22:b1:7f:6e brd ff:ff:ff:ff:ff:ff
    inet 192.168.253.230/24 brd 192.168.253.255 scope global eth0
    inet6 fe80::214:22ff:feb1:7f6e/64 scope link
       valid_lft forever preferred_lft forever
21: xenbr0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
    inet6 fe80::200:ff:fe00:0/64 scope link
       valid_lft forever preferred_lft forever

bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              vif0.0
                                                        peth0
                                                        vif2.0

192.168.253.0/24 dev eth0  proto kernel  scope link  src 192.168.253.230
169.254.0.0/16 dev eth0  scope link
127.0.0.0/8 dev lo  scope link
default via 192.168.253.164 dev eth0

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.253.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
0.0.0.0         192.168.253.164 0.0.0.0         UG    0      0        0 eth0
============================================================
peterrabbit:~ # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:14:22:B1:7F:6E
          inet addr:192.168.253.230  Bcast:192.168.253.255
Mask:255.255.255.0
          inet6 addr: fe80::214:22ff:feb1:7f6e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4274 errors:0 dropped:0 overruns:0 frame:0
          TX packets:971 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:293432 (286.5 Kb)  TX bytes:117711 (114.9 Kb)

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)

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:4258 errors:0 dropped:0 overruns:0 frame:0
          TX packets:970 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:311993 (304.6 Kb)  TX bytes:121645 (118.7 Kb)
          Base address:0xdcc0 Memory:fe7e0000-fe800000

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:971 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4278 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:117711 (114.9 Kb)  TX bytes:293740 (286.8 Kb)

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 MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:3578 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  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:3306 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:166399 (162.4 Kb)  TX bytes:468 (468.0 b)
----------------------------------------------------------------------------
--------------------------------------------------------
---------------------------

Benjamin R. Carleski
Software Engineer
Summit Information Systems
541.758.5899 x6240


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Network card not available in domU, Carleski, Benjamin <=