|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] libxen+xend vs linux vanilla kernels.
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
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF 5BDD 07B0 9597 6D58 D70C
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-devel] libxen+xend vs linux vanilla kernels.,
Nicholas Lee <=
|
|
|
|
|