From: Nivedita Singhvi <niv@us.ibm.com>
To: Xin Zhao <zhaoxin@eecs.umich.edu>
Cc: xen-devel@lists.xensource.com, Ewan Mellor <ewan@xensource.com>
Subject: Re: Lost connection after upgrading to latest xen-unstable
Date: Tue, 01 Nov 2005 13:23:27 -0800 [thread overview]
Message-ID: <4367DCCF.8060709@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0511011608120.26892@willow.eecs.umich.edu>
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
>
>
next prev parent reply other threads:[~2005-11-01 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 19:42 Lost connection after upgrading to latest xen-unstable Xin Zhao
2005-11-01 20:11 ` Ewan Mellor
2005-11-01 21:10 ` Xin Zhao
2005-11-01 21:23 ` Nivedita Singhvi [this message]
2005-11-02 3:34 ` Xin Zhao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4367DCCF.8060709@us.ibm.com \
--to=niv@us.ibm.com \
--cc=ewan@xensource.com \
--cc=xen-devel@lists.xensource.com \
--cc=zhaoxin@eecs.umich.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.