[Pkg-xen-devel] xen-api: xcp-xapi.init conflicts with xend

[Jonathan Ludlam]

I think that the mechanism to disable xend via /etc/default/xen hasn't been uploaded yet; it's in xen-utils-common_4.1.2-2. IIRC there were a couple of things that needed fixing; the creation of /var/lib/xen and an overhaul of the xendomains init script. 

Jon

I believe there was some work to do
On 21 Dec 2011, at 20:35, Thomas Goirand wrote:

> On 12/22/2011 01:37 AM, Mike McClurg wrote:
>> Hi Thomas, Jon,
>> 
>> I was hoping that you could both comment on this github pull request:
>> 
>> https://github.com/jonludlam/xen-api/pull/12
>> 
>> Mike
>> 
> 
> In Debian, /etc/default/xen is there to select xm vs xl. So we could do:
> 
> if ! [ -f /etc/default/xen ] ; then
> 	TOOLSTACK=xm
> else
> 	. /etc/default/xen
> 	if ! [ "x${TOOLSTACK}" = "xxl" ] ; then
> 		TOOLSTACK=xm
> 	fi
> fi
> 
> if ! [ ${TOOLSTACK} = "xl" ] ; then
> 	log_failure_msg "Please configure /etc/default/xen to use xl"
> 	exit 1
> fi
> 
> I think it's also good to check for a xend instance, but I'd rather
> advocate for doing this:
> 
> # Exit with failure if xend is running
> if [ -f /var/run/xend.pid ] ; then
> 	log_failure_msg "xend.pid found, XCP conflicts with xend"
> 	exit 1
> fi
> 
> By the way, I was thinking, would you like me to add a debconf question
> like this:
> 
> Template: xen/xl_toolstack
> Type: select
> Choices: xm, xl
> _Description: Xen tool stack to use:
> Xen offers 2 types of command line interface to start and stop virtual
> machines. xm is the old one, while xl is the new way using the Xen Light
> library.
> .
> If you intend to use Xen together with the Xen Cloud Platform API
> (xcp-api) package, then you must choose xl.
> 
> That would of course control what's in /etc/default/xen
> 
> Thomas