All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Coss <mjcoss@alcatel-lucent.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: issues with running xend init.d script
Date: Mon, 14 Sep 2009 18:00:24 -0400	[thread overview]
Message-ID: <4AAEBCF8.8000203@alcatel-lucent.com> (raw)

Not sure that this is the correct place to post this but when I tried to 
start xend from the init.d directory, I ran into 2 problems. 

The first issue was that xend wants to check the Xen is running, and 
does that by checking /proc/xen/capabilities, which requires xenfs to be 
mounted.  It was not in the fstab, and so wasn't mounted.  This should 
probably should be in the install setup somewhere, or maybe the first 
time the xend is run, it checks to see if it's mounted and if it isn't 
tries to mounts it and adds an entry to fstab if successful. 

The second issue was that the script network-bridge didn't handle my 
network interfaces properly.  I tracked down the problem to the fact 
that the script, in the function get_ip_info() uses "ip addr show dev" 
to get the ip address and broadcast address.  Unfortunately on my 
machine, I have ipv6 configured, and so there is a second inet line for 
the link local ipv6 address.  As a temporary hack, I added "scope 
global" to the ip command, and the network is setup albeit without 
ipv6.  This certainly isn't a real fix, but does fix the case where the 
ipv6 is only a local address.

---Michael J Coss

             reply	other threads:[~2009-09-14 22:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14 22:00 Michael J Coss [this message]
2009-09-17 14:09 ` issues with running xend init.d script Ian Jackson
2009-09-17 15:13   ` Boris Derzhavets

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=4AAEBCF8.8000203@alcatel-lucent.com \
    --to=mjcoss@alcatel-lucent.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.