Kronos: xcp-xapi.init should conflict with xend

[Mike McClurg]

xend and xapi should not be running at the same time. The xcp-xapi.init file should do one of two things:

1) Kill xend if it finds that xend is running
2) Fail to start if it finds that xend is running

I think that 2 is probably better. We should emit a clear error message if xcp-xapi fails to start because of xend running, and modify our docs to say that we conflict with xend, and that the user should remove xend from startup.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Heling Yao (hyao)]

Just installed xcp-xapi on top of a xen installation, and had to run:
update_rc.d xendomains disable
update-rc.d openvswitch-switch disable (I chose 'bridge' in the post install configuration)

There's the /etc/init.d/xend script, and according to:
Workaround XAPI conflicts with XEND (Debian and Ubuntu)
http://wiki.xen.org/wiki/XCP_toolstack_on_a_Debian-based_distribution

"You will need to disable xend from starting in order to get xcp-xapi to start. This is done by modifying the file at /etc/init.d/xend. Many of the setup processes in this script still need to run, but xend itself should not start. This will be resolved in a future release. The command to resolve this is:
sed -i -e 's/xend_start$/#xend_start/' -e 's/xend_stop$/#xend_stop/' /etc/init.d/xend
update-rc.d xendomains disable"

So we still need to run the xend script with the xend_start lines commented out, and it wouldn't conflict with xcp-xapi service.

[Thomas Goirand (thomas-goirand)]

Hi,

As the maintainer of xen-api in Debian (and therefor in Ubuntu because the package derives from it) I believe that is is up to *you* to decide which of the xen toolstack you want to choose, through /etc/default/xen. By default, Xen is shipped to used xm as a toolstack, and therefor needs to start xend. It should be, IMO, set to xl instead, so that xend wouldn't need to run by default, therefor solving your problem.

Note that in upstream Xen 4.2 (currently available in Debian Experimental thanks to Waldi's awesome work...), xl should even more be set as default toolstack, since they are deprecating xm.

Finally, because of the above, I believe this bug should be reassigned to the Xen hypervisor.

Cheers,

Thomas Goirand (zigo)