Re: [Xen-devel] Lost connection after upgrading to latest xen-unstable

[Xin Zhao <zhaoxin@xxxxxxxxxxxxxx>]

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@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> >
> >
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

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