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


[Xen-users] Kernel upgrade in domU

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Kernel upgrade in domU
From: "Guilherme E.J." <guilherme.e@xxxxxxxxx>
Date: Tue, 16 Nov 2010 15:02:59 -0200
Delivery-date: Tue, 16 Nov 2010 09:05:19 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=Xl5XX3ThiNgs5I4b4rvLwH+zhmi+lxzrj2KOtPgYRnE=; b=js8MF2/+yUZ2xNt/EODyMvsSghXvJehqtJ/ikjlnprrM9M8K3ONfo9/STQPaoxifHi 53V8mrv8etDfoC8F2NITBQvksyDnDtxqmvtbldiqAGAlwaYYUGbokNYAJ1mEJWPEcZDw H7LpY4suuw1ak7SjXMEGVu00xJALNU8qqkmoU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Y12oi0gzVt01M7wtcfVP8sjSTp24owXCcFv6Um3r6oIMlo6lq2O/LWsTzgE8fJ3Gfr LfwkOx/EifMALb78Ut7Au3qO2NeoVOGX4z1kTmTwhL9EIAjPRT3BHXrOMVafAFLz/dkE I0pV1gc3w7gMfRvebP019wEXrFy7kDnqYBgog=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

I administrate a lot of xen servers with some linux virtual machines (paravirtualized), and I've some operational problems (costs) to mass upgrade kernel version in domU's.

In a linux server farm (non virtualized servers), the kernel upgrade is trivial, fast and automatized. I simple schedule in my cfengine server, to run "yum update kernel -y && reboot" in all servers.

In a virtualized linux server farm, it's a hard work to upgrade kernel, when needed. First of all, I use cfengine to update kernel-xen package, but after that I've a lot of manual steps that the Operations Department runs:

- Shutdown all virtual machines of xen server X;
- Upgrade kernel and ramdisk of all instances (for example, /xen/hosts/user/i-xxxxx/kernel and /xen/hosts/user/i-xxxxx/ramdisk))
- Upgrade kernel version of dom0
- Reboot dom0

The problem is that I've almost 300 virtual servers, and when we need to upgrade kernel, operations department spend some days to do that.

My question is if this is the best approach to mass upgrade kernel or if exists some tool that I can use to speed up this process?

Any advice is welcome!!


Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>