Overview

Project website docs.freebsd.org/en
Translation license BSD 2-Clause "Simplified" License
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Only chosen users can contribute.
  • The translation uses bilingual files.
File mask documentation/content/*/books/handbook/virtualization/_index.po
Translation file Download documentation/content/fr_FR/books/handbook/virtualization/_index.po
Last change None
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 710 12,648 89,886
Translated 0% 0 0% 0 0% 0
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 100% 710 100% 12,648 100% 89,886
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 242 changes 3 changes 3 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 4 changes 205 changes 0 changes 0 changes 0 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

12,648
Hosted words
710
Hosted strings
0%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

−1%
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
—
+100%
Contributors
—
User avatar None

New strings to translate

Documentation / books/handbook/virtualization/_index — French (fr_FR)

32 new strings to translate appeared to the translation. 13 days ago
User avatar None

Resource update

Documentation / books/handbook/virtualization/_index — French (fr_FR)

The "documentation/content/fr_FR/books/handbook/virtualization/_index.po" file was changed. 13 days ago
User avatar None

String updated in the repository

Documentation / books/handbook/virtualization/_index — French (fr_FR)

If the verbose output does not help diagnose the issue, there are also QEMU and Xen(TM) toolstack logs in [.filename]#/var/log/xen#. Note that the name of the domain is appended to the log name, so if the domain is named `freebsd` find a [.filename]#/var/log/xen/xl-freebsd.log# and likely a [.filename]#/var/log/xen/qemu-dm-freebsd.log#. Both log files can contain useful information for debugging. If none of this helps solve the issue, please send the description of the issue and as much information as possible to mailto:freebsd-xen@FreeBSD.org[freebsd-xen@FreeBSD.org] and mailto:xen-devel@lists.xenproject.org[xen-devel@lists.xenproject.org] to get help.
 
13 days ago
User avatar None

String updated in the repository

Documentation / books/handbook/virtualization/_index — French (fr_FR)

In order to troubleshoot host boot issues, a serial cable or a debug USB cable is needed. Verbose Xen(TM) boot output can be obtained by adding options to the `xen_cmdline` option found in [.filename]#loader.conf#. A couple of relevant debug options are:
 
13 days ago
User avatar None

String updated in the repository

Documentation / books/handbook/virtualization/_index — French (fr_FR)

Please note that the following troubleshooting tips are intended for Xen(TM) 4.11 or newer. When still using Xen(TM) 4.7 and having issues, consider migrating to a newer version of Xen(TM).
 
13 days ago
User avatar None

String updated in the repository

Documentation / books/handbook/virtualization/_index — French (fr_FR)

Modifying the IP address configuration of a system may terminate the current remote connection (e.g., via SSH), causing a lock out. Take precautions to maintain system access or make those modifications while logged in on a local terminal session.
 
13 days ago
User avatar None

String updated in the repository

Documentation / books/handbook/virtualization/_index — French (fr_FR)

For a host with an _igb0_ interface connected to the network with IP `10.10.10.1` and netmask `255.255.255.0`, use the following commands:
 
13 days ago
User avatar None

String updated in the repository

Documentation / books/handbook/virtualization/_index — French (fr_FR)

To connect the virtual machine's [.filename]#tap# device to the network via a [.filename]#bridge#, persisting the device settings in [.filename]#/etc/rc.conf# is needed. Additionally, load the necessary kernel modules `vmm` for bhyve and `nmdm` for [.filename]#nmdm# devices through the `kld_list` configuration variable. When configuring `ifconfig_bridge0`, make sure to replace `<ipaddr>/<netmask>` with the actual IP address of the physical interface ([.filename]#igb0# in this example) and remove IP settings from the physical device.
 
13 days ago
User avatar None

String updated in the repository

Documentation / books/handbook/virtualization/_index — French (fr_FR)

When using [.filename]#tap# interfaces as network backend, either manually set each used [.filename]#tap# interface to UP or simply set the following sysctl:
 
13 days ago
User avatar None

String updated in the repository

Documentation / books/handbook/virtualization/_index — French (fr_FR)

The number in the [.filename]#nmdm# device path must be unique for each virtual machine and must not be used by any other processes before bhyve starts. The number can be chosen arbitrarily and does not need to be taken from a consecutive sequence of numbers. The device node pair (i.e. [.filename]#/dev/nmdm0a# and [.filename]#/dev/nmdm0b#) are created dynamically when bhyve connects its console and destroyed when it shuts down. Keep this in mind when creating scripts to start the virtual machines: make sure that all virtual machines are assigned unique [.filename]#nmdm# devices.
 
13 days ago
Browse all translation changes