Xen users - Jan 2006 - ctrl-c doesn''t work in domU consoles

Hey,

I''ve installed Xen 3.0 on a freshly installed Debian Sarge. dom0 is
working nicely (kernel 2.6.12.6-xen0). Then I created a domU, again with
Debian Sarge, booting Xen''s vmlinuz-2.6.12-xenU. Unfortunately ctrl-c
does not work in the domU''s console, neither if I create the domU
with "xm create -c ..." nor if I attach to it later. It
doesn''t matter
if I do this over ssh or directly on the dom0''s console -- in both
cases
nothing happens if I press ctrl-c. Note that ctrl-] works and detaches
the console normally.

Any tips? Thanks in advance.

Regards,
Moritz

-- 
LINET Services GbR

Gotenweg 15                      Tel.: 0531-280 191 71
38106 Braunschweig               Fax.: 0531-280 191 72

http://www.linet-services.de
mailto:info@linet-services.de



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

Moritz Bunkus wrote:
> Hey,
>
> I''ve installed Xen 3.0 on a freshly installed Debian Sarge. dom0
is
> working nicely (kernel 2.6.12.6-xen0). Then I created a domU, again with
> Debian Sarge, booting Xen''s vmlinuz-2.6.12-xenU. Unfortunately
ctrl-c
> does not work in the domU''s console, neither if I create the domU
> with "xm create -c ..." nor if I attach to it later. It
doesn''t matter
> if I do this over ssh or directly on the dom0''s console -- in both
cases
> nothing happens if I press ctrl-c. Note that ctrl-] works and detaches
> the console normally.
>
> Any tips? Thanks in advance.
>   
Try ctrl-] instead (I just had the same effect, and remebered some 
consoles saying "escape is control-]" works for me to end a ping
command.

Henning

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

Moritz Bunkus wrote:
> Hey,
>
> I''ve installed Xen 3.0 on a freshly installed Debian Sarge. dom0
is
> working nicely (kernel 2.6.12.6-xen0). Then I created a domU, again with
> Debian Sarge, booting Xen''s vmlinuz-2.6.12-xenU. Unfortunately
ctrl-c
> does not work in the domU''s console, neither if I create the domU
> with "xm create -c ..." nor if I attach to it later. It
doesn''t matter
> if I do this over ssh or directly on the dom0''s console -- in both
cases
> nothing happens if I press ctrl-c. Note that ctrl-] works and detaches
> the console normally.
>   
Sorry, I was completely wrong with my guess... ctrl-] logs me out, 
that''s why the ping messages stop - I just didn''t adjust the
hostname of
my domu1, so it doesn''t change in the console when ctrl-] gets me out.

So I have the same problem, ctrl-c "doesn''t have any effect",
at least
in a console opened by xm, and I feel a bit helpless how I can end a 
simple ping...


Henning



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

Moritz Bunkus wrote:
> Hey,
>
> I''ve installed Xen 3.0 on a freshly installed Debian Sarge. dom0
is
> working nicely (kernel 2.6.12.6-xen0). Then I created a domU, again with
> Debian Sarge, booting Xen''s vmlinuz-2.6.12-xenU. Unfortunately
ctrl-c
> does not work in the domU''s console, neither if I create the domU
> with "xm create -c ..." nor if I attach to it later. It
doesn''t matter
> if I do this over ssh or directly on the dom0''s console -- in both
cases
> nothing happens if I press ctrl-c. Note that ctrl-] works and detaches
> the console normally.
>   
Sorry, I was completely wrong with my guess... ctrl-] logs me out,
that''s why the ping messages stop - I just didn''t adjust the
hostname of
my domu1, so it doesn''t change in the console when ctrl-] gets me out.

So I have the same problem, ctrl-c "doesn''t have any effect",
at least
in a console opened by xm, and I feel a bit helpless how I can end a
simple ping...


Henning





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

Pierre "Le Pierrot" wrote:
> As a quick hack/sugestion: Have you tried ctrl-z and then ps aux|grep ping,
> then kill -9 pid
>
> If ^Z works... :-)
> Otherwise, try telnet/ssh''ing into your domU and kill it with
kill.
>   
I can also shut down the complete vm, because I am just testing right 
now, but if the system will be used for something "real" it would be 
real great to know how I can make ctrl-c really work as usual.

Just looked at the demo cd, there ctrl-c  works as usual. I''m gonna 
compare my config now with the demo cd.

BTW, the system that can''t handle ctrl-c is debian sarge dom0, with a 
debian sarge domU installed exactly as said in the the DebianDomU Howto 
in the wiki...

Henning

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

I''m also having the same issue.  Is this because I''m missing a
package or
missing some other detail?

Here''s the relevant output from ''stty -a'':
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;

So Ctrl-C is properly defined in domU.


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

On Sat, 2006-01-07 at 23:18 -0600, Eric Peterson wrote:
> I''m also having the same issue.  Is this because I''m
missing a package
> or missing some other detail?
I just found out, in a console started by the xm command, you can type

ctrl-o then the key "e"

This seems to terminate all processes in that console.
typing

ctrl-o o

shows SysRq HELP, which seems to be something which has it''s traces
back
from somehwere in the kernel. Probably these are keys for what is
described in man xm starting with  "sysrq domain-id letter"

Probably there are some special functions on the control keys, but I
don''t know where they are documented, apart from the source of xm,
maybe.

Meanwhile, in a ssh shell the problem doesn''t exist.

Henning



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

I tried the same thing, however it didn''t work for me.

On 1/9/06, Henning Sprang <henning_sprang@gmx.net>
wrote:
>
> I just found out, in a console started by the xm command, you can type
>
> ctrl-o then the key "e"
>
> This seems to terminate all processes in that console.
> typing
>
> ctrl-o o
>
> shows SysRq HELP, which seems to be something which has it''s
traces back
> from somehwere in the kernel. Probably these are keys for what is
> described in man xm starting with  "sysrq domain-id letter"
>
> Probably there are some special functions on the control keys, but I
> don''t know where they are documented, apart from the source of xm,
> maybe.
>
> Meanwhile, in a ssh shell the problem doesn''t exist.
>
--

regards,

Anand


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

I read through the man page for xm and found it refering to sysrq.txt in the
kernel documentation. Any one has an idea on how to actually use it ?

The value for /proc/sys/kernel/sysrq in the domU is 0.

On 1/9/06, Henning Sprang <henning_sprang@gmx.net>
wrote:
>
> On Sat, 2006-01-07 at 23:18 -0600, Eric Peterson wrote:
> > I''m also having the same issue.  Is this because I''m
missing a package
> > or missing some other detail?
>
> I just found out, in a console started by the xm command, you can type
>
> ctrl-o then the key "e"
>
> This seems to terminate all processes in that console.
> typing
>
> ctrl-o o
>
> shows SysRq HELP, which seems to be something which has it''s
traces back
> from somehwere in the kernel. Probably these are keys for what is
> described in man xm starting with  "sysrq domain-id letter"
>
> Probably there are some special functions on the control keys, but I
> don''t know where they are documented, apart from the source of xm,
> maybe.
>
> Meanwhile, in a ssh shell the problem doesn''t exist.
>
> Henning
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>


--

regards,

Anand


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

Hey,

On Sunday 08 January 2006 06:18, Eric Peterson wrote:
> I''m also having the same issue.  Is this because I''m
missing a package or
> missing some other detail?
>
> Here''s the relevant output from ''stty -a'':
> intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
Same here in the dom0 and in the domU. I haven''t found a solution so
far.

Mosu

-- 
LINET Services GbR

Gotenweg 15                      Tel.: 0531-280 191 71
38106 Braunschweig               Fax.: 0531-280 191 72

http://www.linet-services.de
mailto:info@linet-services.de



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

Hey,

On Monday 09 January 2006 00:21, Henning Sprang wrote:
> This seems to terminate all processes in that console.
> typing
>
> ctrl-o o
>
> shows SysRq HELP
I definitely don''t want the SysRq functionality for terminating a
simple
ping -- a normal Ctrl-C will suffice.
> Meanwhile, in a ssh shell the problem doesn''t exist.
True, but I''m experimenting with network configuration and most of the
time there is no SSH access to the domU.

Mosu

-- 
LINET Services GbR

Gotenweg 15                      Tel.: 0531-280 191 71
38106 Braunschweig               Fax.: 0531-280 191 72

http://www.linet-services.de
mailto:info@linet-services.de



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

Moritz Bunkus wrote:
> [...]
>> This seems to terminate all processes in that console.
>> typing
>>
>> ctrl-o o
>>
>> shows SysRq HELP
>>     
>
> I definitely don''t want the SysRq functionality for terminating a
simple
> ping -- a normal Ctrl-C will suffice.
>
>   
>> Meanwhile, in a ssh shell the problem doesn''t exist.
>>     
>
> True, but I''m experimenting with network configuration and most of
the
> time there is no SSH access to the domU.
>   
You''re completely right! All these are not solutions but
"dirty"
workarounds.  But they might help others who come in such a
"desperate"
situation when trying xen and accidently use, for example, ping.

Henning







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

Isn''t this problem a standard one with Linux serial drivers?

  I know when I used to hook my Sun Netra up to my desktop
 via a serial cable the console I received didn''t understand
 Ctrl-c.  (Both machines running Debian.)

  My "solution" was to run:

  alias ping=''ping -c 5''

  Or otherwise use SSH to connect to the host to kill otherwise
 unkillable jobs.

Steve
-- 
http://www.steve.org.uk/

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

On 1/9/06, Steve Kemp <steve@steve.org.uk> wrote:
>
>
>   Isn''t this problem a standard one with Linux serial drivers?
>
>   I know when I used to hook my Sun Netra up to my desktop
> via a serial cable the console I received didn''t understand
> Ctrl-c.  (Both machines running Debian.)
>
>   My "solution" was to run:
>
>   alias ping=''ping -c 5''
>
>   Or otherwise use SSH to connect to the host to kill otherwise
> unkillable jobs.
>
This is a workaround, but not really a solution as you indicate.

It believe it has something to do with this version of Xen or with the
debootstrap process.

I am experiencing this problem with Debian etch and sarge built from a 2006
copy of the xen source.  I am not having this problem with my Fedora box
running xen from the 3.0.0 installer version of testing.

I''ll keep poking at it and let you all know if I find anything. 
I''m going
to try the same setup on a Fedora machine this afternoon.

_Eric


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

Well I finally had time to test the same procedures using FC4 and Ctrl-C
works fine.

So is this purely a debian problem?  Research seems to suggest it is, but
why hasn''t the rest of the world seen the problem?  Are we doing
something
wrong?

Let me know what I can do to help determine the problem.

Thanks.
Eric


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

Am Donnerstag, 12. Januar 2006 19:45 schrieb Eric
Peterson:
> Well I finally had time to test the same procedures using FC4 and Ctrl-C
> works fine.
If I remeber it correctly, it works without problems on a suse domainU too. I 
can test that tomorrow.
> So is this purely a debian problem?  Research seems to suggest it is, but
> why hasn''t the rest of the world seen the problem?  Are we doing
something
> wrong?
It''s at least a debian problem. I have it on all my debian
domainU''s (about
20).

interessting is, that if you use "screen" in a xen console, then
ctrl-c works
again. So it seems to problem with getty, right? They key is passed from 
domain0 to domainU, just then debian getty seems to have a bug.

"stty -a" on a debian domainU (via console) where ctrl-c is not
working:
speed 38400 baud; rows 0; columns 0; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W;
lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 hupcl -cstopb cread -clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon ixoff
-iuclc -ixany -imaxbel
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 
ff0
isig icanon -iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt
echoctl echoke

"stty -a" on the same domainU (via console), but in a screen session
(ctrl-c
works there):
speed 9600 baud; rows 24; columns 80; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^H; eof = ^D; eol = <undef>;
eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W;
lnext = ^V; flush = ^O; min = 0; time = 0;
-parenb -parodd cs8 -hupcl -cstopb cread clocal -crtscts
-ignbrk brkint ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff
-iuclc -ixany -imaxbel
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab3 bs0 vt0 
ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt
echoctl echoke

I know it''s not great, but for a domainU with no network access using
screen
would be a workout until this gets fixed.
> Let me know what I can do to help determine the problem.
we should probably sumbit a bug report against getty in the debian bug 
tracking system, maybe the maintainer of getty knows what going on here. I 
have no clue...
> Thanks.
> Eric
--Ralph

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

> I know it''s not great, but for a domainU with no network access
using
> screen would be a workout until this gets fixed.
I meant "workaround", of course... to much live migrations for today
;-P

--Ralph

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

We had the same problem. I changed the line
0:2345:respawn:/sbin/qlogin /dev/ttys/0 root
to
0:2345:respawn:/sbin/qlogin /dev/tty1 root
in /etc/inittab on domU. We are using qlogin so I don''t know if this 
applies to you but you could check it out.

/Anders

Moritz Bunkus wrote:
> Hey,
> 
> I''ve installed Xen 3.0 on a freshly installed Debian Sarge. dom0
is
> working nicely (kernel 2.6.12.6-xen0). Then I created a domU, again with
> Debian Sarge, booting Xen''s vmlinuz-2.6.12-xenU. Unfortunately
ctrl-c
> does not work in the domU''s console, neither if I create the domU
> with "xm create -c ..." nor if I attach to it later. It
doesn''t matter
> if I do this over ssh or directly on the dom0''s console -- in both
cases
> nothing happens if I press ctrl-c. Note that ctrl-] works and detaches
> the console normally.
> 
> Any tips? Thanks in advance.
> 
> Regards,
> Moritz
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users

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

On Fri, Jan 27, 2006 at 10:21:22AM +0100, Anders Siverby
wrote:
> We had the same problem. I changed the line
> 0:2345:respawn:/sbin/qlogin /dev/ttys/0 root
> to
> 0:2345:respawn:/sbin/qlogin /dev/tty1 root
> in /etc/inittab on domU. We are using qlogin so I don''t know if
this
> applies to you but you could check it out.
Changing my inittab in Debian SID from:

1:2345:respawn:/sbin/getty 38400 console

to:

1:2345:respawn:/sbin/getty 38400 tty1

seems to work here. Ctrl-C works fine now.
    
Thanks for the tip!

-- 
CJ van den Berg

mailto:cj@vdbonline.com
  xmpp:cj@vdbonline.com
   sip:8918316@sipgate.de

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