Re: [Xen-users] domU consoles

[Yura Pismerov <y.pismerov@xxxxxxxxxxxxx>]

Chris Peterman wrote:
> Whoa thats cool! I'm gonna implement it on my machine tomorrow :D
>   

Yes, but how about. let's say, 100 VMs ?
IMHO setting up shell aliases (eg. alias vm1='xm console dom1') would be
more scalable solution.
Though you'd lose screen buffer in this case and would not be able to
scroll back (or I am mistaken ?)
So here is a better solution using old good program called "screen":

alias vm1="screen -T vt100 -a -A -S vm1 xm console dom1"
alias scd='screen -dr'  # to re-attach screen
alias sls='screen -ls' # to list all screen sessions

Then you can run "vmN" will open screen sessions to domN from any shell.
This has to be run once (unless you terminate the screen session).
Within the attached session you can use "Ctrl-A-D" to detach it.
Outside the screen session you can use "scd vmN" to reattach any session
even if it was attached elsewhere.
Even you close your current shell, your session does not terminate since
screen keeps it open.
For example, you can start long running task, detach the session and
continue your work. then you can re-attach it and review the results or
check the status.
You can even scroll back and/or search through the screen buffer (after
hitting Ctrl-A-Esc)
Technically you need only one terminal (or ssh) session to manage
hundreds of hosts. This is why many sysadmins love screen :)



> On Thursday 15 June 2006 19:27, Itai Tavor wrote:
>   
>>> Paolo Supino wrote:
>>>       
>>>> Hi
>>>>
>>>>  I have a couple of questions:
>>>> 2. How do I setup a dom0/domU in order to get a tty login?
>>>>         
>> Not sure if it's quite what you're after, but I use the following in /
>> etc/inittab:
>>
>> 1:2345:respawn:/usr/sbin/xm top > /dev/tty1
>> 2:23:respawn:/usr/sbin/xm console dom1 > /dev/tty2 < /dev/tty2 2>&1
>> 3:23:respawn:/usr/sbin/xm console dom2 > /dev/tty3 < /dev/tty3 2>&1
>> 4:23:respawn:/usr/sbin/xm console dom3 > /dev/tty4 < /dev/tty4 2>&1
>> 5:23:respawn:/usr/sbin/xm console dom4 > /dev/tty5 < /dev/tty5 2>&1
>> 6:23:respawn:/usr/sbin/xm console dom5 > /dev/tty6 < /dev/tty6 2>&1
>> 7:23:respawn:/usr/sbin/xm console dom6 > /dev/tty7 < /dev/tty7 2>&1
>> 8:23:respawn:/usr/sbin/xm console dom7 > /dev/tty8 < /dev/tty8 2>&1
>> 9:23:respawn:/sbin/getty 38400 tty9
>>
>> This gives me 'xm top' on the main console, console access to my
>> guests using ALT-F2..ALT-F8, and a host login prompt with ALT-F9.
>>
>> There's room for improvement... if a guest is down, the guest console
>> spits out an endless stream "Domain xxx isn't running" - I'm thinking
>> of wrapping the xm call in a script that will deal with that quietly.
>>
>> HTH, Itai
>>
>>
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-users
>>     
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users


-- 
Yuri Pismerov, System Administrator
Armor Technologies (Canada) Inc.

P: 905 305 1946 (x.3519)
http://www.armorware.net

Privacy Protection Guaranteed!




_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users