|
version 1.39, 2014/12/24 16:13:59
|
version 1.40, 2014/12/26 13:00:23
|
|
Line 337 running domains:
|
Line 337 running domains:
|
| xm info |
xm info |
| xm list |
xm list |
| |
|
| |
Xen-specific NetBSD issues |
| |
-------------------------- |
| |
|
| |
There are (at least) two additional things different about NetBSD as a |
| |
dom0 kernel compared to hardware. |
| |
|
| |
One is that modules are not usable in DOM0 kernels, so one must |
| |
compile in what's needed. It's not really that modules cannot work, |
| |
but that modules must be built for XEN3_DOM0 because some of the |
| |
defines change and the normal module builds don't do this. Basically, |
| |
enabling Xen changes the kernel ABI, and the module build system |
| |
doesn't cope with this. |
| |
|
| |
The other difference is that XEN3_DOM0 does not have exactly the same |
| |
options as GENERIC. While it is debatable whether or not this is a |
| |
bug, users should be aware of this and can simply add missing config |
| |
items if desired. |
| |
|
| Updating NetBSD in a dom0 |
Updating NetBSD in a dom0 |
| ------------------------- |
------------------------- |
| |
|
|
Line 627 working vif-bridge is also provided with
|
Line 645 working vif-bridge is also provided with
|
| |
|
| #!/bin/sh |
#!/bin/sh |
| #============================================================================ |
#============================================================================ |
| # $NetBSD: howto.mdwn,v 1.38 2014/12/24 16:07:32 gdt Exp $ |
# $NetBSD: howto.mdwn,v 1.39 2014/12/24 16:13:59 gdt Exp $ |
| # |
# |
| # /usr/pkg/etc/xen/vif-bridge |
# /usr/pkg/etc/xen/vif-bridge |
| # |
# |
![[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