--- wikisrc/ports/xen/howto.mdwn 2016/12/20 04:07:39 1.109 +++ wikisrc/ports/xen/howto.mdwn 2016/12/20 04:09:54 1.110 @@ -521,10 +521,15 @@ TODO: actually do this and fix it if nec Upgrading Xen versions --------------------- -Updating Xen is 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 /. +Minor version upgrades are trivial. Just rebuild/replace the +xenkernel version and copy the new xen.gz to / (where /boot.cfg +references it), and reboot. + +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, they must match the package you just installed and not be left over @@ -534,9 +539,9 @@ Enable the correct set of daemons; see t (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. -Specifically: remove autorestart=True, and ensure that disks are -specified with numbers as the second argument, as the examples above -show, and not NetBSD device names. +Specifically, for 4.x remove autorestart=True, and ensure that disks +are specified with numbers as the second argument, as the examples +above show, and not NetBSD device names. Hardware known to work ----------------------