Re: Upgrading Kernel on VPS - Failed?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 23/02/15 10:36, Karl E. Jorgensen wrote:
> What does "uname -a" report? This should tell you what the running
> kernel version is.
>
> It could be a case of your providing implementing your Virtual
> Private Server using kernel cgroups - e.g. via Linux Containers
> (LXC). If so, then you do not control what kernel you run - you
> share the kernel of the host operating system, but have limited
> access inside it. Tools like grub and lilo do not apply inside
> Linux Containers either.
>
> A VPC is a very close approximation to a "real" hardware server,
> but not quite the same.
>
> One relatively easy way of detecting whether you're inside a LXC is
> to run "uptime" - this will report the uptime of the host kernel.
> If you recently rebooted your VPS, you will see an uptime which is
> "too long". Tools like the "imvirt" package can also tell you what
> virtualisation you're running under.
Another possibility is that the VPS is running under Xen, which also
generally has the kernel loaded from outside - but loading a different
one is possible, either by negotiation with your provider, or, if they
support it, using pv-grub:
http://www.rackspace.com/knowledge_center/article/using-a-custom-kernel-with-pv-grub
(rackspace-specific instructions, of course - ymmv)
Richard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQEcBAEBAgAGBQJU6/JnAAoJELSi8I/scBaNaVYIAIwKOJOUVd3EjNk8Mm/U9sUS
/erJWplV5Mlf1a0zWfwqDDbvTf417LMFUWVBvwbaW1TKjPB5LZ+E3QaA9NtOBul0
t6Zyllr0Fz7bDhLEaUVksAgylqCD3IIUfJjSA7TPuooTyLGl0efv6AcvMUt+f23X
V6KtirVs7lW97jlatJUT/0BlBn9bLusB0gQOWtqGLhhteVLamY6ShMdexJhEffSq
RrXRcJmPoY2Y8+suD+Uwin1sTkDeEzSU7UQcwFwX2+qRxT5J4V8IsQs7RlqB+EqM
zI9BvzREDon/2L7mUP8NJHGt3tw9XmMSqPo4T4zs3nEBdIrME3Lgj+/eFnFHyEk=
=Lkve
-----END PGP SIGNATURE-----
Reply to: