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-devel] Re: A proposal - binary

To: Jeff Dike <jdike@xxxxxxxxxxx>
Subject: [Xen-devel] Re: A proposal - binary
From: David Lang <dlang@xxxxxxxxxxxxxxxxxx>
Date: Fri, 4 Aug 2006 15:40:02 -0700 (PDT)
Cc: Andrew Morton <akpm@xxxxxxxx>, zach@xxxxxxxxxx, jeremy@xxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, jeremy@xxxxxxxxxxxxx, simon@xxxxxxxxxxxxx, jlo@xxxxxxxxxx, greg@xxxxxxxxx, Rusty Russell <rusty@xxxxxxxxxxxxxxx>, Antonio Vargas <windenntw@xxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, hch@xxxxxxxxxxxxx, ian.pratt@xxxxxxxxxxxxx, torvalds@xxxxxxxx
Delivery-date: Mon, 07 Aug 2006 02:26:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060804214643.GA6407@xxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <44D2B678.6060400@xxxxxxxxxxxxx> <20060803211850.3a01d0cc.akpm@xxxxxxxx> <1154667875.11382.37.camel@xxxxxxxxxxxxxxxxxxxxx> <20060803225357.e9ab5de1.akpm@xxxxxxxx> <1154675100.11382.47.camel@xxxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.63.0608040944480.18902@xxxxxxxxxxxxxxxxxxx> <69304d110608041146t44077033j9a10ae6aee19a16d@xxxxxxxxxxxxxx> <Pine.LNX.4.63.0608041150360.18862@xxxxxxxxxxxxxxxxxxx> <20060804194549.GA5897@xxxxxxxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.63.0608041246010.18862@xxxxxxxxxxxxxxxxxxx> <20060804214643.GA6407@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, 4 Aug 2006, Jeff Dike wrote:

On Fri, Aug 04, 2006 at 12:49:13PM -0700, David Lang wrote:
Why might you have to do that?

take this with a grain of salt, I'm not saying the particular versions I'm
listing would require this

if your new guest kernel wants to use some new feature (SKAS3, time
virtualization, etc) but the older host kernel didn't support some system
call nessasary to implement it, you may need to upgrade the host kernel to
one that provides the new features.

OK, yeah.

Just making sure you weren't thinking that the UML and host versions
were tied together (although a modern distro won't boot on a 2.6 UML
on a 2.4 host because UML's TLS needs TLS support on the host...).

this is exactly the type of thing that I think is acceptable.

this is a case of a new client needing a new host.

if you have a server running a bunch of 2.4 UMLs on a 2.4 host and want to add a 2.6 UML you can do it becouse you can shift to a buch of 2.4 UMLs (plus one 2.6 UML) running on a 2.6 host.

what I would be bothered by was if you weren't able to run a 2.4 UML on a 2.6 host becouse you have locked out the upgrade path

Everyone needs to remember that this sort of thing does happen, Xen2 clients cannot run on a Xen3 host.

David Lang

Xen-devel mailing list

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