On 8/16/2013 at 02:30 PM, in message <520E8BE3.9010302@suse.com>, Jim Fehlig
wrote: ar16 wrote: This is probably the case. xenstored.service must be running before xencommons.service. Since xencommons will start xenstored, we may not need xenstored.service right? It's useful to be able to disable xen guest launching on boot.
Right, that is the default config.
disabling xendomains.service seems a logical way/place to do that.
Right, not enabled out of the box.
if not, &/or you remove it, what't the 'right' way to do it?
I'm not talking about xendomains.service, but xenstored.service. xencommons starts xenstored, so no need to have systemd do that and hence no need for the service file.
We get to pick the 'right' way as upstream has no service files :) Historically, for as long as xencommons existed, it has always started xendomains. I'll experiment without the xendomains.service file and if it seems reasonable, I'll remove it. - Charles -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org