Bug 410053 – app-emulation/xen-tools-4.1.2-r2 init script throws: option 'a' not supported

• Product: Gentoo Linux
• Status: RESOLVED OBSOLETE

[Description Marcin Mirosław 2012-03-28 19:24:26 UTC]

There is in file /etc/init.d/, in function stop() such line:
/usr/sbin/xl shutdown -a -w >/dev/null
but xl shutdown doesn't support parameter "-a". xl help shutdown also doesn't display "-a" as available option.

Reproducible: Always

[Comment 1 Anthony Weltzer 2012-05-07 03:04:31 UTC]

(In reply to comment #0)
> There is in file /etc/init.d/, in function stop() such line:
> /usr/sbin/xl shutdown -a -w >/dev/null
> but xl shutdown doesn't support parameter "-a". xl help shutdown also
> doesn't display "-a" as available option.

I also can attest to the existence of this bug. My test fix is to replace the 'xl' command with 'xm'. The line would then read:
/usr/sbin/xm shutdown -aw > /dev/null
This small modification works for my system, but I have yet to test the wider implications of a global replacement. As far as I can tell 'xl' and 'xm' do the same things, but the 'xl' is not allowing the same syntax as 'xm'.

[Comment 2 Tomáš Mózes 2012-06-07 07:32:52 UTC]

According to http://wiki.xen.org/wiki/XL:

As of Xen 4.1 xl is the default toolstack supplied as part of the Xen release. The older xend toolstack is still available in tree but is considered deprecated and may eventually be removed.

A quick workaround is to write a shell script, that would kill your machines, or to use a command as:
for i in `xl list|tail -n +3|awk '{print $1}'`; do xl shutdown $i; done

[Comment 3 Yixun Lan 2014-05-27 22:16:26 UTC]

I think we've partially handled this problem, restrict "-a" option been used while xen >=4.2.x versions.

Tomas Mozes's suggestion probably would be better, using script to iterate all domUs and shutdown them all or one by one, which means it also handle well with the manually started domU (the one not start by xendomains init script)

[Comment 4 Yixun Lan 2014-05-29 20:30:05 UTC]

em.. all ebuild in tree are >=4.2, so this bug is not valid anymore