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/
Home Products Support Community News


Re: [Xen-users] Upgrade to 3.1 and backout plan

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Upgrade to 3.1 and backout plan
From: "Fajar A. Nugraha" <fajar@xxxxxxxxxxxxx>
Date: Wed, 26 Sep 2007 09:41:59 +0700
Delivery-date: Tue, 25 Sep 2007 19:42:50 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <46F97313.9050403@xxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <46F97313.9050403@xxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20070728)
Gregory Gee wrote:
>  So I am planning on upgrading my dom0 from 3.0.4 to 3.1.0.  I have
> already done this for the domU's.  But I need to know my backout plan
> if something doesn't go right.  I have a simple question.
>  If I install the 3.1.0 from the tarball, can I still boot the 3.0.4
> dom0 kernel with the 3.1.0 Xen tools if needed?
You can use kernels build for xen 3.0.3 on 3.1, but the xen userland
tools must match xen version.
>   I'm not sure of the compatibility.   I had to compile my own 3.0.4
> kernel because of missing SATA drivers in 2.6.16, but I believe they
> are in 2.6.18, which Xen 3.1.0 is based on.    I'll try and boot the
> 3.1.0 kernel, but if it fails, can I boot the 3.0.4 kernel even though
> the xm tools are 3.1.0?

What distro are you using?
On RHEL5 x86_64 :
- xen.gz is provided by kernel-xen RPM
- xen userland tools is provided by xen RPM, which in turn needs xen-libs

For a clean update to xen 3.1, you need to provide kernel-xen, xen, and
xen-libs RPM.
It also means you can't have kernel-xen updates from RH automatically
used by default (set UPDATEDEFAULT=no in /etc/sysconfig/kernel) since it
has xen.gz from xen 3.0.3.

Here's what I did :
- create my own xen-3.1.0-0.2.fan.x86_64.rpm, using RH's Xen-3.0.5 SRPM
as a starting point
- download RH's xen-3.0.3-25.0.3.el5.x86_64.rpm
xen-libs-3.0.3-25.0.3.el5.x86_64.rpm, for fallback purposes.
- yum erase xen-libs.i386
- rpm -Uvh xen-3.1.0-0.2.fan.x86_64.rpm xen-libs-3.1.0-0.2.fan.x86_64.rpm
- copy /usr/lib64/xen/xen.gz (created by my xen-3.1 rpm) to
- create an entry in /boot/grub/menu.lst that looks like this

title Xen 3.1 (2.6.18-8.1.10.el5xen)
        root (hd0,0)
        kernel /xen.gz-3.1.0-src console=vga
        module /vmlinuz-2.6.18-8.1.10.el5xen ro root=/dev/rootvg/rootlv
quiet xencons=tty
        module /initrd-2.6.18-8.1.10.el5xen.img

note that I just copy an existing kernel-xen section, and change the
"kernel" line.

- set UPDATEDEFAULT=no in /etc/sysconfig/kernel
- reboot

Fallback scenario :
- rpm -Uvh --oldpackage xen-3.0.3-25.0.3.el5.x86_64.rpm
- edit /boot/grub/menu.lst to use the original entry



Xen-users mailing list

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