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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Michael J Coss writes ("[Xen-devel] issues with running xend init.d
script"):> 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.
This is now done in xen-unstable''s /etc/init.d/xend. It might be
worth backporting this as evidently people are having trouble with
older trees (I assume you''re on 3.4?)
> 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.
If you''d like to provide a patch for the script, we''d all be
grateful
:-).
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-Sep-17 15:13 UTC
Re: [Xen-devel] issues with running xend init.d script
>This is now done in xen-unstable''s /etc/init.d/xend. It might be >worth backporting this as evidently people are having trouble with >older trees (I assume you''re on 3.4?)Script /etc/init.d/xend in 3.4.1 looks like :- . . . . . . . . /etc/rc.d/init.d/functions if [ ! -d /proc/xen ]; then exit 0 fi if ! grep -q "control_d" /proc/xen/capabilities ; then exit 0 fi ******************** Changeset 20185 ******************** @@ -21,6 +21,15 @@ shopt -s extglob test -f /etc/sysconfig/xend && . /etc/sysconfig/xend + +if test "x$1" = xstart && \ + test -d /proc/xen && \ + ! test -d /proc/xen/capabilities && \ + grep '' xenfs$'' /proc/filesystems >/dev/null && \ + ! grep ''^xenfs '' /proc/mounts >/dev/null; +then + mount -t xenfs xenfs /proc/xen +fi if ! grep -q "control_d" /proc/xen/capabilities ; then exit 0 It seems that some other CSs ( which ones ?) from Xen Unstable have to be backported as well before 20185. Boris. --- On Thu, 9/17/09, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote: From: Ian Jackson <Ian.Jackson@eu.citrix.com> Subject: Re: [Xen-devel] issues with running xend init.d script To: "Michael J Coss" <mjcoss@alcatel-lucent.com> Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com> Date: Thursday, September 17, 2009, 10:09 AM Michael J Coss writes ("[Xen-devel] issues with running xend init.d script"):> 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.This is now done in xen-unstable''s /etc/init.d/xend. It might be worth backporting this as evidently people are having trouble with older trees (I assume you''re on 3.4?)> 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.If you''d like to provide a patch for the script, we''d all be grateful :-). Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel