[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] libxen+xend vs linux vanilla kernels.

  • To: Xen development list <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Nicholas Lee <emptysands@xxxxxxxxx>
  • Date: Fri, 10 Feb 2006 16:28:53 +1300
  • Delivery-date: Fri, 10 Feb 2006 03:40:14 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=EtmN06SfmXAdWiC05f6DyLqIXlt0wft3eppWawew8ZZBhAsSAyiNwmQn6ulgE3Ptg41RoY/beEuoQOKpZJrYAfoUFtH+T8RlMELlApOBKMKbbI59exG48XeX/Y54gg82PwRYONFAhMX+3eHqBpyOw6V/bT7WXz/GL8GWQl2jamc=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I'm wondering what the long run process will be with regards to
management of the three main components of Xen and the work [1] to put
xen into the vanilla kernel.

Those three components being:
  1. xen micro kernel
  2. linux dom0 kernel
  3. libxen+xend userland control mechanism.

I'm thinking that in the long run with 2.distributed via the vanilla
kernel that 1. and 3. would be split into seperate packages.

For another point of view, for us system integrator non-kernel dev
types. Once xen is frozen into the kernel, in the 3.0 roadmap will the
dependencies between them or api be fixed?

ie. If we upgrade the dom0 kernel will be forced to upgrade the xen
microkernel? Or the reverse, if we upgrade the xen microkernel, will
the dom0 kernel need to be upgraded? etc.

[1] http://xenbits.xensource.com/linux-2.6-xen.hg

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

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.