--- wikisrc/ports/xen/howto.mdwn 2019/04/11 17:33:16 1.165 +++ wikisrc/ports/xen/howto.mdwn 2019/12/17 20:36:16 1.166 @@ -45,12 +45,12 @@ matching versions. Versions available in pkgsrc: [[!table data=""" -Xen Version |Package Name |Xen CPU Support |EOL'ed By Upstream -4.2 |xenkernel42 |32bit, 64bit |Yes -4.5 |xenkernel45 |64bit |Yes -4.6 |xenkernel46 |64bit |Partially -4.8 |xenkernel48 |64bit |No -4.11 |xenkernel411 |64bit |No +Xen Version |Package Name |Xen CPU Support |xm? |EOL'ed By Upstream +4.2 |xenkernel42 |32bit, 64bit |yes |Yes +4.5 |xenkernel45 |64bit | |Yes +4.6 |xenkernel46 |64bit | |Yes +4.8 |xenkernel48 |64bit | |Yes +4.11 |xenkernel411 |64bit | |No """]] See also the [Xen Security Advisory page](http://xenbits.xen.org/xsa/). @@ -66,6 +66,11 @@ domU |Yes Note: NetBSD support is called XEN3. However, it does support Xen 4, because the hypercall interface has remained identical. +Older Xen had a python-based management tool called xm, now replaced +by xl. xm is obsolete, but 4.2 remains in pkgsrc because migrating +from xm to xl is not always trivial, and because 4.2 is the last +version to run on an i386 dom0. + Architecture ------------ @@ -83,7 +88,7 @@ For domUs, i386PAE is considered as [faster](https://lists.xen.org/archives/html/xen-devel/2012-07/msg00085.html) than amd64. -#Creating a dom0 +# Creating a dom0 In order to install a NetBSD as a dom0, one must first install a normal NetBSD system, and then pivot the install to a dom0 install by changing