version 1.42, 2014/12/26 13:10:00
|
version 1.43, 2014/12/26 13:15:32
|
Line 301 is using xm or xl. Note that xend is fo
|
Line 301 is using xm or xl. Note that xend is fo
|
only be used if you plan on using "xm". Do NOT enable xend if you |
only be used if you plan on using "xm". Do NOT enable xend if you |
plan on using "xl" as it will cause problems. |
plan on using "xl" as it will cause problems. |
|
|
|
The installation of NetBSD should already have created devices for xen |
|
(xencons, xenevt), but if they are not present, create them: |
|
|
|
cd /dev && sh MAKEDEV xen |
|
|
TODO: Give 3.1 advice (or remove it from pkgsrc). |
TODO: Give 3.1 advice (or remove it from pkgsrc). |
|
|
For 3.3 (and thus xm), add to rc.conf (but note that you should have |
For 3.3 (and thus xm), add to rc.conf (but note that you should have |
Line 329 For 4.2 with xl (preferred), add to rc.c
|
Line 334 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 eitehr started them or |
After you have configured the daemons and either started them or |
rebooted, run the following (or use xl) to inspect Xen's boot |
rebooted, run the following (or use xl) to inspect Xen's boot |
messages, available resources, and running domains: |
messages, available resources, and running domains: |
|
|
xm dmesg |
# xm dmesg |
xm info |
[xen's boot info] |
xm list |
# xm info |
|
[available memory, etc.] |
|
# xm list |
|
Name Id Mem(MB) CPU State Time(s) Console |
|
Domain-0 0 64 0 r---- 58.1 |
|
|
anita (for testing NetBSD) |
anita (for testing NetBSD) |
-------------------------- |
-------------------------- |
Line 513 Creating specific unprivileged domains (
|
Line 522 Creating specific unprivileged domains (
|
|
|
Creating domUs is almost entirely independent of operating system. We |
Creating domUs is almost entirely independent of operating system. We |
first explain NetBSD, and then differences for Linux and Solaris. |
first explain NetBSD, and then differences for Linux and Solaris. |
|
Note that you must have already completed the dom0 setup so that "xm |
|
list" (or "xl list") works. |
|
|
Creating an unprivileged NetBSD domain (domU) |
Creating an unprivileged NetBSD domain (domU) |
--------------------------------------------- |
--------------------------------------------- |
|
|
Once you have *domain0* running, you need to start the xen tool daemon |
|
(`/usr/pkg/share/examples/rc.d/xend start`) and the xen backend daemon |
|
(`/usr/pkg/share/examples/rc.d/xenbackendd start` for Xen3\*, |
|
`/usr/pkg/share/examples/rc.d/xencommons start` for Xen4.\*). Make sure |
|
that `/dev/xencons` and `/dev/xenevt` exist before starting `xend`. You |
|
can create them with this command: |
|
|
|
# cd /dev && sh MAKEDEV xen |
|
|
|
xend will write logs to `/var/log/xend.log` and |
|
`/var/log/xend-debug.log`. You can then control xen with the xm tool. |
|
'xm list' will show something like: |
|
|
|
# xm list |
|
Name Id Mem(MB) CPU State Time(s) Console |
|
Domain-0 0 64 0 r---- 58.1 |
|
|
|
'xm create' allows you to create a new domain. It uses a config file in |
'xm create' allows you to create a new domain. It uses a config file in |
PKG\_SYSCONFDIR for its parameters. By default, this file will be in |
PKG\_SYSCONFDIR for its parameters. By default, this file will be in |
`/usr/pkg/etc/xen/`. On creation, a kernel has to be specified, which |
`/usr/pkg/etc/xen/`. On creation, a kernel has to be specified, which |
Line 657 working vif-bridge is also provided with
|
Line 651 working vif-bridge is also provided with
|
|
|
#!/bin/sh |
#!/bin/sh |
#============================================================================ |
#============================================================================ |
# $NetBSD: howto.mdwn,v 1.41 2014/12/26 13:04:31 gdt Exp $ |
# $NetBSD: howto.mdwn,v 1.42 2014/12/26 13:10:00 gdt Exp $ |
# |
# |
# /usr/pkg/etc/xen/vif-bridge |
# /usr/pkg/etc/xen/vif-bridge |
# |
# |