search for: xend_start

...p; return 0 log_progress_msg "xenfs" [ -d "/proc/xen" ] || return 1 mount -t xenfs xenfs /proc/xen || return 1 return 0 } capability_check() { [ -e "/proc/xen/capabilities" ] || return 1 grep -q "control_d" /proc/xen/capabilities || return 1 return 0 } xend_start() { log_progress_msg "xend" $XEND status && return 1 $XEND start || return 2 i=0 while [ $i -lt 10 ]; do $XEND status && return 0 || true i=$(($i + 1)) sleep 1 done return 2 } xend_stop() { log_progress_msg "xend" $XEND status || return 0 $XEND st...

...is a patch that demonstrates how to solve this problem. --- xen.old 2014-10-12 17:49:11.348923959 +1100 +++ xen 2014-10-12 17:50:49.257694941 +1100 @@ -66,6 +66,7 @@ [ -d /run/xen ] && return 0 mkdir -m 700 /run/xen + [ -x /sbin/restorecon ] && /sbin/restorecon /run/xen } xend_start() @@ -189,6 +190,7 @@ start-stop-daemon --start --quiet --pidfile "$XENSTORED_PIDFILE" --exec "$XENSTORED" --test > /dev/null \ || return 1 [ -d "$XENSTORED_DIR" ] || mkdir -p "$XENSTORED_DIR" + [ -x /sbin/restorecon ] && /sbin/restorecon &q...

Hi all, Long time no speak. Well, since I''ve chosen to stick with the XML Xen configs; config.sxp, how do I; 1) Have a domain truly shutdown upon xend shutting down (not save state but halt -p). 2) Have certain VMs start before others. Startup is (on-xend_start start) But thats all I could really muster at this point. Thanks in advance, - Brian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Package: xen-utils-common Version: 3.3.1-2 Tags: patch xend_stop currently fails because the script defines $XEND rather than $DAEMON. --- xen-common/debian/xen-utils-common.xend.init +++ xen-common/debian/xen-utils-common.xend.init @@ -49,8 +49,8 @@ xend_start() xend_stop() { - $DAEMON status || return 0 - $DAEMON stop || return 1 + $XEND status || return 0 + $XEND stop || return 1 } xenconsoled_start()

...] || return 1 mount -t xenfs xenfs /proc/xen || return 1 return 0 } capability_check() { [ -e "/proc/xen/capabilities" ] || return 1 grep -q "control_d" /proc/xen/capabilities || return 1 return 0 } env_setup() { [ -d /run/xen ] && return 0 mkdir -m 700 /run/xen } xend_start() { if [ -z "$XEND" ] || [ "$(basename "$TOOLSTACK")" != xm ]; then return 0 fi log_progress_msg "xend" xend_start_real return $? } xend_stop() { if [ -z "$XEND" ] || [ "$(basename "$TOOLSTACK")" != xm ]; then return 0...

...p; return 0 log_progress_msg "xenfs" [ -d "/proc/xen" ] || return 1 mount -t xenfs xenfs /proc/xen || return 1 return 0 } capability_check() { [ -e "/proc/xen/capabilities" ] || return 1 grep -q "control_d" /proc/xen/capabilities || return 1 return 0 } xend_start() { if [ -z "$XEND" ] || [ "$(basename "$TOOLSTACK")" != xm ]; then return 0 fi log_progress_msg "xend" xend_start_real return $? } xend_stop() { if [ -z "$XEND" ] || [ "$(basename "$TOOLSTACK")" != xm ]; then return 0...

...TOOLSTACK= Also with xapi active and running, I get the following from the toolstack command: lnx200-39:/etc/init.d# /usr/lib/xen-common/bin/xen-toolstack /usr/lib/xen-4.1/bin/xm Now in the xend script, I see: TOOLSTACK=$(/usr/lib/xen-common/bin/xen-toolstack 2>/dev/null) and further... xend_start() { if [ -z "$XEND" ] || [ "$(basename "$TOOLSTACK")" != xm ]; then return 0 fi log_progress_msg "xend" Given that, even with xapi enabled, xen-toolstack reports me that the stack is xm. And TOOLSTACK value from /etc/default/xen is not honored by xend ini...