From: Tom Wilkie <tw275@cam.ac.uk>
To: Nate Carlson <natecars@natecarlson.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: RE: [PATCH] network -> network-bridge rename WAS: Re: RE: help with bugs
Date: Fri, 05 Aug 2005 16:09:19 +0100 [thread overview]
Message-ID: <42F3811F.2080509@cam.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.61.0508050949280.15712@tungsten.technicality.org>
When I was doing some testing a few weeks ago, I found the network
script would knock out my NFS root for dom 0 when I started xend - this
would in turn hang the machine.
We suspected it was when the routes / addresses got removed from eth0.
We were using some quite new gigabit ethernet cards, ian though it might
be because the promiscuois(?) flag was being lost.
I will do some more testing on this next week, let you know if this is
still the case.
Tom
Nate Carlson wrote:
> On Fri, 5 Aug 2005, Ian Pratt wrote:
>
>> It probably won't if you're using NFS root or anything else fancy, but
>> I still think its worth having.
>
>
> Actually, it does work on NFS root. :)
>
> ------------------------------------------------------------------------
> | nate carlson | natecars@natecarlson.com | http://www.natecarlson.com |
> | depriving some poor village of its idiot since 1981 |
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2005-08-05 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 14:13 [PATCH] network -> network-bridge rename WAS: Re: RE: help with bugs Ian Pratt
2005-08-05 14:49 ` Nate Carlson
2005-08-05 15:09 ` Tom Wilkie [this message]
2005-08-05 18:54 ` Nate Carlson
2005-08-09 13:00 ` Sean Dague
-- strict thread matches above, loose matches on Subject: below --
2005-08-05 15:20 Ian Pratt
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=42F3811F.2080509@cam.ac.uk \
--to=tw275@cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=natecars@natecarlson.com \
--cc=xen-devel@lists.xensource.com \
/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.