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-bugs

[Xen-bugs] [Bug 632] New: Network interface not available in domU

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 632] New: Network interface not available in domU
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 03 May 2006 09:19:15 -0700
Delivery-date: Wed, 03 May 2006 09:20:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=632

           Summary: Network interface not available in domU
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: major
          Priority: P2
         Component: Hardware Support
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: Benjamin.Carleski@xxxxxxxxxxxxxxxxx


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 using
the following configuration file for domU

--------------------------------------------------------
#  -*- 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, 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 need help on how to configure this system so that I can get a working network
in the domU's.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 632] New: Network interface not available in domU, bugzilla-daemon <=