|
version 1.74, 2015/01/04 02:18:47
|
version 1.77, 2015/01/17 01:36:44
|
|
Line 274 For debugging, one may copy xen-debug.gz
|
Line 274 For debugging, one may copy xen-debug.gz
|
| to DIAGNOSTIC and DEBUG in NetBSD. xen-debug.gz is basically only |
to DIAGNOSTIC and DEBUG in NetBSD. xen-debug.gz is basically only |
| useful with a serial console. Then, place a NetBSD XEN3_DOM0 kernel |
useful with a serial console. Then, place a NetBSD XEN3_DOM0 kernel |
| in /, copied from releasedir/amd64/binary/kernel/netbsd-XEN3_DOM0.gz |
in /, copied from releasedir/amd64/binary/kernel/netbsd-XEN3_DOM0.gz |
| of a NetBSD build. Both xen and NetBSD may be left compressed. (If |
of a NetBSD build. If using i386, use |
| using i386, use releasedir/i386/binary/kernel/netbsd-XEN3PAE_DOM0.gz.) |
releasedir/i386/binary/kernel/netbsd-XEN3PAE_DOM0.gz. (If using Xen |
| |
3.1 and i386, you may use XEN3_DOM0 with the non-PAE Xen. But you |
| With Xen as the kernel, you must provide a dom0 NetBSD kernel to be |
should not use Xen 3.1.) Both xen and the NetBSD kernel may be (and |
| used as a module; place this in /. Suitable kernels are provided in |
typically are) left compressed. |
| releasedir/binary/kernel: |
|
| |
In a dom0 kernel, kernfs is mandatory for xend to comunicate with the |
| i386 XEN3_DOM0 |
kernel, so ensure that /kern is in fstab. TODO: Say this is default, |
| i386 XEN3PAE_DOM0 |
or file a PR and give a reference. |
| amd64 XEN3_DOM0 |
|
| |
|
| The first one is only for use with Xen 3.1 and i386-mode Xen (and you |
|
| should not do this). Current Xen always uses PAE on i386, but you |
|
| should generally use amd64 for the dom0. In a dom0 kernel, kernfs is |
|
| mandatory for xend to comunicate with the kernel, so ensure that /kern |
|
| is in fstab. TODO: Say this is default, or file a PR and give a |
|
| reference. |
|
| |
|
| Because you already installed NetBSD, you have a working boot setup |
Because you already installed NetBSD, you have a working boot setup |
| with an MBR bootblock, either bootxx_ffsv1 or bootxx_ffsv2 at the |
with an MBR bootblock, either bootxx_ffsv1 or bootxx_ffsv2 at the |
| 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. In an attempt to add performance, one can also |
allocated for domUs. To use a serial console, use |
| 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 314 As with non-Xen systems, you should have
|
Line 312 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 332 Configuring Xen
|
Line 333 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: |
![[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