[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



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

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.