[kernel-xen] xenconsoled starts twice
glenn at rimuhosting.com
Sun May 18 14:34:45 EST 2014
Yeah xenconsoled is essential. We use xl.
The issue I faced is that there is an init script for it, but there is
also a command to start it in xencommons. I had both enabled in the
startup sequence. If more than one instance is running that confuses
For now I've just explicitly disabled the init script, and let
xencommons take care of it.
See more on our other services at http://ri.mu
On 05/18/2014 02:43 PM, Steven Haigh wrote:
> On 17/05/14 16:13, Steven Haigh wrote:
>> On 16/05/14 13:29, Glenn Enright wrote:
>>> In a the latest release I see multiple messages like this in xm dmesg
>>> every time I start a domain.
>>> (XEN) event_channel.c:233:d0 EVTCHNOP failure: domain 14, error -22
>>> I eventually foind out this was caused by multiple copioes of
>>> xenconsoled running...
>>> root 1485 0.0 0.0 86580 528 ? SLl 01:58 0:00
>>> xenconsoled --pid-file=/var/run/xenconsoled.pid
>>> root 1679 0.0 0.0 86580 488 ? SLl 01:58 0:00
>>> /usr/sbin/xenconsoled --log=none --log-dir=/var/log/xen/console
>>> It looks like one is started by xencommons and one by the actual
>>> xenconsoled init script
>>> clueref: http://lists.xen.org/archives/html/xen-devel/2014-01/msg02460.html
>>> Running '/etc/init.d/xenconsoled stop' solves the unexpected messages.
>>> I'm not sure if this is a bug in the package scripts, an leftover init
>>> script, or my PEBKAC.
>>> What is expected there? Should I just disable the xenconsoled init
>>> script? If thats the case why is that file present?
>>> Appreciate any thoughts on what is the best thing to do there.
>> I believe xenconsoled is there for compatibility only. I'm pretty sure
>> you can disable it from starting at boot without any concequences.
>> I haven't removed it as I can't be perfectly sure that nobody uses it!
> And ignore the above! I was tinkering around with xenconsoled today - as
> it doesn't seem to be included in the stock tarball but was added by
> RedHat for the inital packaging I picked up.
> It seems that it is critical to actually starting DomUs on boot - and
> without it, they just sit there!
> Does the same happen if you use xl vs xm? (chkconfig xend off && reboot)?
> kernel-xen mailing list
> kernel-xen at lists.wireless.org.au
More information about the kernel-xen