Michael H. Warfield escribió:
On Tue, 2010-01-19 at 20:26 -0600, SD :: Ventas wrote:
Scott Dowdle escribió:
Greetings,

----- "SD :: Ventas" <[email protected]> wrote:
Mike i do what you say:

[r...@ns ~]# yumdownloader ovzkernel
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * addons: mirror.steadfast.net
 * base: centos.mirrors.tds.net
 * extras: mirrors.bigtennetwork.com
 * openvz-kernel-rhel5: mirror.ubiquityservers.com
 * openvz-utils: mirror.ubiquityservers.com
 * updates: mirror.fdcservers.net
extras 325/325 openvz-kernel-rhel5 | 951 B 00:00 openvz-kernel-rhel5/primary | 25 kB 00:00 openvz-kernel-rhel5 14/14 openvz-utils | 951 B 00:00 openvz-utils/primary | 5.8 kB 00:00 openvz-utils 26/26 updates | 1.9 kB 00:00 updates/primary_db | 416 kB 00:00 ovzkernel-2.6.18-164.2.1.el5.028stab066.10.i686.rpm | 19 MB 00:05

then

[r...@ns ~]# rpm -ivh
ovzkernel-2.6.18-164.2.1.el5.028stab066.10.i686.rpm
Preparing... ########################################### [100%] package ovzkernel-2.6.18-164.2.1.el5.028stab066.10.i686 is already installed
[r...@ns ~]#

and if i chek on /boot/grub/grub.conf


[r...@ns ~]# cat /boot/grub/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this
file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
#          initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-164.10.1.el5PAE)
        root (hd0,0)
kernel /vmlinuz-2.6.18-164.10.1.el5PAE ro root=/dev/VolGroup00/LogVol00
        initrd /initrd-2.6.18-164.10.1.el5PAE.img
title CentOS (2.6.18-164.2.1.el5.028stab066.10)
        root (hd0,0)
kernel /vmlinuz-2.6.18-164.2.1.el5.028stab066.10 ro root=/dev/VolGroup00/LogVol00
        initrd /initrd-2.6.18-164.2.1.el5.028stab066.10.img
title CentOS (2.6.18-164.2.1.el5.028stab066.10PAE)
        root (hd0,0)
kernel /vmlinuz-2.6.18-164.2.1.el5.028stab066.10PAE ro root=/dev/VolGroup00/LogVol00
        initrd /initrd-2.6.18-164.2.1.el5.028stab066.10PAE.img
title CentOS (2.6.18-92.1.18.el5.028stab060.8PAE)
        root (hd0,0)
kernel /vmlinuz-2.6.18-92.1.18.el5.028stab060.8PAE ro root=/dev/VolGroup00/LogVol00
        initrd /initrd-2.6.18-92.1.18.el5.028stab060.8PAE.img
title OpenVz (2.6.18-92.1.18.el5.028stab060.2PAE)
        root (hd0,0)
kernel /vmlinuz-2.6.18-92.1.18.el5.028stab060.2PAE ro root=/dev/VolGroup00/LogVol00
        initrd /initrd-2.6.18-92.1.18.el5.028stab060.2PAE.img
title OpenVzn (2.6.18-92.1.18.el5.028stab060.2)
        root (hd0,0)
kernel /vmlinuz-2.6.18-92.1.18.el5.028stab060.2 ro root=/dev/VolGroup00/LogVol00
        initrd /initrd-2.6.18-92.1.18.el5.028stab060.2.img
title CentOS (2.6.18-92.el5PAE)
        root (hd0,0)
        kernel /vmlinuz-2.6.18-92.el5PAE ro
root=/dev/VolGroup00/LogVol00
        initrd /initrd-2.6.18-92.el5PAE.img
[r...@ns ~]#
Well that solves that.  You have upgraded and upgraded... but not rebooted to 
switch kernels... or maybe you DID reboot but it still has the old kernel as 
the default.

What I recommend you do is to remove any of the kernels you don't plan on 
using, and make sure your /etc/grub.conf is set to boot the kernel you want as 
default.  I think the rpm package the OpenVZ project provides tries to update 
your grub.conf every time a new kernel is installed but it isn't always 
successful setting the new kernel to be default.  SO... the lesson is, whenever 
you install a new kernel, make sure your /etc/grub.conf file is how you want 
it, then reboot if you want to switch kernels.

TYL,
ok, im gonna do that, but isnt problem if the kernel dont say PAE, i
have 6gb ram on my server.

Time OUT!

I don't know when you rebooted last and when you last updated but it
looks like the default boot (0) is a non-ovz kernel.  If you look at
entry #2 (third entry), isn't that the PAE ovzkernel you are looking
for?  Change default to 2 instead of 0 and then reboot.

--
Ing. Alejandro M.
-----------------------
Hospedaje Web y Servidores Dedicados
http://www.dedicados.com.mx
-----------------------
[email protected]
-----------------------


__________ Informacin de ESET NOD32 Antivirus, versin de la base de
firmas de virus 4787 (20100119) __________

ESET NOD32 Antivirus ha comprobado este mensaje.

Mike
------------------------------------------------------------------------

_______________________________________________
Users mailing list
[email protected]
https://openvz.org/mailman/listinfo/users



__________ Información de ESET NOD32 Antivirus, versión de la base de firmas de 
virus 4788 (20100120) __________

ESET NOD32 Antivirus ha comprobado este mensaje.

http://www.eset.com

is there any way to have problems rebooting?? im asking because i have 8 VE there, so i dont want problems with customers, if you guys think that can be a problem, i prefeer to wait. so reboot dont affect.

--
Ing. Alejandro M.
-----------------------
Hospedaje Web y Servidores Dedicados
http://www.dedicados.com.mx
-----------------------
[email protected]
-----------------------




__________ Informaci�n de ESET NOD32 Antivirus, versi�n de la base de firmas de 
virus 4788 (20100120) __________

ESET NOD32 Antivirus ha comprobado este mensaje.

http://www.eset.com

_______________________________________________
Users mailing list
[email protected]
https://openvz.org/mailman/listinfo/users

Reply via email to