search for: xenstored_args

...t;$USER_XENSTORED" ]; then > + log_failure_msg "Failed to start $USER_XENSTORED: no such executable." > + return 2 > + else > + start-stop-daemon --start --quiet \ > + --pidfile "$XENSTORED_PIDFILE" --exec "$USER_XENSTORED" -- \ > + $XENSTORED_ARGS --pid-file="$XENSTORED_PIDFILE" > + if [ $? -ne 0 ]; then > + return 2 > + fi > + fi > + else > + for try_xenstored in "$OXENSTORED" "$CXENSTORED"; do > + if [ -x $try_xenstored ]; then > + start-stop-daemon --start --quiet \ >...

Currently PVHVM Linux guests after ddacf5ef684a "xen/pv-on-hvm kexec: add xs_reset_watches to shutdown watches from old kernel" hang when run against oxenstored because it does not handle the unknown XS_RESET_WATCHES operation and does not reply. The symptom of this issue is a hang during boot at this point: cpu 1 spinlock event irq 70 CPU 1 irqstacks, hard=dec94000

...runtime. See diff [1] for details. Also, I think xenstored should write a pidfile. You might consider adding to /usr/lib/systemd/system/xenstored.service: PIDFile=/var/run/xenstored.pid and change ExecStart=/usr/sbin/xenstored to ExecStart=/usr/sbin/xenstored --pid-file /var/run/xenstored.pid $XENSTORED_ARGS Hope this helps, this is just a quick start. I'll continue checking and reporting during the next days. Regards, Thomas [1] diff -u rpmbuild-xen-4.6rc2x-3.el7-org/SPECS/xen.spec rpmbuild-xen-4.6rc2x-3.el7/SPECS/xen.spec --- rpmbuild-xen-4.6rc2x-3.el7-org/SPECS/xen.spec 2015-09-08 18:4...

The contents are the wip.testme branch currently on salsa. I combined the wip.initscript and wip.oxenstored into this and added more things today. I think this is pretty gtg and it's smoke tested (in several cases by scping files around instead of doing package build), so it needs a final extra review and test round before putting it in master branch (which I don't want to force push). I

...R" ] || mkdir -p "$XENSTORED_DIR" + [ -x /sbin/restorecon ] && /sbin/restorecon "$XENSTORED_DIR" export XENSTORED_ROOTDIR="$XENSTORED_DIR" start-stop-daemon --start --quiet --pidfile "$XENSTORED_PIDFILE" --exec "$XENSTORED" -- \ $XENSTORED_ARGS --pid-file="$XENSTORED_PIDFILE" \ -- System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale:...

...> Also, I think xenstored should write a pidfile. You might consider adding to > /usr/lib/systemd/system/xenstored.service: > PIDFile=/var/run/xenstored.pid > and change > ExecStart=/usr/sbin/xenstored > to > ExecStart=/usr/sbin/xenstored --pid-file /var/run/xenstored.pid > $XENSTORED_ARGS > > Hope this helps, this is just a quick start. I'll continue checking and > reporting during the next days. I think because systemd doesn't do forking, that it doesn't need a pidfile. In fact, if xenstored detects that it's running under systemd, it will actually ignore...

...R" ] || mkdir -p "$XENSTORED_DIR" + [ -x /sbin/restorecon ] && /sbin/restorecon "$XENSTORED_DIR" export XENSTORED_ROOTDIR="$XENSTORED_DIR" start-stop-daemon --start --quiet --pidfile "$XENSTORED_PIDFILE" --exec "$XENSTORED" -- \ $XENSTORED_ARGS --pid-file="$XENSTORED_PIDFILE" \ --- /etc/init.d/xendomains.orig 2012-06-24 10:29:08.000000000 +1000 +++ /etc/init.d/xendomains 2012-06-24 10:30:05.000000000 +1000 @@ -152,6 +152,7 @@ { [ -n "$XENDOMAINS_SAVE" ] || return [ -d "$XENDOMAINS_SAVE" ] || mkdir -m 0...

...--pidfile "$XENSTORED_PIDFILE" -- exec "$XENSTORED" --test > /dev/null \ || return 1 [ -d "$XENSTORED_DIR" ] || mkdir -p "$XENSTORED_DIR" start-stop-daemon --start --quiet --pidfile "$XENSTORED_PIDFILE" -- exec "$XENSTORED" -- \ $XENSTORED_ARGS --pid-file="$XENSTORED_PIDFILE" \ || return 2 } case "$1" in start) log_daemon_msg "Starting $DESC" modules_setup [ -x /sbin/restorecon ] && /sbin/restorecon -R /dev xenfs_setup case "$?" in 0) ;; *) log_end_msg 1; exit ;; esac capab...

...ns. * Drop a file in /etc/sysconfig/modules/xen.modules to trigger loading of the backend driver modules. So we have a config file in /etc/sysconfig/modules containing user config options [root@celery console]# cat /etc/sysconfig/xend #XENSTORED_PID="/var/run/xenstore.pid" #XENSTORED_ARGS= # Log all hypervisor messages (cf xm dmesg) #XENCONSOLED_LOG_HYPERVISOR=yes # Log all guest console output (cf xm console) #XENCONSOLED_LOG_GUESTS=yes # Location to store guest & hypervisor logs #XENCONSOLED_LOG_DIR=/var/log/xen/console #XENCONSOLED_ARGS= #BLKTAPCTRL_ARGS=...

...uot;$XENSTORED" --test > /dev/null \ || return 1 [ -d "$XENSTORED_DIR" ] || mkdir -p "$XENSTORED_DIR" export XENSTORED_ROOTDIR="$XENSTORED_DIR" start-stop-daemon --start --quiet --pidfile "$XENSTORED_PIDFILE" --exec "$XENSTORED" -- \ $XENSTORED_ARGS --pid-file="$XENSTORED_PIDFILE" \ || return 2 xenstore-write "/local/domain/0/name" "Domain-0" } case "$1" in start) log_daemon_msg "Starting $DESC" modules_setup xenfs_setup case "$?" in 0) ;; *) log_end_msg 1; exit ;; esac...

You''re right scout the last line. Out looks like xapi is waiting on tapdisk to plug a key into xenstore. Perhaps a udev rule problem? Perhaps someone who knows more about tapdisk than I well be able to diagnose this tomorrow. Mike Sent from Samsung tablet Sébastien RICCIO <sr@swisscenter.com> wrote: Of course, here it is attached. Last line seems interesting. However tapdisk2