Remus Toolkit Differences: Difference between revisions
Lars.kurth (talk | contribs) No edit summary |
Lars.kurth (talk | contribs) |
||
Line 2: | Line 2: | ||
=== Xen 4.5 and newer === |
=== Xen 4.5 and newer === |
||
In [ |
In [[:Category:Xen|4.5]] the [[XM]] toolstack is not supported any more. Remus is invoked via the "xl remus ..." syntax. This syntax can be found in recent [http://xenbits.xenproject.org/docs/4.5-testing/man/xl.1.html#remus_options_domain_id_host xl man pages] (search for the "remus" option). |
||
=== Xen 4.4. === |
=== Xen 4.4. === |
Revision as of 15:55, 28 January 2015
Remus in XL
Xen 4.5 and newer
In 4.5 the XM toolstack is not supported any more. Remus is invoked via the "xl remus ..." syntax. This syntax can be found in recent xl man pages (search for the "remus" option).
Xen 4.4.
Xenlight is the current toolkit for Xen Project. In xenlight, Remus is invoked via the "xl remus ..." syntax. This syntax can be found in recent xl man pages (search for the "remus" option).
As of 4.4, Remus support in xl is still in experimental (proof-of-concept) phase. Per the man page, there is no support for network or disk buffering in the current release.
Remus in XM
Remus was originally implemented when Xen Project was using the xm toolkit. If you are still using xm, you will need to use the "remus" command to control the software.
The "remus" command uses the following syntax:
Usage: remus [options] domain [destination]
Options: -h, --help show this help message and exit -i MS, --interval=MS checkpoint every MS milliseconds -p PORT, --port=PORT send stream to port PORT --blackhole replicate to /dev/null (no disk checkpoints, only memory & net buffering) --no-net run without net buffering (benchmark option) --no-compression run without checkpoint compression --timer force pause at checkpoint interval (experimental)