Lost connection after upgrading to latest xen-unstable

Lost connection after upgrading to latest xen-unstable

[Xin Zhao]

Hi,

I upgrade my xen to latest changeset of xen-unstable with 2.6.12.6 kernel.
After that, one of my network interface stop working.

I have two interfaces: eth0 has public IP: 141.213.X.X, eth1 has
internal IP: 192.168.0.1

I set the IP address of my DomU as 192.168.0.188.

Before this upgrade, eth1 can talk to domU without any problem. But now
eth1 stop working. It cannot talk to domU, nor to other machines on the
192.168.0.* network.

Here is the result of "ifconfig", I noticed that eth1 had no IP address.
Instead, 12.168.0.1 is specified to veth0, is this normal?

Thanks in advance for help!

Xin

/*****************************************************************/
th0      Link encap:Ethernet  HWaddr 00:0D:56:2A:23:F7
          inet addr:141.213.10.110  Bcast:141.213.10.255
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2122 errors:0 dropped:0 overruns:0 frame:0
          TX packets:851 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:184054 (179.7 KiB)  TX bytes:99457 (97.1 KiB)
          Base address:0xdf40 Memory:fcde0000-fce00000

eth1      Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:50 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18288025 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7768 (7.5 KiB)  TX bytes:768103047 (732.5 MiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2072 (2.0 KiB)  TX bytes:2072 (2.0 KiB)

veth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.255
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:87224125 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:3663413250 (3.4 GiB)

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:87257124 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:3664799208 (3.4 GiB)  TX bytes:0 (0.0 b)

vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          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:87272099 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

xen-br0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:87287099 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:2444038772 (2.2 GiB)  TX bytes:0 (0.0 b)

Re: Lost connection after upgrading to latest xen-unstable

[Ewan Mellor]

On Tue, Nov 01, 2005 at 02:42:07PM -0500, Xin Zhao wrote:

> Hi,
> 
> I upgrade my xen to latest changeset of xen-unstable with 2.6.12.6 kernel.
> After that, one of my network interface stop working.
> 
> I have two interfaces: eth0 has public IP: 141.213.X.X, eth1 has
> internal IP: 192.168.0.1
> 
> I set the IP address of my DomU as 192.168.0.188.
> 
> Before this upgrade, eth1 can talk to domU without any problem. But now
> eth1 stop working. It cannot talk to domU, nor to other machines on the
> 192.168.0.* network.
> 
> Here is the result of "ifconfig", I noticed that eth1 had no IP address.
> Instead, 12.168.0.1 is specified to veth0, is this normal?

How are you configuring your network?  In other words, what are your settings
for network-script and vif-script in /etc/xen/xend-config.sxp, and what is the
configuration of the network before xend runs?

Ewan.

Re: Lost connection after upgrading to latest xen-unstable

[Xin Zhao]

I left it as default, which is listed as follows:

(network-script    network)  <--------------------------------
# The default bridge that virtual interfaces should be connected to.
(vif-bridge        xen-br0)
# The default script used to control virtual interfaces.
(vif-script        vif-bridge) <------------------------------

in network file, I have :

#netdev=${netdev:-veth0}
netdev=${netdev:-eth1}

Do I need to change something?

Thanks in advance!

Xin



On Tue, 1 Nov 2005, Ewan Mellor wrote:

> On Tue, Nov 01, 2005 at 02:42:07PM -0500, Xin Zhao wrote:
>
> > Hi,
> >
> > I upgrade my xen to latest changeset of xen-unstable with 2.6.12.6 kernel.
> > After that, one of my network interface stop working.
> >
> > I have two interfaces: eth0 has public IP: 141.213.X.X, eth1 has
> > internal IP: 192.168.0.1
> >
> > I set the IP address of my DomU as 192.168.0.188.
> >
> > Before this upgrade, eth1 can talk to domU without any problem. But now
> > eth1 stop working. It cannot talk to domU, nor to other machines on the
> > 192.168.0.* network.
> >
> > Here is the result of "ifconfig", I noticed that eth1 had no IP address.
> > Instead, 12.168.0.1 is specified to veth0, is this normal?
>
> How are you configuring your network?  In other words, what are your settings
> for network-script and vif-script in /etc/xen/xend-config.sxp, and what is the
> configuration of the network before xend runs?
>
> Ewan.
>

Re: Lost connection after upgrading to latest xen-unstable

[Nivedita Singhvi]

Xin Zhao wrote:
> I left it as default, which is listed as follows:
> 
> (network-script    network)  <--------------------------------
> # The default bridge that virtual interfaces should be connected to.
> (vif-bridge        xen-br0)
> # The default script used to control virtual interfaces.
> (vif-script        vif-bridge) <------------------------------

This is very old.  Make sure you copy over the scripts
from the source tree (../tools/examples/) to your /etc/xen/ and
/etc/xen/scripts directory.

thanks,
Nivedita


> in network file, I have :
> 
> #netdev=${netdev:-veth0}
> netdev=${netdev:-eth1}
> 
> Do I need to change something?
> 
> Thanks in advance!
> 
> Xin
> 
> 
> 
> On Tue, 1 Nov 2005, Ewan Mellor wrote:
> 
> 
>>On Tue, Nov 01, 2005 at 02:42:07PM -0500, Xin Zhao wrote:
>>
>>
>>>Hi,
>>>
>>>I upgrade my xen to latest changeset of xen-unstable with 2.6.12.6 kernel.
>>>After that, one of my network interface stop working.
>>>
>>>I have two interfaces: eth0 has public IP: 141.213.X.X, eth1 has
>>>internal IP: 192.168.0.1
>>>
>>>I set the IP address of my DomU as 192.168.0.188.
>>>
>>>Before this upgrade, eth1 can talk to domU without any problem. But now
>>>eth1 stop working. It cannot talk to domU, nor to other machines on the
>>>192.168.0.* network.
>>>
>>>Here is the result of "ifconfig", I noticed that eth1 had no IP address.
>>>Instead, 12.168.0.1 is specified to veth0, is this normal?
>>
>>How are you configuring your network?  In other words, what are your settings
>>for network-script and vif-script in /etc/xen/xend-config.sxp, and what is the
>>configuration of the network before xend runs?
>>
>>Ewan.
>>
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 

Re: Lost connection after upgrading to latest xen-unstable

[Xin Zhao]

I copied new scripts, but still no go. eth0 works just fine, but eth1 does
not work at all. Actually, even before I start xend, I cannot access
192.168.0.* machine via eth1.

Any further advice?

Thanks,
Xin

On Tue, 1 Nov 2005, Nivedita Singhvi wrote:

> Xin Zhao wrote:
> > I left it as default, which is listed as follows:
> >
> > (network-script    network)  <--------------------------------
> > # The default bridge that virtual interfaces should be connected to.
> > (vif-bridge        xen-br0)
> > # The default script used to control virtual interfaces.
> > (vif-script        vif-bridge) <------------------------------
>
> This is very old.  Make sure you copy over the scripts
> from the source tree (../tools/examples/) to your /etc/xen/ and
> /etc/xen/scripts directory.
>
> thanks,
> Nivedita
>
>
> > in network file, I have :
> >
> > #netdev=${netdev:-veth0}
> > netdev=${netdev:-eth1}
> >
> > Do I need to change something?
> >
> > Thanks in advance!
> >
> > Xin
> >
> >
> >
> > On Tue, 1 Nov 2005, Ewan Mellor wrote:
> >
> >
> >>On Tue, Nov 01, 2005 at 02:42:07PM -0500, Xin Zhao wrote:
> >>
> >>
> >>>Hi,
> >>>
> >>>I upgrade my xen to latest changeset of xen-unstable with 2.6.12.6 kernel.
> >>>After that, one of my network interface stop working.
> >>>
> >>>I have two interfaces: eth0 has public IP: 141.213.X.X, eth1 has
> >>>internal IP: 192.168.0.1
> >>>
> >>>I set the IP address of my DomU as 192.168.0.188.
> >>>
> >>>Before this upgrade, eth1 can talk to domU without any problem. But now
> >>>eth1 stop working. It cannot talk to domU, nor to other machines on the
> >>>192.168.0.* network.
> >>>
> >>>Here is the result of "ifconfig", I noticed that eth1 had no IP address.
> >>>Instead, 12.168.0.1 is specified to veth0, is this normal?
> >>
> >>How are you configuring your network?  In other words, what are your settings
> >>for network-script and vif-script in /etc/xen/xend-config.sxp, and what is the
> >>configuration of the network before xend runs?
> >>
> >>Ewan.
> >>
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> >
> >
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>