XenEdgy
|
⇤ ← Revision 1 as of 2006-06-23 08:12:11
Size: 1362
Comment: wip
|
Size: 2936
Comment: draft
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 15: | Line 15: |
| * The kernel will not be a normal Ubuntu kernel so hardware support may not be as good - in particular, drivers from linux-restricted-modules are not going to be supported. | * The kernel will not be a normal Ubuntu kernel so hardware support may not be as good - in particular, drivers from linux-restricted-modules are not going to be supported. Significant support effort for problems with this kernel is not likely to be available. * In the default setup, domU's will not be able to talk to the general Internet. Instead, they will talk only to the dom0 via a private network range. * The arrangements for dealing with the TLS libc problem are not wholly wonderful but unlikely to be catastrophic. |
| Line 19: | Line 21: |
| * Xen hypervisor package. We will sync this from Debian. (xen-3.0) | * Xen hypervisor and tools package. We will sync this from Debian. (xen-3.0) with minor changes. |
| Line 26: | Line 28: |
| === Xen hypervisor package === | === Xen hypervisor and tools package === |
| Line 30: | Line 32: |
| The default networking setup for talking to domU's will be vif-route rather than the bridge. This is less intrusive than bridge-based setup in Xen. We will by default use fixed statically allocated range: 172.20.216.0/24, with .1 reserved for the dom0. (http://www.chiark.greenend.org.uk/ucgi/~ijackson/cam-grin?id=ea9920c2a2ff3e58) We will arange to divert everything in /lib/tls http://wiki.xensource.com/xenwiki/DebianTlsLibcDiversion. |
|
| Line 32: | Line 39: |
| There will be a complely separate kernel-source package which contains a stock upstream kernel with the Xen patches. | There will be a completely separate kernel-source package which contains a stock upstream kernel with the Xen patches applied. The Xen patches are intended for specific upstream kernels (2.6.12 in current xen-3.0 in sid) so we will use whatever upstream kernel version corresponds to the patch in the xen-3.0 we are using. This means the Xen-enabled kernel version in use may change relatively late in the release cycle (compared to the main Ubuntu kernels). === update-grub === The Xen-enabled kernels will have names which show that they are for use with the Xen hypervisor. update-grub will be changed to recognise these and add entries to boot xen with xen kernels, in addition to the normal entries for normal kernels. === xen-support package === Metapackage which depends on the appropriate hypervisor, kernel, and tools. |
Xen in Edgy, probably Universe
Xen is really exciting and several Edgy specs depend on or are related to Xen.
Supporting Xen in the Ubuntu kernels is not practical for Edgy, unfortunately (see XenEnabledKernel).
This spec documents our plan to get some kind of Xen support in Edgy.
Goal
Some reasonably straightforward way of converting an existing install into one which runs as dom0 under Xen, including all of the pieces that are needed to make this work and be useful.
Restrictions
- The kernel will not be a normal Ubuntu kernel so hardware support may not be as good - in particular, drivers from linux-restricted-modules are not going to be supported. Significant support effort for problems with this kernel is not likely to be available.
- In the default setup, domU's will not be able to talk to the general Internet. Instead, they will talk only to the dom0 via a private network range.
- The arrangements for dealing with the TLS libc problem are not wholly wonderful but unlikely to be catastrophic.
Pieces
- Xen hypervisor and tools package. We will sync this from Debian. (xen-3.0) with minor changes.
Kernel. We will provide a stock upstream kernel patched with the Xen guest support.
- Grievous hack to divert tls libc.
- update-grub change to detect Xen setups and add them to the menu. The system will dual boot into Xen+xenkernel and stock ubuntu kernel.
Design
Xen hypervisor and tools package
This is reasonably well-developed upstream and in Debian and we don't expect many changes will be needed.
The default networking setup for talking to domU's will be vif-route rather than the bridge. This is less intrusive than bridge-based setup in Xen. We will by default use fixed statically allocated range: 172.20.216.0/24, with .1 reserved for the dom0. (http://www.chiark.greenend.org.uk/ucgi/~ijackson/cam-grin?id=ea9920c2a2ff3e58)
We will arange to divert everything in /lib/tls http://wiki.xensource.com/xenwiki/DebianTlsLibcDiversion.
Kernel
There will be a completely separate kernel-source package which contains a stock upstream kernel with the Xen patches applied. The Xen patches are intended for specific upstream kernels (2.6.12 in current xen-3.0 in sid) so we will use whatever upstream kernel version corresponds to the patch in the xen-3.0 we are using. This means the Xen-enabled kernel version in use may change relatively late in the release cycle (compared to the main Ubuntu kernels).
update-grub
The Xen-enabled kernels will have names which show that they are for use with the Xen hypervisor. update-grub will be changed to recognise these and add entries to boot xen with xen kernels, in addition to the normal entries for normal kernels.
xen-support package
Metapackage which depends on the appropriate hypervisor, kernel, and tools.
XenEdgy (last edited 2008-08-06 16:36:53 by localhost)