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] Brolen virtual machines after updates host system

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] Brolen virtual machines after updates host system
From: "Steffen Heil" <lists@xxxxxxxxxxxxxxx>
Date: Mon, 4 Sep 2006 19:30:47 +0200
Delivery-date: Mon, 04 Sep 2006 10:30:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <44FC0732.8080802@xxxxxxxxx>
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbQEWyAX9C9puoAQiets5lsMOyj1AANmPqA

> My poblem is, that I need to have to modfiy the virtual guests (i.e.
> copy the correct kernel modules into their filesystems).

So you updated the domUs kernels when updating the dom0 kernel?
That's the problem.

Make a copy (or hardlink) of each used kernel for each guest and let the
guests use those copies.
So they have their kernel and will work independently of updates.
You can then also update domUs kernels distinctly...

> My question is, if there is any way to get around this (as we're plan 
> to use various instaces of XEN guests without touching them at every 
> update)?

See above.


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Xen-users mailing list