search for: xenconsoled_arg

...otplug/Linux/init.d/xencommons b/tools/hotplug/Linux/init.d/xencommons index a2e633b..bd15bd4 100644 --- a/tools/hotplug/Linux/init.d/xencommons +++ b/tools/hotplug/Linux/init.d/xencommons @@ -115,11 +115,14 @@ do_start () { echo Starting xenconsoled... test -z "$XENCONSOLED_TRACE" || XENCONSOLED_ARGS=" --log=$XENCONSOLED_TRACE" ${SBINDIR}/xenconsoled --pid-file=$XENCONSOLED_PIDFILE $XENCONSOLED_ARGS - echo Starting QEMU as disk backend for dom0 test -z "$QEMU_XEN" && QEMU_XEN="${LIBEXEC}/qemu-system-i386" - $QEMU_XEN -xen-domid 0 -xen-attach -name dom0...

Package: xen-utils-4.0 Version: 4.0.1-2 Hi, When you change XENCONSOLED_ARGS in /etc/default/xend, there's no normal way to apply it. Even if you do '/etc/init.d/xend stop', that doesn't stop xenconsoled, despite the fact the analogous 'start' action did start it. There isn't even a separate init script action to stop it, it has to be killed man...

Goodmorning, I''m currently playing with XEN/arm on my Allwinner A20 (cubieboard2) I would like to get the XENFB driver working on domU. But currently in xen/arm there''s no support for VFB, atleast qemu is not supported. But this video http://www.youtube.com/watch?v=po1IeElg8tg and this one http://www.youtube.com/watch?v=Km6gBnIqaWo is showing a working framebuffer. So there are

Hello, I want to install a DomU with Fedora 19 in a Debian Host Dom0 with the following versions... ii libc6-xen:i386 2.13-38 i386 Embedded GNU C Library: Shared libraries [Xen version] ii libxen-4.1 4.1.4-3+deb7u1 i386 Public libs for Xen ii libxenstore3.0 4.1.4-3+deb7u1 i386

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: wishlist Hi, this morning I spend some time to find out how to log console output of Xen guest domains into a file in dom0. I ended up using a quick 'n dirty solution: mario:/usr/lib/xen-3.2-1/bin 0-# diff -u xend.orig xend --- xend.orig 2009-03-02 16:49:49.000000000 +0100 +++ xend 2009-03-02 16:16:03.000000000 +0100 @@ -100,7 +100,8 @@

...ess_msg "xenconsoled" start-stop-daemon --start --quiet --pidfile "$XENCONSOLED_PIDFILE" -- exec "$XENCONSOLED" --test > /dev/null \ || return 1 start-stop-daemon --start --quiet --pidfile "$XENCONSOLED_PIDFILE" -- exec "$XENCONSOLED" -- \ $XENCONSOLED_ARGS --pid-file="$XENCONSOLED_PIDFILE" \ || return 2 } xenstored_start() { log_progress_msg "xenstored" start-stop-daemon --start --quiet --pidfile "$XENSTORED_PIDFILE" -- exec "$XENSTORED" --test > /dev/null \ || return 1 [ -d "$XENSTORED_DIR&quot...

...rn 0 } xenconsoled_start_real() { start-stop-daemon --start --quiet --pidfile "$XENCONSOLED_PIDFILE" --exec "$XENCONSOLED" --test > /dev/null \ || return 1 start-stop-daemon --start --quiet --pidfile "$XENCONSOLED_PIDFILE" --exec "$XENCONSOLED" -- \ $XENCONSOLED_ARGS --pid-file="$XENCONSOLED_PIDFILE" \ || return 2 } xenconsoled_stop_real() { start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile "$XENCONSOLED_PIDFILE" --name xenconsoled RETVAL="$?" [ "$RETVAL" = 2 ] && return 2 start-stop-daemon...

...n/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= (This would be /etc/default/xend instead on Debian I believe) When starting, we run all four currently provided Xen daemon processes, list out all daemons being started along the way... [root@celery console]# service xend start Starting xen daemons: xenstored blktapctr...

...rn 0 } xenconsoled_start_real() { start-stop-daemon --start --quiet --pidfile "$XENCONSOLED_PIDFILE" --exec "$XENCONSOLED" --test > /dev/null \ || return 1 start-stop-daemon --start --quiet --pidfile "$XENCONSOLED_PIDFILE" --exec "$XENCONSOLED" -- \ $XENCONSOLED_ARGS --pid-file="$XENCONSOLED_PIDFILE" \ || return 2 } xenconsoled_stop_real() { start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile "$XENCONSOLED_PIDFILE" --name xenconsoled RETVAL="$?" [ "$RETVAL" = 2 ] && return 2 start-stop-daemon...

...rn 0 } xenconsoled_start_real() { start-stop-daemon --start --quiet --pidfile "$XENCONSOLED_PIDFILE" --exec "$XENCONSOLED" --test > /dev/null \ || return 1 start-stop-daemon --start --quiet --pidfile "$XENCONSOLED_PIDFILE" --exec "$XENCONSOLED" -- \ $XENCONSOLED_ARGS --pid-file="$XENCONSOLED_PIDFILE" \ || return 2 } xenconsoled_stop_real() { start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile "$XENCONSOLED_PIDFILE" --name xenconsoled RETVAL="$?" [ "$RETVAL" = 2 ] && return 2 start-stop-daemon...

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