All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Larson <pl@us.ibm.com>
To: Ewan Mellor <ewan@xensource.com>
Cc: Ted Kaczmarek <tedkaz@optonline.net>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Network still broken, new issue as well , 7468:17a9f111fa93
Date: Tue, 25 Oct 2005 17:28:17 -0500	[thread overview]
Message-ID: <435EB181.6000401@us.ibm.com> (raw)
In-Reply-To: <20051025174059.GJ13783@leeni.uk.xensource.com>

Ewan Mellor wrote:
> Regarding your other network problems, if you are still suffering once you've
> changed your configuration, then please submit a full set of logs.  The
> scripts involved have changed recently, as you know, but they are very
> difficult to test, because we don't have a great variation of network
> topologies available.  I'd be looking for
>
> ifconfig
> brctl show
> cat /var/log/syslog
> cat /var/log/debug
> cat /var/log/xend.log
>   
Please see bug #363 that's currently biting several of us with systems 
which, for various reasons, use eth1 instead of eth0.  I hope you don't 
mind, I attached logfiles and command output to the bug rather than 
spamming here with it.  We have always had to workaround this it seems, 
but were hoping the new script would fix it.  Instead, with the new 
script we just had to find a new workaround.

Basicially, on these systems it assumes eth0 (which we don't use), so we 
never get networking on domU.

Thanks,
Paul Larson

  parent reply	other threads:[~2005-10-25 22:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-22  2:26 Network still broken, new issue as well , 7468:17a9f111fa93 Ted Kaczmarek
2005-10-25 17:40 ` Ewan Mellor
2005-10-25 20:52   ` Ted Kaczmarek
2005-10-25 22:28   ` Paul Larson [this message]
2005-10-25 23:01     ` Ewan Mellor
2005-10-26  0:10       ` Michael Lessard
2005-10-26  7:21         ` Ewan Mellor
2005-10-26 12:14           ` Michael Lessard
2005-10-26 12:26             ` Ewan Mellor
2005-10-26 15:35               ` Michael Lessard

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=435EB181.6000401@us.ibm.com \
    --to=pl@us.ibm.com \
    --cc=ewan@xensource.com \
    --cc=tedkaz@optonline.net \
    --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.