About this list Date view Thread view Subject view Author view Attachment view

From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Tue 26 Apr 2005 - 23:10:12 BST


On Tue, Apr 26, 2005 at 07:21:44AM +0200, Benedikt Boehm wrote:
> On Tuesday 26 April 2005 02:41, Michal Ludvig wrote:
> > Hi all,
> >
> > I observe a strange behaviour with SL92/x86 (SuSE Linux 9.2) vserver
> > running on SL92/amd64 host with 2.6.11.5-vs1.95 and util-vserver
> > 0.30.204 (linked with dietlibc 0.28).
> >
> > When starting up the vserver in 'sysv' mode, everything works just fine
> > except that I can't reboot it from inside of the vserver. Reboot fails
> > with:
> >
> > ~# reboot
> > init: timeout opening/writing control channel /dev/initctl
> >
> > So I changed the init method to 'plain' and did 'vserver popelka start'.
> > The host came up in the background, but immediately my keyboard in X
> > (xorg-x11-6.8.1/amd64) died
>
> I can confirm this, the plain init style causes exact the same error, and it
> doesn't matter where the vserver wa started, i tried, Konsole, the Terminal
> on Alt+F1, a screen session, ssh session.. the keyboard always died.

okay, folks, let's investigate this a little further ...
the following theories might be true (please verify/falsify)

 - the tools (util-vserver 0.30.206, + dietlibc 0.28+patches)
   emit some stuff, do some things, whatever .. which 'disturbes
   the X keyboard ... (unlikely, but possible)

   * make sure that the tools are the latest and dietlibc is
     (patched on x86_64)
   * check by starting the vserver from a different host
     (logged on via ssh, and maybe telnet)
 
 - the init inside the vserver does something which manages
   to confuse the X keyboard (would be an isolation issue)

   * try to replace the init with an minit or a different init
   * replace the init by an strace wrapper to dump the syscalls

 - there is an unwanted 'connection' between the X (on the host)
   and the vserver which really should not be there

   * check for device nodes in /dev and various other places
   * verify that no 'magic' keys are copied from the host
   * look for pipes (fifos) which run between host and guest

TIA,
Herbert
>
> > and load came up to 1.00 because the 'X'
> > process ended up eating all the CPU time. Everything else worked - I
> > could use the mouse to exit X and logged in again and it worked fine
> > until I did reboot from inside of the vserver. Now it succeeded, but as
> > soon as the host was about to come up after reboot the keyboard died again.
> >
> > Has anyone else seen this behaviour? I suspect the SuSE init or one of
> > the initscripts run *something* that breaks X/keyboard. N.b. from text
> > console it works with no problems.
>
> No success until now finding out why it dies...
>
> >
> > Is there anyting I should try to avoid this? Or is there any way to
> > allow reboot from inside of the vserver without having 'init' process
> > running?
> >
> > Thanks!
> >
> > Michal Ludvig
> _______________________________________________
> Vserver mailing list
> Vserver_at_list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


About this list Date view Thread view Subject view Author view Attachment view
[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Tue 26 Apr 2005 - 23:10:42 BST by hypermail 2.1.3