All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
To: brianw@terrabox.com
Cc: Xen Devel Mailing List <xen-devel@lists.sourceforge.net>,
	Ian.Pratt@cl.cam.ac.uk
Subject: Re: network access disappears in master on /etc/init.d/xend start
Date: Sun, 21 Nov 2004 20:39:07 +0000	[thread overview]
Message-ID: <E1CVyUG-000655-00@mta1.cl.cam.ac.uk> (raw)
In-Reply-To: Your message of "Sun, 21 Nov 2004 14:22:21 CST." <1101068541.3664.20.camel@enigma.office.terrabox.com>

> Disable ipv6 before you start up xend. As ian said in another email, the
> xend scripts will reliably choke on the ipv6 addrs. 8-P

It's probably trivial to fix. If someone posts the output of
running /etc/xen/scripts/network with 'bash -x' it'll probably be
obvious what the problems is.

Ian


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-11-21 20:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-21 11:59 network access disappears in master on /etc/init.d/xend start Luke Kenneth Casson Leighton
2004-11-21 13:37 ` Vitez Gabor
2004-11-21 15:03   ` Luke Kenneth Casson Leighton
2004-11-21 20:22   ` Brian Wolfe
2004-11-21 20:39     ` Ian Pratt [this message]
2004-11-22  6:50       ` Brian Wolfe
2004-12-09 21:48         ` Error checking for networking issues in xend suggested Jared Rhine
2004-11-21 13:39 ` network access disappears in master on /etc/init.d/xend start Christian Limpach
2004-11-21 15:02   ` Luke Kenneth Casson Leighton
2004-11-21 15:19   ` Luke Kenneth Casson Leighton
2004-11-21 16:05     ` 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=E1CVyUG-000655-00@mta1.cl.cam.ac.uk \
    --to=ian.pratt@cl.cam.ac.uk \
    --cc=brianw@terrabox.com \
    --cc=xen-devel@lists.sourceforge.net \
    /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.