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-devel] Daily Xen Builds

To: Anthony Liguori <aliguori@xxxxxxxxxx>
Subject: Re: [Xen-devel] Daily Xen Builds
From: Nicholas Lee <emptysands@xxxxxxxxx>
Date: Wed, 12 Oct 2005 11:31:09 +1300
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 11 Oct 2005 22:28:31 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=T9iQQL6XAWjCWnLoERBqSr8V9rA5cQIoGqDc2/t3GzpLQ3hBKgSQ+EgKoDI8vPWzpMs/+c/49kaeQDdr85QGCuvaRLj9WFWyHMbL952QK0ZbkCf6iz/5tU4ZxRVr22p0Nnv73sqvAeUQMwl37oYHhJkhn/Ga2WNI2o8hy+oa91s=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <434C37A9.9070605@xxxxxxxxxx>
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: <1128978545.12366.15.camel@dbarrera_tp> <434ADB55.8050609@xxxxxxxxxx> <2b6116b30510111342p1359bd40t21f4bfac54c3c33@xxxxxxxxxxxxxx> <434C37A9.9070605@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 10/12/05, Anthony Liguori <aliguori@xxxxxxxxxx> wrote:

> This is Open Source.  Soon is when-it's-ready.  6 months is probably a
> safe bet.  I would hold your breath to see a release in the next 1-2
> months though.

Right, I figured that. Its good to know though that we are on the
spiral to stable.

I don't mind running unstable, since we all know that unstable in
Linux land often is the same as SP1 in Windows land. Furthermore, with
OSS we can find out who to hassle. ;)

Problem I'm seeing is I'm not keen to pull a machine in 6 months to
upgrade to 3.0.  From the looks of things it not going to be easy to
both upgrade to 64bit userland and Xen 3.0 remotely for dom0. (*) 
Even though the Xen 2.0  kernel config has an option of x68_64 I
haven't seen anywhere that this works, so 32bit Xen 2.0 seems the only

Finding a good changeset to test and run with should be ok, the main
issue with running Xen I find is the tight coupling between the Xen
userland, kernel and Xen micro kernel.  With a natural kernel you can
install a new kernel config, break it and revert easily via a serial
console.  With Xen its hard to tell if one set of userland/python xm
tools will work with another kernel.

(*) Problem seems to be: Need 64bit python to talk to 64bit Xen. Need
to install 64bit kernel to get 64bit python.

Nicholas Lee
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

Xen-devel mailing list