From 7fb4f0a6349a99dcf248b9809ee9c6baf432ff57 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Mon, 5 Oct 2009 14:37:29 +0200 Subject: public_hurd_boxen/domu_console -> public_hurd_boxen/xen_handling --- public_hurd_boxen/xen_handling.mdwn | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 public_hurd_boxen/xen_handling.mdwn (limited to 'public_hurd_boxen/xen_handling.mdwn') diff --git a/public_hurd_boxen/xen_handling.mdwn b/public_hurd_boxen/xen_handling.mdwn new file mode 100644 index 00000000..8407cd58 --- /dev/null +++ b/public_hurd_boxen/xen_handling.mdwn @@ -0,0 +1,31 @@ +[[!meta copyright="Copyright © 2009 Free Software Foundation, Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="Permission is granted to copy, distribute and/or modify this +document under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no Invariant +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]]."]]"""]] + +# 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): + + $ 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 +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 `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`? 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. -- cgit v1.2.3 From 7795eaf0e452da24f7302c132fc6ca7f9460a0c7 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Mon, 5 Oct 2009 14:45:16 +0200 Subject: public_hurd_boxen/xen_handling: Some more Xen usage basics. --- public_hurd_boxen/xen_handling.mdwn | 14 ++++++++++++++ 1 file changed, 14 insertions(+) (limited to 'public_hurd_boxen/xen_handling.mdwn') diff --git a/public_hurd_boxen/xen_handling.mdwn b/public_hurd_boxen/xen_handling.mdwn index 8407cd58..e0874b37 100644 --- a/public_hurd_boxen/xen_handling.mdwn +++ b/public_hurd_boxen/xen_handling.mdwn @@ -8,6 +8,20 @@ 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]]."]]"""]] +# 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*. + # domU consoles To avoid any complications with people trying to use the same console at the -- cgit v1.2.3 From 79cdd566c5194a8ce0a21d3bbb72f9a7d25ea530 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Mon, 5 Oct 2009 14:49:37 +0200 Subject: public_hurd_boxen/xen_handling: About ``xm shutdown''. --- public_hurd_boxen/xen_handling.mdwn | 4 ++++ tag/open_issue_xen.mdwn | 19 +++++++++++++++++++ 2 files changed, 23 insertions(+) create mode 100644 tag/open_issue_xen.mdwn (limited to 'public_hurd_boxen/xen_handling.mdwn') diff --git a/public_hurd_boxen/xen_handling.mdwn b/public_hurd_boxen/xen_handling.mdwn index e0874b37..47d92c43 100644 --- a/public_hurd_boxen/xen_handling.mdwn +++ b/public_hurd_boxen/xen_handling.mdwn @@ -22,6 +22,10 @@ Forcefully killing a domU (that has crashed or is busy-looping, etc.): 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 diff --git a/tag/open_issue_xen.mdwn b/tag/open_issue_xen.mdwn new file mode 100644 index 00000000..5ce9301c --- /dev/null +++ b/tag/open_issue_xen.mdwn @@ -0,0 +1,19 @@ +[[!meta copyright="Copyright © 2009 Free Software Foundation, Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="Permission is granted to copy, distribute and/or modify this +document under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no Invariant +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=open_issue_xen]] + +[[!map pages="tagged(open_issue_xen) and !open_issues and !*/discussion" +show=title]] + +[[!inline +pages="tagged(open_issue_xen) and !open_issues and !*/discussion" +show=0 +feeds=no]] -- cgit v1.2.3