version 1.167, 2019/12/17 20:59:09
|
version 1.168, 2020/04/03 10:48:35
|
Line 657 A second issue is multiple CPUs. With N
|
Line 657 A second issue is multiple CPUs. With N
|
multiple vcpus, and it is typical for VPS providers to enable multiple |
multiple vcpus, and it is typical for VPS providers to enable multiple |
CPUs for NetBSD domUs. |
CPUs for NetBSD domUs. |
|
|
pygrub |
|
------- |
|
|
|
pygrub runs in the dom0 and looks into the domU file system. This |
|
implies that the domU must have a kernel in a file system in a format |
|
known to pygrub. As of 2014, pygrub seems to be of mostly historical |
|
interest. |
|
|
|
pvgrub |
pvgrub |
------ |
------ |
|
|
Line 691 partition for the kernel with the intent
|
Line 683 partition for the kernel with the intent
|
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 partition. |
to update the special boot partition. |
|
|
|
pygrub |
|
------- |
|
|
|
pygrub runs in the dom0 and looks into the domU file system. This |
|
implies that the domU must have a kernel in a file system in a format |
|
known to pygrub. |
|
|
|
pygrub doesn't seem to work to load Linux images under NetBSD dom0, |
|
and is inherently less secure than pvgrub due to running inside dom0. For both these |
|
reasons, pygrub should not be used, and is only still present so that |
|
historical DomU images using it still work. |
|
|
|
As of 2014, pygrub seems to be of mostly historical |
|
interest. New DomUs should use pvgrub. |
|
|
Amazon |
Amazon |
------ |
------ |
|
|