ar16 wrote:
> Ooops, sry, cp'd the wrong result. Same result for BOTH Guests, alone.
>
> My point is that in BOTH cases, the single-guest -- whether it's "test1"
> or "test2" -- launches without error.
>
> If BOTH guests are included to auto-launch, then only the one launches
> successfully.
>
Were you using the xl toolstack before the packages were updated?
Do both guests start if you run the xendomains script after boot? I.e.
disable the script from running at boot, then do '/etc/init.d/xendomains
start' after boot.
Your suspicion of systemd might warrent some investigation
# rpm -q xen --changelog | grep -A 7 systemd
- Added support for systemd with the following service files
xenstored.service
blktapctrl.service
xend.service
xenconsoled.service
xen-watchdog.service
xendomains.service
xencommons.service
Perhaps a bit of tweaking on the xendomains script might give some hints
too, e.g.
--- /etc/init.d/xendomains.orig 2013-08-15 11:53:39.487569293 -0600
+++ /etc/init.d/xendomains 2013-08-15 11:54:33.440841893 -0600
@@ -34,7 +34,7 @@
$CMD list &> /dev/null
if test $? -ne 0
then
- CMD=${SBINDIR}/xl
+ CMD=${SBINDIR}/xl -v
HEADCOMP="Xen saved domain"
fi
@@ -297,7 +297,7 @@
if [ $? -eq 0 ] || is_running $dom; then
echo -n "(skip)"
else
- XMC=`$CMD create --quiet --defconfig $dom`
+ XMC=`$CMD create --defconfig $dom`
if [ $? -ne 0 ]; then
echo -e "\nAn error occurred while creating domain
${dom##*/}: $XMC\n"
rc_failed $?
Regards,
Jim
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
