You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 23, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: en/_start.html
+5
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,11 @@
30
30
</div>
31
31
<divid="referat"></div>
32
32
<divclass="content">
33
+
<!--
34
+
<div class="warning">
35
+
<p>2023-02 upd: important announcement. Due to the loss of the main server (non-technical problems related to paying for hosting), the CBSD-related images (ISO, cloud images, jail images ...) will be unavailable indefinitely.</p>
36
+
</div>
37
+
-->
33
38
<divclass="block black-text info">
34
39
<p>2020-10 upd: we reached the first fundraising goal and rented a server in Hetzner for development! Thank you for <atarget="_blank" href="https://www.patreon.com/clonos">donating</a> !</p>
Copy file name to clipboardExpand all lines: en/cbsd_additional.html
+22-6
Original file line number
Diff line number
Diff line change
@@ -221,20 +221,36 @@ <h2><a name="jnameasmask">Multiple operation by jname as mask</a></h2>
221
221
<h2><aname="hier">A brief summary of the filesystem hierarchy <strong>CBSD</strong></a></h2>
222
222
<divclass="block">
223
223
<tableclass="images">
224
-
<tr><tdclass="bg-gray">${workdir}/.rssh/</td><td>This directory stores the private keys of remote nodes. The files are added and removed via the command <strong>cbsd node</strong></td></tr>
225
-
<tr><tdclass="bg-gray">${workdir}/.ssh</td><td>This directory stores the private and public keys of the nodes. The directory is created during initialization with the command <strong><em>cbsd initenv</em></strong>. This is also where the public key comes from when the command <strong>cbsd node mode=add</strong> is issued to copy the pub key to a remote host. The Key file name is the md5 sum of the nodename. In addition, this key pair is used by default when working with cloud images of virtual machines, For example, in the operations 'cbsd bexec, cbsd bscp, cbsd blogin'</td></tr>
224
+
<tr><tdclass="bg-gray"><strong>${workdir}/.rssh/</strong></td><td>This directory stores the private keys of remote nodes. The files are added and removed via the command <strong>cbsd node</strong></td></tr>
225
+
<tr><tdclass="bg-gray"><strong>${workdir}/.ssh</strong></td><td>This directory stores the private and public keys of the nodes. The directory is created during initialization with the command <strong><em>cbsd initenv</em></strong>. This is also where the public key comes from when the command <strong>cbsd node mode=add</strong> is issued to copy the pub key to a remote host. The Key file name is the md5 sum of the nodename. In addition, this key pair is used by default when working with cloud images of virtual machines, For example, in the operations 'cbsd bexec, cbsd bscp, cbsd blogin'</td></tr>
226
226
<tr><tdclass="bg-gray">${workdir}/basejail</td><td>This directory is used to store the bases and kernels for FreeBSD that are used when creating baserw=0 jails. These are generated via cbsd buildworld/buildkernel, cbsd installworld/installkernel, or cbsd repo action=get sources=base/kernel)</td></tr>
227
227
<tr><tdclass="bg-gray">${workdir}/etc</td><td>Configuration files needed to run <strong>CBSD</strong></td></tr>
228
228
<tr><tdclass="bg-gray">${workdir}/export</td><td>The default directory that will be stored in a file exported by the jail (a cbsd jexport jname=$jname, this directory will file $jname.img)</td></tr>
229
229
<tr><tdclass="bg-gray">${workdir}/import</td><td>The default directory containing data to be imported to a jail (a cbsd jimport jname=$jname, will be deployed jail $jname)</td></tr>
230
230
<tr><tdclass="bg-gray">${workdir}/jails</td><td>This directory contains the mount point for the root jails that use baserw=0.</td></tr>
231
-
<tr><tdclass="bg-gray">${workdir}/jails-data</td><td>This directory stores all jail data. Backup these directories to take a backup of the jails (including fstab and rc.conf files). Note: if a jail uses baserw=1, these directories are the root of the jail when it starts.</td></tr>
232
-
<tr><tdclass="bg-gray">${workdir}/jails-fstab</td><td>The fstab file for the jails. The syntax for regular FreeBSD with the only exception that the path to the mount point is written relative to the root <em>jail</em> (record <strong>/usr/ports /usr/ports nullfs rw 0 0 </strong> in the file fstab.$jname means that of the master node directory /usr/ports will be mounted at startup in ${workdir}/jails/$jname/usr/ports)</td></tr>
233
-
<tr><tdclass="bg-gray">${workdir}/jails-rcconf</td><td>rc.conf files for jail creation. These parameters can be changed using $editor, or via the command <strong><em>cbsd jset $jname param=val</em></strong> (eg <em>cbsd jset jname=$jname ip="192.168.0.2/24"</em>). To change these settings, the jail should be turned <strong>off</strong>. </td></tr>
234
-
<tr><tdclass="bg-gray">${workdir}/jails-system</td><td> This directory may contain some helper scripts related to the jail (eg wizards to configure, configurators, etc) as well as the preserved jail traffic when using ipfw and its description. This catalog participates in jimport/jexport operations and migration of jail</td></tr>
231
+
<tr><tdclass="bg-gray"><fontstyle="color:RED"><strong>${workdir}/jails-data</strong></font></td><td>This directory stores all jail/VM data. Backup these directories to take a backup of the jails (including fstab and rc.conf files). Note: if a jail uses baserw=1, these directories are the root of the jail when it starts. <fontstyle="color:red">Pay attention!</font> when using ZVOL, in fact, the virtual disk are located in/as ZVOL and jails-data/ENV has only symbolic links - please take into consideration this when planning backup/DR!. This directory (or volume, which indicate symlinks to) is subject to backup copying if you want to restore your virtual environment in the case of failures.</td></tr>
232
+
<tr><tdclass="bg-gray"><strong>${workdir}/jails-fstab</strong></td><td>The fstab file for the jails. The syntax for regular FreeBSD with the only exception that the path to the mount point is written relative to the root <em>jail</em> (record <strong>/usr/ports /usr/ports nullfs rw 0 0 </strong> in the file fstab.$jname means that of the master node directory /usr/ports will be mounted at startup in ${workdir}/jails/$jname/usr/ports)</td></tr>
233
+
<tr><tdclass="bg-gray">${workdir}/jails-rcconf</td><td>rc.conf files for jail creation. These parameters can be changed using $editor, or via the command <strong><em>cbsd jset $jname param=val</em></strong> (eg <em>cbsd jset jname=$jname ip="192.168.0.2/24"</em>). To change these settings, the jail should be turned <strong>off</strong>. </td></tr>
234
+
<tr><tdclass="bg-gray"><strong>${workdir}/jails-system</strong></td><td> This directory may contain some helper scripts related to the jail (eg wizards to configure, configurators, etc) as well as the preserved jail traffic when using ipfw and its description. This catalog participates in jimport/jexport operations and migration of jail. This catalog is subject to backup copying if you want to restore the <strong>CBSD</strong> during failures. </td></td></tr>
235
235
<tr><tdclass="bg-gray">${workdir}/var</td><td> This directory contains system information for <strong>CBSD</strong>. For example, in ${workdir}/var/db is an inventory of local and remote nodes that were added. </td></tr>
236
+
<tr><tdclass="bg-gray"><strong>${workdir}/var/db</strong></td><td> The main and the most important SQLite3 CBSD base, it is indicated by a sympathetic link <strong>local.sqlite</strong>. This catalog is subject to backup copying if you want to restore the <strong>CBSD</strong> during failures. </td></tr>
236
237
<tr><tdclass="bg-gray">/usr/local/cbsd</td><td> A copy of the original files installed by the <strong>CBSD</strong> port. The working scripts for sudoexec can also be found here. </td></tr>
237
238
</table>
239
+
<p>For example, for manual transfer of a container/VM from the <strong>CBSD</strong> structure, you need a SQLite3 database indicated by a symbolic link ~cbsd/var/db/local.sqlite. Its contents (table jails, bhyve, xen ..) is responsible for the list of registered environment, for example:</p>
240
+
<pre>
241
+
sqlite3 ~cbsd/var/db/local.sqlite "SELECT * from jails";
<p>Also, you need a rootfs container in the ~cbsd/jails-data/JAILNAME-data directory</p>
247
+
<p>As for virtual machines, you need to additionally check whether the discs of virtual machines ZVOL-based ( zfs list | egrep "dsk [0-9]+.vhd"), as well as, be sure to copy ~cbsd/jails-system/ENVNAME/, where there are a virtual machine settings in the local.sqlite file:</p>
248
+
<pre>
249
+
sqlite3 ~cbsd/jails-system/VMNAME/local.sqlite "SELECT * from settings";
Copy file name to clipboardExpand all lines: en/cbsd_qemu_quickstart.html
+10
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,11 @@ <h2><a name="knowit">CBSD and QEMU</a></h2>
22
22
kldload nvmm
23
23
</pre>
24
24
25
+
<p>Don't forget to add nvmm into auto-load via /boot/loader.conf:</p>
26
+
<pre>
27
+
nvmm_load="YES"
28
+
</pre>
29
+
25
30
<p>You can check the status of NVMM through the command:</p>
26
31
<preclass="brush:bash;ruler:true;">
27
32
nvmmctl identify
@@ -34,6 +39,11 @@ <h2><a name="knowit">CBSD and QEMU</a></h2>
34
39
<p>Also, acceleration will not be available if you are running non-native architectures.</p>
35
40
</div>
36
41
42
+
<p>You need to install QEMU package named 'qemu' (or 'qemu-devel' in some cases):</p>
43
+
<preclass="brush:bash;ruler:true;">
44
+
pkg install qemu
45
+
</pre>
46
+
37
47
<p>Detailed description of working with NVMM/QEMU on the: <atarget="_blank" href="https://www.dragonflybsd.org/docs/docs/howtos/nvmm/">DragonflyBSD project page</a>, <atarget="_blank" href="https://www.netbsd.org/docs/guide/en/chap-virt.html">NetBSD project guide</a></p>
38
48
39
49
<p>When working with emulation of non-native architectures, you may need firmware and bios to boot systems:</p>
<p><em>If you want to experiment with the next version of <strong>CBSD</strong>, use <strong>git clone https://github.com/cbsd/cbsd.git</strong> for <strong>/usr/local/cbsd</strong></em></p>
<li>pass users /usr/obj via nullfs on DFLY platform;</li>
147
+
<li>jails: support for single file mount via nullfs ( <atarget="_blank" href="https://reviews.freebsd.org/D37478">https://reviews.freebsd.org/D37478</a> );</li>
148
+
<li>bugfix for zfs-migrator script;</li>
149
+
<li>fix permission on ~cbsd/.ssh/sockets directory;</li>
0 commit comments