On Nov 19, 2008, at 1:11 PM, "Eric Jansen" <janseneric@xxxxxxxxx> wrote:
Thanks for quick reply Ross, please see the followings:
Please suggest me on how should I redo?
1. This is the result of /boot/grub/grub.conf:
default=0
timeout=5
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
hiddenmenu
title Xen-3.3 CentOS 5.2 x86_32 (2.6.18.8-xen)
root (hd0,0)
kernel /boot/xen-3.3.gz
module /boot/vmlinuz-2.6.18.8-xen ro root=LABEL=/1 rhgb quiet
module /boot/initrd-2.6.18.8-xen.img
Is this the xenlinux kernel from Xen.org? Why not stick with stock?
title CentOS (2.6.18-92.el5xen)
root (hd0,0)
kernel /boot/xen.gz-2.6.18-92.el5
module /boot/vmlinuz-2.6.18-92.el5xen ro root=LABEL=/1 rhgb
quiet
module /boot/initrd-2.6.18-92.el5xen.img
If this kernel boots you will see the issue you described.
title CentOS-base (2.6.18-92.el5)
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-92.el5 ro root=LABEL=/1 rhgb quiet
initrd /boot/initrd-2.6.18-92.el5.img
Can you give the output of rpm -qa "*xen*"
I guess with the appearence of xenlinux you downloaded the tarball and
did a make install which makes reinstallation of Xen extremely
difficult.
Next time use the src.rpm from 3.2 to build an rpm package which makes
reinstalls a lot easier.
It is wholly possible that the Xen-libs package from CentOS was still
installed when you did the make install and then was upgraded which
wrote over your 3.3 libs with 3.1 libs.
I hope not but an rpm -qa will show us.
-Ross
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|