--- wikisrc/ports/xen/howto.mdwn 2014/12/26 16:43:51 1.46 +++ wikisrc/ports/xen/howto.mdwn 2014/12/26 18:35:45 1.47 @@ -519,34 +519,26 @@ obtain domU kernels. Config files ------------ -The following is an example domain configuration file, lightly -sanitized from a known working on Xen 4.1 (NetBSD 5 amd64 dom0 and -NetBSD 6 i386 domU): +The following is an example domain configuration file +"/usr/pkg/etc/xen/foo", lightly sanitized from a known working on Xen +4.1 (NetBSD 5 amd64 dom0 and NetBSD 6 i386 domU): # -*- mode: python; -*- kernel = "/netbsd-XEN3PAE_DOMU-i386-foo.gz" - memory = 1024 - - name = "foo" - #cpu = -1 - vif = [ 'mac=aa:00:00:d1:00:09,bridge=bridge0' ] - disk = [ 'file:/n0/xen/foo-wd0,0x1,w', 'file:/n0/xen/foo-wd1,0x2,w' ] - root = "xbd0" - autorestart = True -The kernel has the host/domU name in it, so that on the dom0 one can -update the various domUs independently. The vif line causes an -interface to be provided, with a specific mac address (do not reuse -MAC addresses!), in bridge mode. Two disks are provided, and they are -writable. +The domain will have the same name as the file. The kernel has the +host/domU name in it, so that on the dom0 one can update the various +domUs independently. The vif line causes an interface to be provided, +with a specific mac address (do not reuse MAC addresses!), in bridge +mode. Two disks are provided, and they are writable. TODO: explain if the root line is really necessary. TODO: explain or remove autorestart. @@ -697,7 +689,7 @@ working vif-bridge is also provided with #!/bin/sh #============================================================================ - # $NetBSD: howto.mdwn,v 1.45 2014/12/26 16:17:25 gdt Exp $ + # $NetBSD: howto.mdwn,v 1.46 2014/12/26 16:43:51 gdt Exp $ # # /usr/pkg/etc/xen/vif-bridge #