Diff for /wikisrc/ports/xen/howto.mdwn between versions 1.107 and 1.110

version 1.107, 2016/12/20 04:02:27 version 1.110, 2016/12/20 04:09:54
Line 152  when using a dom0 as a normal computer.) Line 152  when using a dom0 as a normal computer.)
 Architecture  Architecture
 ------------  ------------
   
 Xen itself can run on i386 (some versions) or amd64 machines (all  Xen itself can run on i386 (Xen < 3.1) or amd64 machines (all Xen
 versions).  (Practically, almost any computer where one would want to  versions).  (Practically, almost any computer where one would want to
 run Xen today supports amd64.)  run Xen today supports amd64.)
   
Line 465  Xen-specific NetBSD issues Line 465  Xen-specific NetBSD issues
 There are (at least) two additional things different about NetBSD as a  There are (at least) two additional things different about NetBSD as a
 dom0 kernel compared to hardware.  dom0 kernel compared to hardware.
   
 One is that modules are not usable in DOM0 kernels, so one must  One is that the module ABI is different because some of the #ddefines
 compile in what's needed.  It's not really that modules cannot work,  change, so one must build modules for Xen.  As of netbsd-7, the build
 but that modules must be built for XEN3_DOM0 because some of the  system does this automatically.  TODO: check this.  (Before building
 defines change and the normal module builds don't do this.  Basically,  Xen modules was added, it was awkward to use modules to the point
 enabling Xen changes the kernel ABI, and the module build system  where it was considered that it did not work.)
 doesn't cope with this.  
   
 The other difference is that XEN3_DOM0 does not have exactly the same  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  options as GENERIC.  While it is debatable whether or not this is a
Line 522  TODO: actually do this and fix it if nec Line 521  TODO: actually do this and fix it if nec
 Upgrading Xen versions  Upgrading Xen versions
 ---------------------  ---------------------
   
 Updating Xen is conceptually not difficult, but can run into all the  Minor version upgrades are trivial.  Just rebuild/replace the
 issues found when installing Xen.  Assuming migration from 4.1 to 4.2,  xenkernel version and copy the new xen.gz to / (where /boot.cfg
 remove the xenkernel41 and xentools41 packages and install the  references it), and reboot.
 xenkernel42 and xentools42 packages.  Copy the 4.2 xen.gz to /.  
   Major version upgrades are conceptually not difficult, but can run
   into all the issues found when installing Xen.  Assuming migration
   from 4.1 to 4.2, remove the xenkernel41 and xentools41 packages and
   install the xenkernel42 and xentools42 packages.  Copy the 4.2 xen.gz
   to /.
   
 Ensure that the contents of /etc/rc.d/xen* are correct.  Specifically,  Ensure that the contents of /etc/rc.d/xen* are correct.  Specifically,
 they must match the package you just installed and not be left over  they must match the package you just installed and not be left over
Line 535  Enable the correct set of daemons; see t Line 539  Enable the correct set of daemons; see t
 (Upgrading from 3.x to 4.x without doing this will result in a hang.)  (Upgrading from 3.x to 4.x without doing this will result in a hang.)
   
 Ensure that the domU config files are valid for the new version.  Ensure that the domU config files are valid for the new version.
 Specifically: remove autorestart=True, and ensure that disks are  Specifically, for 4.x remove autorestart=True, and ensure that disks
 specified with numbers as the second argument, as the examples above  are specified with numbers as the second argument, as the examples
 show, and not NetBSD device names.  above show, and not NetBSD device names.
   
 Hardware known to work  Hardware known to work
 ----------------------  ----------------------

Removed from v.1.107  
changed lines
  Added in v.1.110


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb