Remus Toolkit Differences: Difference between revisions
From Xen
Jump to navigationJump to search
Rcpavlicek (talk | contribs) m (→Remus in XL) |
Rcpavlicek (talk | contribs) |
||
Line 2: | Line 2: | ||
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 [http://xenbits.xenproject.org/docs/4.4-testing/man/xl.1.html xl man pages] (search for the "remus" option). |
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 [http://xenbits.xenproject.org/docs/4.4-testing/man/xl.1.html 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 in XM == |
Revision as of 19:14, 19 June 2014
Remus in XL
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)