WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Supported Distros

On Wed, Jun 16, 2010 at 3:46 PM, Jonathan Tripathy <jonnyt@xxxxxxxxxxx> wrote:
> I think I've tried the above in the past, but followed this guide:
> http://www.syntaxtechnology.com/2010/01/upgrade-xen-3-0-on-centos-5-4-x86_64-to-xen-3-4-2/
>
> but it replaced the kernel...
>
> What is the best way to make sure that the same kernel is used? Just run yum
> update xen?

Well, yeah.

BTW, the tutorial on that page is also correct. Somewhat.
It uninstalls and reinstalls a whole group, thus (possibly) requiring
you to add/edit grub.conf manually.

Last time I check, when "kernel-xen" is already installed, running
"yum install xen", "yum update xen", or simply "yum update" while
having Gitco repo enabled will install updated xen from Gitco which
automatically edit existing grub.conf entry to use newer xen
hypervisor. The magic is in rpm postscript doing something like this

for XENKVER in $(/bin/grep el5xen /boot/grub/menu.lst | /bin/grep
vmlinuz | /bin/sed 's/.*\/vmlinuz-\(.*el5xen\).*/\1/'); do
  /sbin/new-kernel-pkg --package kernel-xen --mkinitrd --depmod
--install --multiboot=/boot/xen.gz-4.0.0 $XENKVER || exit $?
done

Again, I recommend you keep a copy of old and new /boot/grub/menu.lst
to see the difference.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>