Vserver kernel/Lilo/unknown on Debian woody trouble - any hints?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I want to start using vserver on my Debian woody server machine (it
stands far from here, and I have root, but no terminal access).
Testing the software on my local test machine, everything went smooth
apart from some small issues just at the beginning of my test.
So I compiled a vserver kernel for the server, too, copied it to /boot,
added a lilo entry and ran "lilo -R vserver" to test it first (as it is
more complicated to have the machine restarted with a specific image, I
didn't change the default).
Everything came up and worked all right.
However, after changing the lilo default image, the server did not come
up again. It only worked when I instructed the hoster to select the
"old"/plain kernel image.
This error is reproducable - having the non-vserver image as default,
the server does boot with both kernels (uname -r told me that I worked
using the vserver kernel).
Changing the default to the vserver image, the computer only starts
when manually choosing the plain kernel.
Does anybody have a hint what I'm doing wrong or where I could start
searching?
Thank you a lot, greetings from Regensburg, Germany
Baltasar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBwvo4p2YsmzTbIwYRAkrfAJ4vG8s4bphoJ/+qw+gTQ/nNXCKzbwCfSYvh
90HMjtVCdPerBHFrbStCFSY=
=OdER
-----END PGP SIGNATURE-----
Reply to: