[Pkg-xen-devel] Bug#655301: Bug#655301: Bug#655301: Bug#655301: Bug#655301: xcp-xapi fails to start

[Mike McClurg]

On Tue, Jan 17, 2012 at 6:47 AM, Ritesh Raj Sarraf <rrs at debian.org> wrote:
> On 01/17/2012 02:26 AM, Thomas Goirand wrote:
>>> >
>>> > Interestingly there's nothing under /proc/xen.
>> The /etc/init.d/xend init script should have mount xenfs for you. Try to
>> restart it by hand, and see if it does it. xenfs and xen-evtchn modules
>> are also loaded by this init script. Can you also check if they are
>> loaded? If they aren't loaded after doing a /etc/init.d/xend start, then
>> you got an issue here, which really, has nothing to do with XCP.
>
> Yes, running xend mounts /proc/xen.
>
> But the problem is, xcp-xapi wants to have xend disabled.
>
> # Exit with failure if xend is running
> if [ -f /var/run/xend.pid ]; then
>        log_failure_msg "/var/run/xend.pid exists; ${NAME} conflicts
> with xend"
>        exit 1
> fi
>
>
> So I disabled the xend init file and then ran into this problem. If I
> run xapi with xend enabled, I get the expected err msg.
>
> lnx200-39:~# ls /proc/xen/
> capabilities  privcmd  xenbus  xsd_kva  xsd_port
> lnx200-39:~# /etc/init.d/xcp-xapi start
> /var/run/xend.pid exists; xapi conflicts with xend ... failed!
>

Hi Ritesh,

We're in a bit of a bind with the xend init script. Xapi depends on
most of the init script being run (as you've seen), but xend itself
conflicts with xapi. We need to come up with a good solution to this
conflict.

I think it would be best if we could create a file /etc/default/xen
that would let us switch between the xm, xl and xapi toolstacks. Until
then, do you think it would be best to copy the required parts of
xend.init into xcp-xapi.init? Are there any other solutions that we're
overlooking?

Mike