There's no date defined yet, but Wheezy freeze will happen soon. How do we plan on concluding on this bug report?
Recap for the actual bug I reported: If you want to start xapi, execute
the following steps:
1) Start /etc/init.d/xend
2) Stop /etc/init.d/xend
3) Start /etc/init.d/xcp-xapi
Step 1 is required because you need access to /proc/xen/
Step 2 is required because xapi cannot run while xend daemon is active
With the above 3 steps: I get xapi back and openxenmanager nicely
connect to it. After following this bug report's conversation, I did
notice that I do not have anything in /etc/default/xen.
lnx200-39:/etc/init.d# cat /etc/default/xen
# Configuration for Xen system
# ----------------------------
# There exists several tool stacks to configure a Xen system.
# …
# Attention: You need to reboot after changing this!
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 init script. It determines the TOOLSTACK value right in its script.
Where do we want to fix it?
I have filed bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661687
If that is fixed, as part for xcp post-install, just set
/etc/default/xen to xcp and we should be good.
Okay??? Let's target it for Wheezy
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
signature.asc
Description: OpenPGP digital signature
