search for: xendomains_auto_on

...especially for some HVM domains which MUST be saved instead of shut down, it affects also the wished migration of the domain to another machine, etc. The error code is in the beginning of the loop in the stop() procedure: stop() { # Collect list of domains to shut down if test "$XENDOMAINS_AUTO_ONLY" = "true"; then rdnames fi echo -n "Shutting down Xen domains:" while read LN; do parseln "$LN" if test $id = 0; then continue; fi echo -n " $name" if test "$XENDOMAINS_AUTO_ONLY" =...

...especially for some HVM domains which MUST be saved instead of shut down, it affects also the wished migration of the domain to another machine, etc. The error code is in the beginning of the loop in the stop() procedure: stop() { # Collect list of domains to shut down if test "$XENDOMAINS_AUTO_ONLY" = "true"; then rdnames fi echo -n "Shutting down Xen domains:" while read LN; do parseln "$LN" if test $id = 0; then continue; fi echo -n " $name" if test "$XENDOMAINS_AUTO_ONLY" =...

I''ve migrated my Dom0 host to Xen 4.2.0 + xl toolstack. With ''xm'' toolstack, configs in /etc/xen/auto are autostarted, assuming xend/xendomains services are started. IIUC, when using xl toolstack, those services are not to be started; and, afaict, the installation process for 4.2 has them disabled by default. Now, the configs in /etc/xen/auto are simply ignored. I

...hanged: XENDOMAINS_SYSRQ="" XENDOMAINS_USLEEP=100000 XENDOMAINS_CREATE_USLEEP=5000000 XENDOMAINS_MIGRATE="" XENDOMAINS_SAVE="" XENDOMAINS_SHUTDOWN="--wait" XENDOMAINS_SHUTDOWN_ALL="--all --wait" XENDOMAINS_RESTORE=false XENDOMAINS_AUTO=/etc/xen/auto XENDOMAINS_AUTO_ONLY=true XENDOMAINS_STOP_MAXWAIT=300 /etc/init.d/xendomains changed: . /etc/xen/scripts/hotplugpath.sh CMD=${SBINDIR}/xm HEADCOMP="LinuxGuestRecord" $CMD list &> /dev/null if test $? -ne 0 then CMD=${SBINDIR}/xl HEADCOMP="Xen saved domain" fi $CMD list &> /dev/nul...

...anged: XENDOMAINS_SYSRQ="" XENDOMAINS_USLEEP=100000 XENDOMAINS_CREATE_USLEEP=5000000 XENDOMAINS_MIGRATE="" XENDOMAINS_SAVE= XENDOMAINS_SHUTDOWN="--halt --wait" XENDOMAINS_SHUTDOWN_ALL="--all --halt --wait" XENDOMAINS_RESTORE=true XENDOMAINS_AUTO=/etc/xen/auto XENDOMAINS_AUTO_ONLY=false XENDOMAINS_STOP_MAXWAIT=300 /etc/xen/xend-config.sxp changed: (network-script network-bridge) (vif-script vif-bridge) (dom0-min-mem 196) (enable-dom0-ballooning yes) (total_available_memory 0) (dom0-cpus 0) (vncpasswd '') -- no debconf information -- The Sunday Times Scottish...

...MAINS_SYSRQ="" XENDOMAINS_USLEEP=100000 XENDOMAINS_CREATE_USLEEP=5000000 XENDOMAINS_MIGRATE="" XENDOMAINS_SAVE="" XENDOMAINS_SHUTDOWN="--halt --wait" XENDOMAINS_SHUTDOWN_ALL="--all --halt --wait" XENDOMAINS_RESTORE=true XENDOMAINS_AUTO=/etc/xen/auto XENDOMAINS_AUTO_ONLY=false XENDOMAINS_STOP_MAXWAIT=20 /etc/xen/xend-config.sxp changed: (xend-unix-server yes) (vif-script vif-bridge) (dom0-min-mem 196) (enable-dom0-ballooning yes) (total_available_memory 0) (dom0-cpus 0) (vnc-listen '0.0.0.0') (vncpasswd '') -- no debconf information

...DER" = "Xen saved domain" ]; then echo -n " ${dom##*/}" XMR=`$CMD restore $dom 2>&1 1>/dev/null` #$CMD restore $dom @@ -365,11 +365,11 @@ echo -n " $name" if test "$XENDOMAINS_AUTO_ONLY" = "true"; then eval " - case \"\$name\" in - ($NAMES) + case \"$name\" in + $NAMES) # nothing ;; - (*) + *)...

[This email is either empty or too large to be displayed at this time]

hi folks, after long trying i need some help from the big world :-) question ******** when I boot a guest system, tried debian 6.0.2 amd64 firmware, I get errors like: 1) after click install on debian 6.0.2 installer [0.642450] vbd vbd-5632: 19 xenbus_dev_probe on device/vbd/5632 [0.642911] vbd vbd-5632: failed to write error node for device/vbd/5632 (19 xenbus_dev_probe on device/vbd/5632) 2)

hi folks, after long trying i need some help from the big world :-) question ******** when I boot a guest system, tried debian 6.0.2 amd64 firmware, I get errors like: 1) after click install on debian 6.0.2 installer [0.642450] vbd vbd-5632: 19 xenbus_dev_probe on device/vbd/5632 [0.642911] vbd vbd-5632: failed to write error node for device/vbd/5632 (19 xenbus_dev_probe on device/vbd/5632) 2)