|
version 1.75, 2015/01/17 01:32:12
|
version 1.79, 2015/01/17 12:56:36
|
|
Line 100 Note that NetBSD support is called XEN3.
|
Line 100 Note that NetBSD support is called XEN3.
|
| Xen command program |
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 |
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 |
called xl is provided, but it does not work well in 4.1. In 4.2, both |
| the last version that has "xm". |
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 |
NetBSD |
| ------ |
------ |
|
Line 289 with an MBR bootblock, either bootxx_ffs
|
Line 290 with an MBR bootblock, either bootxx_ffs
|
| beginning of your root filesystem, /boot present, and likely |
beginning of your root filesystem, /boot present, and likely |
| /boot.cfg. (If not, fix before continuing!) |
/boot.cfg. (If not, fix before continuing!) |
| |
|
| See boot.cfg(5) for an example. The basic line is |
Add a line to to /boot.cfg to boot Xen. See boot.cfg(5) for an |
| |
example. The basic line is |
| |
|
| menu=Xen:load /netbsd-XEN3_DOM0.gz console=pc;multiboot /xen.gz dom0_mem=256M |
menu=Xen:load /netbsd-XEN3_DOM0.gz console=pc;multiboot /xen.gz dom0_mem=256M |
| |
|
| which specifies that the dom0 should have 256M, leaving the rest to be |
which specifies that the dom0 should have 256M, leaving the rest to be |
| allocated for domUs. To use In an attempt to add performance, one can |
allocated for domUs. To use a serial console, use |
| also add |
|
| |
menu=Xen:load /netbsd-XEN3_DOM0.gz console=com0;multiboot /xen.gz dom0_mem=256M console=com1 com1=9600,8n1 |
| |
|
| |
which will use the first serial port for Xen (which counts starting |
| |
from 1), forcing speed/parity, and also for NetBSD (which counts |
| |
starting at 0). In an attempt to add performance, one can also add |
| |
|
| dom0_max_vcpus=1 dom0_vcpus_pin |
dom0_max_vcpus=1 dom0_vcpus_pin |
| |
|
|
Line 306 As with non-Xen systems, you should have
|
Line 313 As with non-Xen systems, you should have
|
| kernel that works without Xen) and fallback versions of the non-Xen |
kernel that works without Xen) and fallback versions of the non-Xen |
| kernel, Xen, and the dom0 kernel. |
kernel, Xen, and the dom0 kernel. |
| |
|
| |
Now, reboot so that you are running a DOM0 kernel under Xen, rather |
| |
than GENERIC without Xen. |
| |
|
| Using grub (historic) |
Using grub (historic) |
| --------------------- |
--------------------- |
| |
|
|
Line 324 Configuring Xen
|
Line 334 Configuring Xen
|
| |
|
| Xen logs will be in /var/log/xen. |
Xen logs will be in /var/log/xen. |
| |
|
| Now, you have a system that will boot Xen and the dom0 kernel, and |
Now, you have a system that will boot Xen and the dom0 kernel, but not |
| just run the dom0 kernel. There will be no domUs, and none can be |
do anything else special. Make sure that you have rebooted into Xen. |
| started because you still have to configure the dom0 tools. The |
There will be no domUs, and none can be started because you still have |
| daemons which should be run vary with Xen version and with whether one |
to configure the dom0 tools. The daemons which should be run vary |
| is using xm or xl. Note that xend is for supporting "xm", and should |
with Xen version and with whether one is using xm or xl. Note that |
| only be used if you plan on using "xm". Do NOT enable xend if you |
xend is for supporting "xm", and should only be used if you plan on |
| plan on using "xl" as it will cause problems. |
using "xm". Do NOT enable xend if you plan on using "xl" as it will |
| |
cause problems. |
| |
|
| The installation of NetBSD should already have created devices for xen |
The installation of NetBSD should already have created devices for xen |
| (xencons, xenevt), but if they are not present, create them: |
(xencons, xenevt), but if they are not present, create them: |
|
Line 358 For 4.2 with xm, add to rc.conf
|
Line 369 For 4.2 with xm, add to rc.conf
|
| xencommons=YES |
xencommons=YES |
| xend=YES |
xend=YES |
| |
|
| For 4.2 with xl (preferred), add to rc.conf: |
For 4.2 with xl, add to rc.conf: |
| |
|
| xencommons=YES |
xencommons=YES |
| TODO: explain if there is a xend replacement |
TODO: explain if there is a xend replacement |
|
Line 366 For 4.2 with xl (preferred), add to rc.c
|
Line 377 For 4.2 with xl (preferred), add to rc.c
|
| TODO: Recommend for/against xen-watchdog. |
TODO: Recommend for/against xen-watchdog. |
| |
|
| After you have configured the daemons and either started them (in the |
After you have configured the daemons and either started them (in the |
| order given) or rebooted, run the following (or use xl) to inspect |
order given) or rebooted, use xm or xl to inspect Xen's boot messages, |
| Xen's boot messages, available resources, and running domains: |
available resources, and running domains. An example with xm follows: |
| |
|
| # xm dmesg |
# xm dmesg |
| [xen's boot info] |
[xen's boot info] |
|
Line 377 Xen's boot messages, available resources
|
Line 388 Xen's boot messages, available resources
|
| Name Id Mem(MB) CPU State Time(s) Console |
Name Id Mem(MB) CPU State Time(s) Console |
| Domain-0 0 64 0 r---- 58.1 |
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) |
anita (for testing NetBSD) |
| -------------------------- |
-------------------------- |
| |
|
| With the setup so far, one should be able to run anita (see |
With the setup so far, one should be able to run anita (see |
| pkgsrc/sysutils/py-anita) to test NetBSD releases, by doing (as root, |
pkgsrc/misc/py-anita) to test NetBSD releases, by doing (as root, |
| because anita must create a domU): |
because anita must create a domU): |
| |
|
| anita --vmm=xm test file:///usr/obj/i386/ |
anita --vmm=xm test file:///usr/obj/i386/ |
![[BACK]](/icons/back.gif){kind=icon}
Return to howto.mdwn CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [NetBSD Developer Wiki] / wikisrc / ports / xen