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

Mike McClurg mike.mcclurg at gmail.com
Thu Dec 22 10:39:22 UTC 2011


On Thu, Dec 22, 2011 at 4:27 AM, Thomas Goirand <thomas at goirand.fr> wrote:
> On 12/22/2011 05:13 AM, Jonathan Ludlam wrote:
>> I think that the mechanism to disable xend via /etc/default/xen hasn't
>> been uploaded yet;
>
> It has! That's how I switch from xm to xl on my SID box.
>
>> it's in xen-utils-common_4.1.2-2.
>
> 4.1.2-1 has it too.
>

We're developing on Ubuntu right now, and it looks like
xen-utils-common-4.1.0~rc6-1ubuntu1 is the latest we have. I'd like
our solution to work on both systems, so that we have to make minimal
changes between the debian and ubuntu packages. I had considered
checking for the pid file, but wasn't sure if that was the best way to
do it. If you think it is, I'll modify that pull request.

After doing some checking, though, I'm not sure that completely
disabling xend is the right thing to do. I took a look at the xend
init script, and it does more than start xend. It's also responsible
for starting xenstored and xenconsoled, which we need. It seems like
the best thing to do might actually be to have xcp-xapi.init shut down
xend, instead of failing to run if xend.pid is present. The other
option is to reimplement xend.init's functionality in xcp-xapi.init,
but I'm not sure we want that responsibility.

So, what do you guys think?



More information about the Pkg-xen-devel mailing list