Diff for /wikisrc/ports/xen/howto.mdwn between versions 1.71 and 1.74

version 1.71, 2015/01/04 02:14:15 version 1.74, 2015/01/04 02:18:47
Line 883  configuration.  The big issue is usually Line 883  configuration.  The big issue is usually
 is booted, because the kernel is nominally in the dom0 filesystem (to  is booted, because the kernel is nominally in the dom0 filesystem (to
 which VPS users do not normally have acesss).  A second issue is how  which VPS users do not normally have acesss).  A second issue is how
 to install NetBSD.  to install NetBSD.
   
 A VPS user may want to compile a kernel for security updates, to run  A VPS user may want to compile a kernel for security updates, to run
 npf, run IPsec, or any other reason why someone would want to change  npf, run IPsec, or any other reason why someone would want to change
 their kernel.  their kernel.
Line 894  or to select from a prepopulated list.   Line 893  or to select from a prepopulated list.  
 kernel from the domU filesystem.  This is closer to a regular physical  kernel from the domU filesystem.  This is closer to a regular physical
 computer, where someone who controls a machine can replace the kernel.  computer, where someone who controls a machine can replace the kernel.
   
   A second issue is multiple CPUs.  With NetBSD 6, domUs support
   multiple vcpus, and it is typical for VPS providers to enable multiple
   CPUs for NetBSD domUs.
   
 pygrub  pygrub
 -------  -------
   
Line 913  calls.  It is booted from the dom0 as th Line 916  calls.  It is booted from the dom0 as th
 that pvgrub works with FFsv2 with 16K/2K and 32K/4K block/frag sizes  that pvgrub works with FFsv2 with 16K/2K and 32K/4K block/frag sizes
 (and hence with defaults from "newfs -O 2").  See [Panix's pvgrub  (and hence with defaults from "newfs -O 2").  See [Panix's pvgrub
 page](http://www.panix.com/v-colo/grub.html), which describes only  page](http://www.panix.com/v-colo/grub.html), which describes only
 Linux but should be updated to cover NetBSD :-)  Linux but should be updated to cover NetBSD :-).
   
 [prgmr.com](http://prgmr.com/) also lets users with pvgrub to boot  [prgmr.com](http://prgmr.com/) also lets users with pvgrub to boot
 their own kernel.  See then [prgmr.com NetBSD  their own kernel.  See then [prgmr.com NetBSD
 HOWTO](http://wiki.prgmr.com/mediawiki/index.php/NetBSD_as_a_DomU).  HOWTO](http://wiki.prgmr.com/mediawiki/index.php/NetBSD_as_a_DomU)
   (which is in need of updating).
   
 It appears that [grub's FFS  It appears that [grub's FFS
 code](http://xenbits.xensource.com/hg/xen-unstable.hg/file/bca284f67702/tools/libfsimage/ufs/fsys_ufs.c)  code](http://xenbits.xensource.com/hg/xen-unstable.hg/file/bca284f67702/tools/libfsimage/ufs/fsys_ufs.c)
 does not support all aspects of modern FFS, but there are also reports  does not support all aspects of modern FFS, but there are also reports
 that FFSv2 works fine.  At prmgr, typically one has an ext2 or FAT  that FFSv2 works fine.  At prgmr, typically one has an ext2 or FAT
 partition for the kernel with the intent that grub can understand it,  partition for the kernel with the intent that grub can understand it,
 which leads to /netbsd not being the actual kernel.  One must remember  which leads to /netbsd not being the actual kernel.  One must remember
 to update the special boot partiion.  to update the special boot partiion.

Removed from v.1.71  
changed lines
  Added in v.1.74


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