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

Re: [Xen-devel] domU networking trouble in Xen 3.0-unstable.hg

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] domU networking trouble in Xen 3.0-unstable.hg
From: "Bryan D. Payne" <bryan@xxxxxxxxxxxx>
Date: Mon, 31 Oct 2005 19:36:02 -0500
Delivery-date: Tue, 01 Nov 2005 00:33:15 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <15D2649C-749D-479F-A20F-2C1B8BF3574D@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <15D2649C-749D-479F-A20F-2C1B8BF3574D@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I have just tried to upgrade to changeset 7572. I discovered that doing a 'make install' after my update blew away my dom0 and domU kernel configs! Unfortunately, I didn't have those saved off anywhere (my mistake), so I have spent the past four hours (and counting...) trying to recreate a working config. I shall save this one when I finally get it working, but I'd like to suggest that perhaps a make install doesn't blow away .config* in the kernel source directories ;-)

Anyway, in the mean time, here's some additional information about my setup before attempting the upgrade.

* When I first posted about this problem I was using changeset 7398.

* The additional network config information that people requested is below:

====================
[root@domU ~]# ip addr show
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
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether aa:00:00:3d:b1:dd brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.12/24 brd 192.168.0.255 scope global eth0
[root@domU ~]# ip route show
192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.12
169.254.0.0/16 dev eth0  scope link
default via 192.168.0.254 dev eth0
[root@domU ~]#

====================
[root@dom0 ~]# ip addr show
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,UP> mtu 1500 qdisc noqueue
    link/ether 00:a0:c9:e3:75:5e brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.11/24 brd 192.168.0.255 scope global eth0
    inet6 fe80::2a0:c9ff:fee3:755e/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: sit0: <NOARP> mtu 1480 qdisc noop
    link/sit 0.0.0.0 brd 0.0.0.0
6: xen-br0: <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
7: vif1.1: <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
[root@dom0 ~]# ip route show
192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.11
169.254.0.0/16 dev eth0  scope link
default via 192.168.0.254 dev eth0
[root@dom0 ~]# brctl show
bridge name     bridge id               STP enabled     interfaces
xen-br0         8000.feffffffffff       no              peth0
                                                        vif0.0
                                                        vif1.1
[root@dom0 ~]#

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>