summaryrefslogtreecommitdiff
path: root/public_hurd_boxen
diff options
context:
space:
mode:
authorSamuel Thibault <samuel.thibault@ens-lyon.org>2026-07-23 01:14:27 +0200
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2026-07-23 01:14:27 +0200
commit1c1f023b1c302eae296e68008de1729982e57415 (patch)
tree3ed0a0326a4cc539105bad8699dcf8658f836c72 /public_hurd_boxen
parent5294397783012176473506753bf2b604c8b5f3de (diff)
Refresh xen documentation
Diffstat (limited to 'public_hurd_boxen')
-rw-r--r--public_hurd_boxen/xen_handling.mdwn12
1 files changed, 6 insertions, 6 deletions
diff --git a/public_hurd_boxen/xen_handling.mdwn b/public_hurd_boxen/xen_handling.mdwn
index d4e33ce9..b7d111ce 100644
--- a/public_hurd_boxen/xen_handling.mdwn
+++ b/public_hurd_boxen/xen_handling.mdwn
@@ -10,19 +10,19 @@ License|/fdl]]."]]"""]]
# listing running domUs
- $ sudo xm list
+ $ sudo xl list
- $ sudo xm top
+ $ sudo xl top
# handling running domUs
Forcefully killing a domU (that has crashed or is busy-looping, etc.):
- $ sudo xm destroy [domU]
+ $ sudo xl destroy [domU]
As for (re-)starting a domU, read below in *domU consoles*.
-Using `xm shutdown [domU]` to gracefully shut down a running domU does not yet
+Using `xl shutdown [domU]` to gracefully shut down a running domU does not yet
work -- this is not yet implemented in the [[Xen port of GNU
Mach|microkernel/mach/gnumach/ports/xen]] ([[!taglink open_issue_xen]]).
@@ -32,7 +32,7 @@ To avoid any complications with people trying to use the same console at the
same time, please use this command for attaching to a domU's console (this
command line will also start the domU in case that it isn't running already):
- $ host=[domU] && sudo screen -DRRS console-$host sh -c "xm console $host || xm create -c $host"
+ $ host=[domU] && sudo screen -DRRS console-$host sh -c "xl console $host || xl create -c $host"
Otherwise, if one attaches to the same console twice, the second instance will
in fact forward input to the domU (possibly infering with what the person is
@@ -44,7 +44,7 @@ by typing in `host=flubber`, for example, will be enough to get access to
that machine's console.
/!\ TODO: How does one get the environment variables `COLUMNS` and `LINES` set
-properly when using `xm console`? According to Samuel, *you don't, the xen
+properly when using `xl console`? According to Samuel, *you don't, the xen
console doesn't have the notion of terminal size*. This is relevant for
everything using `(n)curses` -- for interactive console applications. Using
`export COLUMNS=143 LINES=44` does work, but is a manual process.