--- wikisrc/ports/xen/howto.mdwn 2015/01/17 01:37:37 1.78 +++ wikisrc/ports/xen/howto.mdwn 2015/01/17 13:04:01 1.80 @@ -100,10 +100,11 @@ Note that NetBSD support is called XEN3. Xen command program ------------------- -Early Xen used a program called "xm" to manipulate the system from the +Early Xen used a program called xm to manipulate the system from the dom0. Starting in 4.1, a replacement program with similar behavior -called "xl" is provided. In 4.2 and later, "xl" is preferred. 4.4 is -the last version that has "xm". +called xl is provided, but it does not work well in 4.1. In 4.2, both +xm and xl work fine. 4.4 is the last version that has xm. You must +choose one or the other, because it affects which daemons you run. NetBSD ------ @@ -368,7 +369,7 @@ For 4.2 with xm, add to rc.conf xencommons=YES xend=YES -For 4.2 with xl (preferred), add to rc.conf: +For 4.2 with xl, add to rc.conf: xencommons=YES TODO: explain if there is a xend replacement @@ -376,8 +377,8 @@ For 4.2 with xl (preferred), add to rc.c TODO: Recommend for/against xen-watchdog. After you have configured the daemons and either started them (in the -order given) or rebooted, run the following (or use xl) to inspect -Xen's boot messages, available resources, and running domains: +order given) or rebooted, use xm or xl to inspect Xen's boot messages, +available resources, and running domains. An example with xm follows: # xm dmesg [xen's boot info] @@ -387,6 +388,10 @@ Xen's boot messages, available resources Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 64 0 r---- 58.1 +With xl, the commands are the same, and the output may be slightly +different. TODO: add example output for xl, after confirming on 4.2 +and resolving the TODO about rc.conf. + anita (for testing NetBSD) -------------------------- @@ -397,7 +402,7 @@ because anita must create a domU): anita --vmm=xm test file:///usr/obj/i386/ Alternatively, one can use --vmm=xl to use xl-based domU creation instead. -TODO: check this. +TODO: check this, and make the example use xl when confirmed. Xen-specific NetBSD issues --------------------------