blob: 2f131e5a51b487c0e568e014b7a90b417598d153 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
|
[[!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="domU console"]]
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]'
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 `console-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.
|
