summaryrefslogtreecommitdiff
path: root/public_hurd_boxen
diff options
context:
space:
mode:
authorThomas Schwinge <schwinge@nic-nac-project.de>2009-10-14 10:54:37 +0200
committerThomas Schwinge <schwinge@nic-nac-project.de>2009-10-14 10:54:37 +0200
commita02450df1d851dc70da630d9a8aaf5a472ec7cf5 (patch)
treeb95fa4ce5fedccfb2fc3dad34116eda861e585d8 /public_hurd_boxen
parent74f5b4d5f4108ced7ad24ead53a3ba5a39497405 (diff)
parentc2724866ae27469c32ac4c123c4fe727927d52f6 (diff)
Merge branch 'master' into master-news_next
Diffstat (limited to 'public_hurd_boxen')
-rw-r--r--public_hurd_boxen/xen_handling.mdwn (renamed from public_hurd_boxen/domu_console.mdwn)24
-rw-r--r--public_hurd_boxen/zenhost.mdwn2
2 files changed, 22 insertions, 4 deletions
diff --git a/public_hurd_boxen/domu_console.mdwn b/public_hurd_boxen/xen_handling.mdwn
index 02395e11..47d92c43 100644
--- a/public_hurd_boxen/domu_console.mdwn
+++ b/public_hurd_boxen/xen_handling.mdwn
@@ -8,13 +8,31 @@ Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]
-[[!meta title="domU console"]]
+# listing running domUs
+
+ $ sudo xm list
+
+ $ sudo xm top
+
+# handling running domUs
+
+Forcefully killing a domU (that has crashed or is busy-looping, etc.):
+
+ $ sudo xm 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
+work -- this is not yet implemented in the [[Xen port of GNU
+Mach|microkernel/mach/gnumach/ports/xen]] ([[!taglink open_issue_xen]]).
+
+# domU consoles
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):
- $ sudo screen -DRRS xen-console-[domU] sh -c 'xm console [domU] || xm create -c [domU]'
+ $ host=[domU] && sudo screen -DRRS console-$host sh -c "xm console $host || xm 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
@@ -22,7 +40,7 @@ doing on the first instance), but the output won't be sent back to the second
instance.
After having typed this once, Bash's `reverse-search-history` (`C-r`), followed
-by typing in `console-flubber`, for example, will be enough to get access to
+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
diff --git a/public_hurd_boxen/zenhost.mdwn b/public_hurd_boxen/zenhost.mdwn
index e5f42aab..525f4e36 100644
--- a/public_hurd_boxen/zenhost.mdwn
+++ b/public_hurd_boxen/zenhost.mdwn
@@ -12,4 +12,4 @@ License|/fdl]]."]]"""]]
(see the table on [[public hurd boxen]] for a list).
-[[!inline pages=public_hurd_boxen/domu_console feeds=no]]
+[[!inline pages=public_hurd_boxen/xen_handling feeds=no]]