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

To: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] Brolen virtual machines after updates host system
From: "Kris Doosje" <k.doosje@xxxxxxx>
Date: Mon, 4 Sep 2006 13:03:21 +0200
Delivery-date: Mon, 04 Sep 2006 04:09:49 -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
Do you have two kernels on your Xen-server, one for dom0 and one for domU? If 
you use your dom0 kernel also for your domU's, then ofcourse you need to copy 
the correct kernel modules to the virtual-servers' filesystems. If you have a 
seperate kernel for your domU's, and that one does not change, you don't need 
to update the virtual-servers in any way after doing updates on the dom0 kernel.

- Kris

-----Oorspronkelijk bericht-----
Van: Jan Albrecht [mailto:jan.albrecht@xxxxxxxxx]
Verzonden: maandag 4 september 2006 13:00
Aan: xen-users@xxxxxxxxxxxxxxxxxxx
Onderwerp: Re: [Xen-users] Brolen virtual machines after updates host
system


I upgraded the dom0 Kernel. And yes, it is modified (by openSuSE) for XEN.

My poblem is, that I need to have to modfiy the virtual guests (i.e.
copy the correct kernel modules into their filesystems).
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)?

Thanks
J

Galileon Galilei wrote:
> you upgraded the host kernel? in this case, is the new one
> xen-enabled? because the domain0 kernel should always be modified for
> xen...
>
> if it is xen-modified, is xend running? open a console, type
>
> xm list
>
>
> to see if the dom0 is listed....if your new kernel is not
> xen-modified, (plus maybe xen isnt loading at all), you should still
> have an option to boot into the old kernel thru grub when you start
> the computer...
>
>
> On 9/4/06, *Jan Albrecht* <jan.albrecht@xxxxxxxxx
> <mailto:jan.albrecht@xxxxxxxxx>> wrote:
>
>     Hi all,
>
>     I've a little problem here.
>     I'm using SuSE 10.1 as a host system. I had various virtual machines
>     (debian,centos,SuSE,...) running on it.
>     Last week I did a full upgrade on the host system, even a new kernel.
>     After the upgrade all virtual systems had problems, which lasted in
>     not be able to boot systems.
>
>     I know what happened, but my question: Is there a way to upgrade a
>     host system without needing to touch the virtual machines? Or do I
>     always have to patch a virtual host after patching the host system
>     itself?
>     Would this be possible with the virtual system supporting hardware
>     from Intel/AMD?
>
>     Thanks
>     Jan
>
>     --
>     http://blog.salid.de
>
>     _______________________________________________
>     Xen-users mailing list
>     Xen-users@xxxxxxxxxxxxxxxxxxx <mailto:Xen-users@xxxxxxxxxxxxxxxxxxx>
>     http://lists.xensource.com/xen-users
>
>


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

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