Ubuntu Manpage: virt-builder — засіб швидкої побудови образів для віртуальної машини

Provided by: libguestfs-tools_1.36.13-1ubuntu3.3_amd64

НАЗВА

       virt-builder — засіб швидкої побудови образів для віртуальної машини

КОРОТКИЙ ОПИС

        virt-builder ОС-версія
           [-o|--output ОБРАЗ ДИСКА] [--size РОЗМІР] [--format raw|qcow2]
           [--arch АРХІТЕКТУРА] [--attach ФАЙЛ ISO]

        virt-builder -l|--list [--long] [--list-format short|long|json]

        virt-builder --notes версія-ОС

        virt-builder --print-cache

        virt-builder --cache-all-templates

        virt-builder --delete-cache

        virt-builder --get-kernel ОБРАЗДИСКА
           [--format raw|qcow2] [--output КАТАЛОГВИВЕДЕННЯ]

ОПИС

       Virt-builder is a tool for quickly building new virtual machines.  You can build a variety
       of VMs for local or cloud use, usually within a few minutes or less.  Virt-builder also
       has many ways to customize these VMs.  Everything is run from the command line and nothing
       requires root privileges, so automation and scripting is simple.

       Note that virt-builder does not install guests from scratch.  It takes cleanly prepared,
       digitally signed OS templates and customizes them.  This approach is used because it is
       much faster, but if you need to do fresh installs you may want to look at virt-install(1)
       and oz-install(1).

       Найпростіше буде розпочати з прикладів з наступного розділу.

ПРИКЛАДИ

Показ списку доступних віртуальних машин
virt-builder --list

will list out the operating systems available to install. A selection of freely
redistributable OSes is available as standard. You can add your own too (see below).

Після вибору гостьової системи зі списку може виникнути потреба у ознайомленні із
нотатками щодо встановлення:

virt-builder --notes fedora-25

Побудова віртуальної машини
virt-builder fedora-25

will build a Fedora 25 image for the same architecture as virt-builder (so running it from
an i686 installation will try to build an i686 image, if available). This will have all
default configuration (minimal size, no user accounts, random root password, only the bare
minimum installed software, etc.).

Потреби у запуску цієї програми від імені root немає.

Першого разу доведеться отримати шаблон мережею, а наступні операції може бути кешовано
(див. "КЕШУВАННЯ").

The name of the output file is derived from the template name, so above it will be
fedora-25.img. You can change the output filename using the -o option:

virt-builder fedora-25 -o mydisk.img

Ви також можете скористатися параметром -o для запису на наявні пристрої або логічні томи.

virt-builder fedora-25 --format qcow2

As above, but write the output in qcow2 format to fedora-25.qcow2.

virt-builder fedora-25 --size 20G

As above, but the output size will be 20 GB. The guest OS is resized as it is copied to
the output (automatically, using virt-resize(1)).

virt-builder fedora-25 --arch i686

As above, but using an i686 template, if available.

Встановлення пароля root
virt-builder fedora-25 --root-password file:/tmp/rootpw

Create a Fedora 25 image. The root password is taken from the file /tmp/rootpw.

Note if you don't set --root-password then the guest is given a random root password which
is printed on stdout.

Крім того, ви можете створювати облікові записи користувачів. Див. "КОРИСТУВАЧІ І ПАРОЛІ"
нижче.

Встановити назву вузла
virt-builder fedora-25 --hostname virt.example.com

Встановити назву вузла "virt.example.com".

Встановлення програмного забезпечення
To install packages from the ordinary (guest) software repository (eg. dnf or apt):

virt-builder fedora-25 --install "inkscape,@Xfce Desktop"

(У Fedora "@" використовується для встановлення груп пакунків. У Debian вам доведеться
встановлювати відповідний метапакунок.)

To update the installed packages to the latest version:

virt-builder debian-7 --update

For guests which use SELinux, like Fedora and Red Hat Enterprise Linux, you may need to do
SELinux relabelling after installing or updating packages (see "SELINUX" below):

virt-builder fedora-25 --update --selinux-relabel

Налаштовування встановленої системи
There are many options that let you customize the installation. These include:
--run/--run-command, which run a shell script or command while the disk image is being
generated and lets you add or edit files that go into the disk image.
--firstboot/--firstboot-command, which let you add scripts/commands that are run the first
time the guest boots. --edit to edit files. --upload to upload files.

Приклад:

cat <<'EOF' > /tmp/dnf-update.sh
dnf -y --best update
EOF

virt-builder fedora-25 --firstboot /tmp/dnf-update.sh

або просто:

virt-builder fedora-25 --firstboot-command 'dnf -y --best update'

which makes the dnf(8) "update" command run once the first time the guest boots.

або

virt-builder fedora-25 \
--edit '/etc/dnf/dnf.conf:
s/gpgcheck=1/gpgcheck=0/'

which edits /etc/dnf/dnf.conf inside the disk image (during disk image creation, long
before boot).

Ви можете поєднувати ці параметри і додавати декілька параметрів усіх типів.

ПАРАМЕТРИ

--help
Показати довідкове повідомлення.

--arch АРХІТЕКТУРА
Use the specified architecture for the output image. This means there must be sources
providing the requested template for the requested architecture.

Див. також "АРХІТЕКТУРА".

--attach ФАЙЛ_ISO
During the customization phase, the given disk is attached to the libguestfs
appliance. This is used to provide extra software repositories or other data for
customization.

You probably want to ensure the volume(s) or filesystems in the attached disks are
labelled (or use an ISO volume name) so that you can mount them by label in your run-
scripts:

mkdir /tmp/mount
mount LABEL=EXTRA /tmp/mount

You can have multiple --attach options, and the format can be any disk format (not
just an ISO).

Див. також --run, "Встановлення пакунків зі стороннього сховища під час збирання",
genisoimage(1), virt-make-fs(1).

--attach-format ФОРМАТ
Specify the disk format for the next --attach option. The "FORMAT" is usually "raw"
or "qcow2". Use "raw" for ISOs.

--cache КАТАЛОГ
--no-cache
--cache DIR sets the directory to use/check for cached template files. If not set,
defaults to either $XDG_CACHE_HOME/virt-builder/ or $HOME/.cache/virt-builder/.

--no-cache вимикає кешування шаблонів.

--cache-all-templates
Отримати усі шаблони до кешу і завершити роботу. Див. "КЕШУВАННЯ".

Note this doesn't cache everything. More templates might be uploaded. Also this
doesn't cache packages (the --install, --update options).

--check-signature
--no-check-signature
Check/don't check the digital signature of the OS template. The default is to check
the signature and exit if it is not correct. Using --no-check-signature bypasses this
check.

Див. також --fingerprint.

--colors
--colours
Use ANSI colour sequences to colourize messages. This is the default when the output
is a tty. If the output of the program is redirected to a file, ANSI colour sequences
are disabled unless you use this option.

--curl CURL
Specify an alternate curl(1) binary. You can also use this to add curl parameters,
for example to disable https certificate checks:

virt-builder --curl "curl --insecure" [...]

--delete-cache
Вилучити кеш шаблонів. Див. "КЕШУВАННЯ".

--no-delete-on-failure
Don't delete the output file on failure to build. You can use this to debug failures
to run scripts. See "DEBUGGING BUILDS" for ways to debug images.

Типовою є поведінка, коли файл результатів буде вилучено, якщо станеться помилка у
virt-builder (або, наприклад, помилка у одному зі скриптів, які запускає ця програма).

--fingerprint 'AAAA BBBB ...'
Check that the index and templates are signed by the key with the given fingerprint.
(The fingerprint is a long string, usually written as 10 groups of 4 hexadecimal
digits).

You can give this option multiple times. If you have multiple source URLs, then you
can have either no fingerprint, one fingerprint or multiple fingerprints. If you have
multiple, then each must correspond 1-1 with a source URL.

--format qcow2
--format raw
Для звичайних процедур збирання визначає формат виведення даних. Типовим значенням є
raw.

З --get-kernel визначає формат вхідних даних.

To create an old-style qcow2 file (for compatibility with RHEL 6 or very old qemu <
1.1), after running virt-builder, use this command:

qemu-img amend -f qcow2 -o compat=0.10 output.qcow2

--get-kernel ОБРАЗ
This option extracts the kernel and initramfs from a previously built disk image
called "IMAGE" (in fact it works for any VM disk image, not just ones built using
virt-builder).

Note this method is deprecated: there is a separate tool for this, virt-get-kernel(1),
which has more options for the file extraction.

The kernel and initramfs are written to the current directory, unless you also specify
the --output "outputdir" directory name.

Формат образу диска буде визначено автоматично, якщо ви не вкажете його за допомогою
параметра --format.

In the case where the guest contains multiple kernels, the one with the highest
version number is chosen. To extract arbitrary kernels from the disk image, see
guestfish(1). To extract the entire /boot directory of a guest, see virt-copy-out(1).

--gpg GPG
Specify an alternate gpg(1) (GNU Privacy Guard) binary. By default virt-builder looks
for either "gpg2" or "gpg" in the $PATH.

You can also use this to add gpg parameters, for example to specify an alternate home
directory:

virt-builder --gpg "gpg --homedir /tmp" [...]

-l [версія-ОС]
--list [версія-ОС]
--list --list-format формат [версія ОС]
--list --long [версія ОС]
Вивести усі доступні шаблони, якщо не вказано гостьової системи, або вивести шаблони
лише для вказаної гостьової системи.

Ви можете вибрати формат виведення за допомогою параметра --list-format для шаблонів
списку:

short
Типовий формат: виводиться лише ідентифікатор шаблона і, поряд з ним, його
короткий опис.

long
Виводить тестовий список із даними щодо доступних джерел і список даних щодо
доступних шаблонів після нього.

json
Вивести об’єкт JSON із подробицями щодо доступних джерел та подробиці щодо
доступних шаблонів.

The "version" key in the main object represents the "compatibility version", and
it is bumped every time the resulting JSON output is incompatible with the
previous versions (for example the structure has changed, or non-optional keys are
no more present).

--long — скорочення для формату "long".

Див також: --source, --notes, "ДЖЕРЕЛА ШАБЛОНІВ".

--machine-readable
This option is used to make the output more machine friendly when being parsed by
other programs. See "MACHINE READABLE OUTPUT" below.

-m МБ
--memsize МБ
Change the amount of memory allocated to --run scripts. Increase this if you find
that --run scripts or the --install option are running out of memory.

Типові значення можна визначити за допомогою такої команди:

guestfish get-memsize

--network
--no-network
Увімкнути чи вимкнути доступ до мережі для гостьової системи під час встановлення.

Типово увімкнено. Скористайтеся параметром --no-network, щоб вимкнути доступ.

The network only allows outgoing connections and has other minor limitations. See
"NETWORK" in virt-rescue(1).

If you use --no-network then certain other options such as --install will not work.

This does not affect whether the guest can access the network once it has been booted,
because that is controlled by your hypervisor or cloud environment and has nothing to
do with virt-builder.

Загалом кажучи, вам не варто використовувати --no-network. Але ось декілька випадків,
коли у вас може виникнути потреба у використанні цього параметра:

1. У модулі обробки libguestfs, яким ви користуєтеся, не передбачено підтримки
мережі. (Див. "BACKEND" in guestfs(3)).

2. Усе програмне забезпечення, яке ви маєте намір встановити, походить з долученого
образу ISO, отже потреби у мережі немає.

3. You don't want untrusted guest code trying to access your host network when
running virt-builder. This is particularly an issue when you don't trust the
source of the operating system templates. (See "SECURITY" below).

4. Ви не хочете користуватися мережею основної системи (наприклад, через захищеність
або обмеженість середовища у ній).

--no-sync
Не синхронізувати файл виведення під час завершення роботи.

Virt-builder виконує синхронізацію fsync файла результатів або образу диска, якщо
такий існує.

The reason is that qemu/KVM's default caching mode is "none" or "directsync", both of
which bypass the host page cache. Therefore these would not work correctly if you
immediately started the guest after running virt-builder - they would not see the
complete output file. (Note that you should not use these caching modes - they are
fundamentally broken for this and other reasons.)

If you are not using these broken caching modes, you can use --no-sync to avoid this
unnecessary sync and gain considerable extra performance.

--notes версія-ОС
Показує список нотаток, пов’язаних із гостьовою системою, потім завершує роботу
(встановлення не виконується).

-o назва_файла
--output назва_файла
Write the output to filename. If you don't specify this option, then the output
filename is generated by taking the "os-version" string and adding ".img" (for raw
format) or ".qcow2" (for qcow2 format).

Зауважте, що назвою файла виведення результатів може бути пристрій, розділ або
логічний том.

Якщо використовується з --get-kernel, цей параметр задає каталог виведення даних.

--print-cache
Вивести інформацію щодо кешу шаблонів. Див. "КЕШУВАННЯ".

-q
--quiet
Не виводити звичайних повідомлень щодо поступу.

--size РОЗМІР
Select the size of the output disk, where the size can be specified using common names
such as "32G" (32 gigabytes) etc.

Virt-builder змінить розміри файлових систем у образі диска автоматично.

If the size is not specified, then one of two things happens. If the output is a
file, then the size is the same as the template. If the output is a device,
partition, etc then the size of that device is used.

To specify size in bytes, the number must be followed by the lowercase letter b, eg:
"--size 10737418240b".

--smp N
Enable N ≥ 2 virtual CPUs for --run scripts to use.

--source АДРЕСА
Set the source URL to look for indexes.

You can give this option multiple times to specify multiple sources.

Див. також "ДЖЕРЕЛА ШАБЛОНІВ" нижче.

Note that you should not point --source to sources that you don't trust (unless the
source is signed by someone you do trust). See also the --no-network option.

--no-warn-if-partition
Do not emit a warning if the output device is a partition. This warning avoids a
common user error when writing to a USB key or external drive, when you should
normally write to the whole device (--output /dev/sdX), not to a partition on the
device (--output /dev/sdX1). Use this option to suppress this warning.

-v
--verbose
Enable debug messages and/or produce verbose output.

When reporting bugs, use this option and attach the complete output to your bug
report.

-V
--version
Показати дані щодо версії і завершити роботу.

-x Увімкнути трасування викликів програмного інтерфейсу libguestfs.

Параметри налаштовування
--append-line FILE:LINE
Append a single line of text to the "FILE". If the file does not already end with a
newline, then one is added before the appended line. Also a newline is added to the
end of the "LINE" string automatically.

For example (assuming ordinary shell quoting) this command:

--append-line '/etc/hosts:10.0.0.1 foo'

will add either "10.0.0.1 foo⏎" or "⏎10.0.0.1 foo⏎" to the file, the latter only if
the existing file does not already end with a newline.

"⏎" represents a newline character, which is guessed by looking at the existing
content of the file, so this command does the right thing for files using Unix or
Windows line endings. It also works for empty or non-existent files.

To insert several lines, use the same option several times:

--append-line '/etc/hosts:10.0.0.1 foo'
--append-line '/etc/hosts:10.0.0.2 bar'

To insert a blank line before the appended line, do:

--append-line '/etc/hosts:'
--append-line '/etc/hosts:10.0.0.1 foo'

--chmod ПРАВА_ДОСТУПУ:ФАЙЛ
Змінити права доступу до файла "ФАЙЛ" на "ПРАВА_ДОСТУПУ".

Зауваження: типово "ПРАВА_ДОСТУПУ" записуються у десятковому форматі, якщо ви не
додасте початковий 0 , щоб вказати вісімкове число, тобто скористаєтеся 0700, а не
700.

--commands-from-file НАЗВА_ФАЙЛА
Прочитати команди налаштовування з файла, по одній (разом із аргументами) на рядок.

Кожен рядок містить команду налаштовування та її аргументи, наприклад:

delete /якийсь/файл
install якийсь_пакунок
password якийсь-користувач:password:його-новий-пароль

Empty lines are ignored, and lines starting with "#" are comments and are ignored as
well. Furthermore, arguments can be spread across multiple lines, by adding a "\"
(continuation character) at the of a line, for example

edit /якийсь/файл:\
s/^OPT=.*/OPT=ok/

The commands are handled in the same order as they are in the file, as if they were
specified as --delete /some/file on the command line.

--copy ДЖЕРЕЛО:ПРИЗНАЧЕННЯ
Копіювати файли або каталоги рекурсивно у межах гостьової системи.

Не можна використовувати символи-замінники.

--copy-in ЛОКАЛЬНИЙ_ШЛЯХ:ВІДДАЛЕНИЙ_КАТАЛОГ
Copy local files or directories recursively into the disk image, placing them in the
directory "REMOTEDIR" (which must exist).

Не можна використовувати символи-замінники.

--delete ШЛЯХ
Вилучити файл з гостьової системи. Або вилучити каталог (і увесь його вміст,
рекурсивно).

You can use shell glob characters in the specified path. Be careful to escape glob
characters from the host shell, if that is required. For example:

virt-customize --delete '/var/log/*.log'.

Див. також --upload, --scrub.

--edit ФАЙЛ:ВИРАЗ
Edit "FILE" using the Perl expression "EXPR".

Be careful to properly quote the expression to prevent it from being altered by the
shell.

Note that this option is only available when Perl 5 is installed.

Див. "NON-INTERACTIVE EDITING" in virt-edit(1).

--firstboot СКРИПТ
Install "SCRIPT" inside the guest, so that when the guest first boots up, the script
runs (as root, late in the boot process).

The script is automatically chmod +x after installation in the guest.

The alternative version --firstboot-command is the same, but it conveniently wraps the
command up in a single line script for you.

You can have multiple --firstboot options. They run in the same order that they
appear on the command line.

Please take a look at "FIRST BOOT SCRIPTS" for more information and caveats about the
first boot scripts.

Див. також --run.

--firstboot-command 'КОМАНДА+ПАРАМЕТРИ'
Run command (and arguments) inside the guest when the guest first boots up (as root,
late in the boot process).

You can have multiple --firstboot options. They run in the same order that they
appear on the command line.

Please take a look at "FIRST BOOT SCRIPTS" for more information and caveats about the
first boot scripts.

Див. також --run.

--firstboot-install ПАКУНОК,ПАКУНОК..
Install the named packages (a comma-separated list). These are installed when the
guest first boots using the guest's package manager (eg. apt, yum, etc.) and the
guest's network connection.

For an overview on the different ways to install packages, see "INSTALLING PACKAGES".

--hostname НАЗВА_ВУЗЛА
Set the hostname of the guest to "HOSTNAME". You can use a dotted hostname.domainname
(FQDN) if you want.

--install ПАКУНОК,ПАКУНОК..
Install the named packages (a comma-separated list). These are installed during the
image build using the guest's package manager (eg. apt, yum, etc.) and the host's
network connection.

For an overview on the different ways to install packages, see "INSTALLING PACKAGES".

ДОВІДНИК

ВСТАНОВЛЕННЯ ПАКУНКІВ
There are several approaches to installing packages or applications in the guest which
have different trade-offs.

Встановлення пакунків під час збирання

If the guest OS you are installing is similar to the host OS (eg. both are Linux), and if
libguestfs supports network connections, then you can use --install to install packages
like this:

virt-builder fedora-25 --install inkscape

This uses the guest's package manager and the host's network connection.

Оновлення пакунків під час збирання

To update the installed packages in the template at build time:

virt-builder fedora-25 --update

Most of the templates that ship with virt-builder come with a very minimal selection of
packages (known as a "JEOS" or "Just Enough Operating System"), which are up to date at
the time the template is created, but could be out of date by the time you come to install
an OS from the template. This option updates those template packages.

Встановлення пакунків під час першого завантаження

Another option is to install the packages when the guest first boots:

virt-builder fedora-25 --firstboot-install inkscape

This uses the guest's package manager and the guest's network connection.

The downsides are that it will take the guest a lot longer to boot first time, and there's
nothing much you can do if package installation fails (eg. if a network problem means the
guest can't reach the package repositories).

Встановлення пакунків зі стороннього сховища під час збирання

If the software you want to install is not available in the main package repository of the
guest, then you can add a side repository. Usually this is presented as an ISO (CD disk
image) file containing extra packages.

You can create the disk image using either genisoimage(1) or virt-make-fs(1). For
genisoimage, use a command like this:

genisoimage -o extra-packages.iso -R -J -V EXTRA cdcontents/

Create a script that mounts the ISO and sets up the repository. For dnf, create
/tmp/install.sh containing:

mkdir /tmp/mount
mount LABEL=EXTRA /tmp/mount

cat <<'EOF' > /etc/yum.repos.d/extra.repo
[extra]
name=extra
baseurl=file:///tmp/mount
enabled=1
EOF

dnf -y install famousdatabase

Для apt створіть файл /tmp/install.sh із таким вмістом:

mkdir /tmp/mount
mount LABEL=EXTRA /tmp/mount

apt-cdrom -d=/tmp/mount add
apt-get -y install famousdatabase

Use the --attach option to attach the CD / disk image and the --run option to run the
script:

virt-builder fedora-25 \
--attach extra-packages.iso \
--run /tmp/install.sh

КОРИСТУВАЧІ І ПАРОЛІ
The --root-password option is used to change the root password (otherwise a random
password is used). This option takes a password "SELECTOR" in one of the following
formats:

--root-password file:НАЗВА_ФАЙЛА
Read the root password from "FILENAME". The whole first line of this file is the
replacement password. Any other lines are ignored. You should create the file with
mode 0600 to ensure no one else can read it.

--root-password password:ПАРОЛЬ
Set the root password to the literal string "PASSWORD".

Note: this is not secure since any user on the same machine can see the cleartext
password using ps(1).

--root-password random
Вибрати випадковий пароль, який буде виведено до stdout. Випадковість пароля наближено
відповідатиме 120-бітовій.

Типове значення.

--root-password disabled
The root account password is disabled. This is like putting "*" in the password
field.

--root-password locked:file:НАЗВА_ФАЙЛА
--root-password locked:password:ПАРОЛЬ
--root-password locked:random
The root account is locked, but a password is placed on the account. If first
unlocked (using "passwd -u") then logins will use the given password.

--root-password locked
--root-password locked:disabled
The root account is locked and password is disabled.

Створення облікових записів користувачів

To create user accounts, use the useradd(8) command with --firstboot-command like this:

virt-builder --firstboot-command \
'useradd -m -p "" rjones ; chage -d 0 rjones'

The above command will create an "rjones" account with no password, and force the user to
set a password when they first log in. There are other ways to manage passwords, see
useradd(8) for details.

РОЗКЛАДКА КЛАВІАТУРИ
Because there are so many different ways to set the keyboard layout in Linux
distributions, virt-builder does not yet attempt to have a simple command line option.
This section describes how to set the keyboard for some common Linux distributions.

Визначення розкладки клавіатури за допомогою systemd

For distros that use systemd "localectl", use a command like this:

virt-builder fedora-25 \
--firstboot-command 'localectl set-keymap uk'

Докладніший опис можна знайти за посиланнями localectl(1) та
https://www.happyassassin.net/2013/11/23/keyboard-layouts-in-fedora-20-and-previously/.

Keyboard layout using /etc/sysconfig/keyboard

For RHEL ≤ 6, Fedora ≤ 18 and similar, upload or modify the keyboard configuration file
using the --upload, --write or --edit options. For example:

virt-builder centos-6 \
--edit '/etc/sysconfig/keyboard: s/^KEYTABLE=.*/KEYTABLE="uk"/'

The format of this file can be found documented in many places online.

Keyboard layout with Debian-derived distros

For Debian-derived distros using /etc/default/keyboard, upload or modify the keyboard file
using the --upload, --write or --edit options. For example:

virt-builder debian-8 \
--edit '/etc/default/keyboard: s/^XKBLAYOUT=.*/XKBLAYOUT="gb"/'

Див. https://wiki.debian.org/Keyboard.

МОВА
Most Linux distributions support multiple locale settings so that you can have guest
messages printed in another language such as Russian.

However there is no single setting which controls this, since extra packages may need to
be installed to support console and X fonts, and keyboard input methods. The packages
required, and their configuration is highly distro-specific, and it is outside the scope
of virt-builder to do this.

У цьому розділі наведено приклади для типових дистрибутивів Linux.

Setting Japanese in Fedora 25

virt-builder fedora-25 \
--size 20G \
--update \
--install @japanese-support \
--install @xfce \
--install xorg-x11-server-Xorg,xorg-x11-drivers,rsyslog \
--link /usr/lib/systemd/system/graphical.target:/etc/systemd/system/default.target \
--firstboot-command 'localectl set-locale LANG=ja_JP.utf8' \
--firstboot-command 'localectl set-keymap jp' \
--firstboot-command 'systemctl isolate graphical.target'

Setting Japanese in Debian 8 (Jessie)

Note that although this enables Japanese in the text console too, it is unlikely that you
will see properly rendered Japanese there. However Japanese is properly rendered in X
applications and terminals.

pkgs=locales,xfce4,\
ibus,ibus-anthy,\
fonts-ipafont-gothic,fonts-ipafont-mincho,\
fonts-takao-mincho,\
xfonts-intl-japanese,xfonts-intl-japanese-big,\
iceweasel-l10n-ja,manpages-ja

virt-builder debian-8 \
--size 20G \
--install $pkgs \
--edit '/etc/locale.gen: s,^#\s*ja,ja,' \
--write '/etc/default/locale:LANG="ja_JP.UTF-8"' \
--run-command "locale-gen"

ФАЙЛ ЖУРНАЛУ
Scripts and package installation that runs at build time (--run, --run-command, --install,
--update, but not firstboot) is logged in one of the following locations:

/tmp/builder.log
On Linux, BSD, and other non-Windows guests.

C:\Temp\builder.log
У гостьових системах Windows, DOS.

/builder.log
Якщо немає /tmp або C:\Temp.

If you don't want the log file to appear in the final image, then use the --no-logfile
command line option.

КЛЮЧІ SSH
The --ssh-inject option is used to inject ssh keys for users in the guest, so they can
login without supplying a password.

The "SELECTOR" part of the option value is optional; in this case, --ssh-inject "USER"
means that we look in the current user's ~/.ssh directory to find the default public ID
file. That key is uploaded. "default public ID" is the default_ID_file file described in
ssh-copy-id(1).

If specified, the "SELECTOR" can be in one of the following formats:

--ssh-inject КОРИСТУВАЧ:file:НАЗВА_ФАЙЛА
Прочитати ключ ssh з файла НАЗВА ФАЙЛА. Файлом зазвичай є файл .pub.

--ssh-inject USER:string:KEY_STRING
Use the specified "KEY_STRING". "KEY_STRING" is usually a public string like ssh-rsa
AAAA.... user@localhost.

In any case, the ~USER/.ssh directory and the ~USER/.ssh/authorized_keys file will be
created if not existing already.

СКРИПТИ ПЕРШОГО ЗАВАНТАЖЕННЯ
The --firstboot and --firstboot-command options allow you to execute commands at the first
boot of the guest. To do so, an init script for the guest init system is installed, which
takes care of running all the added scripts and commands.

Підтримувані операційні системи:

Linux
Init systems supported are: systemd, System-V init (known also as sysvinit), and
Upstart (using the System-V scripts).

Note that usually init scripts run as root, but with a more limited environment than
what could be available from a normal shell: for example, $HOME may be unset or empty.

The output of the first boot scripts is available in the guest as
~root/virt-sysprep-firstboot.log.

Windows
rhsrvany.exe, available from sources at https://github.com/rwmjones/rhsrvany, or
pvvxsvc.exe, available with SUSE VMDP is installed to run the first boot scripts. It
is required, and the setup of first boot scripts will fail if it is not present.

rhsrvany.exe or pvvxsvc.exe is copied from the location pointed to by the
"VIRT_TOOLS_DATA_DIR" environment variable; if not set, a compiled-in default will be
used (something like /usr/share/virt-tools).

The output of the first boot scripts is available in the guest as C:\Program
Files\Guestfs\Firstboot\log.txt.

SUBSCRIPTION-MANAGER
It is possible to automate the registration and attaching of the system using
"subscription-manager". This is typical on Red Hat Enterprise Linux guests. There are
few options which ease this process, avoid executing commands manually and exposing
passwords on command line.

--sm-register starts the registration process, and requires --sm-credentials to be
specified; the format of the "SELECTOR" of --sm-credentials is one of the following
formats:

--sm-credentials КОРИСТУВАЧ:file:НАЗВА_ФАЙЛА
Read the password for the specified "USER" from FILENAME.

--sm-credentials USER:password:PASSWORD
Use the literal string "PASSWORD" for the specified "USER".

--sm-attach attaches the system to subscriptions; the format of its "SELECTOR" is one of
the following:

--sm-attach auto
"subscription-manager" attaches to the best-fitting subscriptions for the system.

--sm-attach file:НАЗВА_ФАЙЛА
Read the pool ID from FILENAME.

--sm-attach pool:POOL
Use the literal string "POOL" as pool ID.

--sm-remove removes all the subscriptions from the guest, while --sm-unregister completely
unregister the system.

ПРОЦЕДУРА ВСТАНОВЛЕННЯ
When you invoke virt-builder, installation proceeds as follows:

• Отримано образ шаблону.

If the template image is present in the cache, the cached version is used instead.
(See "CACHING").

• Перевірено підпис шаблону.

• Шаблон розпаковано до файла tmp.

• The template image is resized into the destination, using virt-resize(1).

• Долучено додаткові диски (--attach).

• Створено нову базу псевдовипадкових чисел для гостьової системи.

• Guest customization is performed, in the order specified on the command line.

• Зміну міток SELinux виконано (--selinux-relabel).

ІМПОРТУВАННЯ ОБРАЗУ ДИСКА
Імпортування до libvirt

Import the disk image into libvirt using virt-install(1) --import option.

virt-install --import \
--name guest --ram 2048 \
--disk path=disk.img,format=raw --os-variant fedora25

Нотатки:

1. You must specify the correct format. The format is "raw" unless you used virt-
builder's --format option.

2. --os-variant is highly recommended, because it will present optimum devices to enable
the guest to run most efficiently. To get a list of all variants, do:

osinfo-query ОС

Вказана вище програма є частиною пакунка libosinfo.

3. You can run virt-install as root or non-root. Each works slightly differently because
libvirt manages a different set of virtual machines for each user. In particular
virt-manager normally shows the root-owned VMs, whereas Boxes shows the user-owned
VMs, and other tools probably work differently as well.

Імпортування до OpenStack

Import the image into Glance (the OpenStack image store) by doing:

glance image-create --name fedora-25-image --file fedora-25.img \
--disk-format raw --container-format bare \
--is-public True

The --file parameter is the virt-builder-generated disk image. It should match virt-
builder's --output option. The --disk-format parameter should match virt-builder's
--format option (or "raw" if you didn't use that option). The --container-format should
always be "bare" since virt-builder doesn't put images into containers.

You can use the "glance image-show fedora-25-image" command to display the properties of
the image.

To boot up an instance of your image on a Nova compute node, do:

nova boot fedora-25-server --image fedora-25-image \
--flavor m1.medium

Use "nova flavor-list" to list possible machine flavors. Use "nova list" to list running
instances.

Безпосереднє завантаження за допомогою qemu або KVM

The qemu command line is not very stable or easy to use, hence libvirt should be used if
possible. However a command line similar to the following could be used to boot the
virtual machine:

qemu-system-x86_64 \
-machine accel=kvm:tcg \
-cpu host \
-m 2048 \
-drive file=disk.img,format=raw,if=virtio

As with libvirt, it is very important that the correct format is chosen. It will be "raw"
unless the --format option was used.

КЕРУВАННЯ НАЛАШТУВАННЯМИ
Puppet

To enable the Puppet agent in a guest, install the package, point the configuration at
your Puppetmaster, and ensure the agent runs at boot.

A typical virt-builder command would be:

virt-builder fedora-25 \
--hostname client.example.com \
--update \
--install puppet \
--append-line '/etc/puppet/puppet.conf:[agent]' \
--append-line '/etc/puppet/puppet.conf:server = puppetmaster.example.com/' \
--run-command 'systemctl enable puppet' \
--selinux-relabel

The precise instructions vary according to the Linux distro. For further information see:
https://docs.puppet.com/puppet/latest/install_pre.html

ДІАГНОСТИКА ЗБИРАННЯ
If virt-builder itself fails, then enable debugging (-v) and report a bug (see "BUGS"
below).

If virt-builder fails because some script or package it is installing fails, try using
--no-delete-on-failure to preserve the output file, and continue reading this section.

If virt-builder is successful but the image doesn't work, here are some things to try:

Використання virt-rescue
Запустити virt-rescue(1) над образом диска:

virt-rescue -a disk.img

This gives you a rescue shell. You can mount the filesystems from the disk image on
/sysroot and examine them using ordinary Linux commands. You can also chroot into the
guest to reinstall the bootloader. The virt-rescue man page has a lot more
information and examples.

Використання guestfish
Запустити guestfish(1) над образом диска:

guestfish -a disk.img -i

Use guestfish commands like "ll /directory" and "cat /file" to examine directories and
files.

Використання guestmount
Безпечно змонтувати образ диска у основній системі за допомогою FUSE і guestmount(1):

mkdir /tmp/mp
guestmount -a disk.img -i /tmp/mp
cd /tmp/mp

Щоб демонтувати образ диска, виконайте такі дії:

fusermount -u /tmp/mp

Додати послідовну консоль
If the guest hangs during boot, it can be helpful to add a serial console to the
guest, and direct kernel messages to the serial console. Adding the serial console
will involve looking at the documentation for your hypervisor. To direct kernel
messages to the serial console, add the following on the kernel command line:

console=tty0 console=ttyS0,115200

ДЖЕРЕЛА ШАБЛОНІВ
virt-builder reads the available sources from configuration files, with the .conf
extension and located in the following paths:

• $XDG_CONFIG_HOME/virt-builder/reposd/ ($XDG_CONFIG_HOME дорівнює $HOME/.config, якщо
не встановлено).

• $XDG_CONFIG_DIRS/virt-builder/repos.d/ (where $XDG_CONFIG_DIRS means any of the
directories in that environment variable, or just /etc/xdg if not set)

Each .conf file in those paths has a simple text format like the following:

[libguestfs.org]
uri=http://libguestfs.org/download/builder/index.asc
gpgkey=file:///etc/xdg/virt-builder/repos.d/libguestfs.gpg

Частина у квадратних дужках є ідентифікатором сховища, який використовується як унікальний
ідентифікатор.

Можуть з’явитися такі поля:

"uri=АДРЕСА"
Адреса файла покажчика, на який посилається це сховище.

Це поле слід заповнити.

"gpgkey=АДРЕСА"
This optional field represents the URI (although only file:// URIs are accepted) of
the key used to sign the index file. If not present, the index file referred by
uri=.. is not signed.

"proxy=РЕЖИМ"
This optional field specifies the proxy mode, to be used when downloading the index
file of this repository. The possible values are:

no, off
No proxy is being used at all, even overriding the system configuration.

system
Використаний проксі-сервер є системним.

усе інше
Specifies the actual proxy configuration to be used, overriding the system
configuration.

If not present, the assumed value is to respect the proxy settings of the system (i.e.
as if system would be specified).

"format=ФОРМАТ"
This optional field specifies the format of the repository. The possible values are:

native
The native format of the "virt-builder" repository. See also "Creating and
signing the index file" below.

simplestreams
The URI represents the root of a Simple Streams v1.0 tree of metadata.

For more information about Simple Streams, see also
https://launchpad.net/simplestreams.

If not present, the assumed value is "native".

For serious virt-builder use, you may want to create your own repository of templates.

Сховище libguestfs.org

Out of the box, virt-builder downloads the file
http://libguestfs.org/download/builder/index.asc which is an index of available templates
plus some information about each one, wrapped up in a digital signature. The command
"virt-builder --list" lists out the information in this index file.

The templates hosted on libguestfs.org were created using shell scripts, kickstart files
and preseed files which can be found in the libguestfs source tree, in
"builder/templates".

Налаштовування доступу до сховища

You can set up your own site containing an index file and some templates, and then point
virt-builder at the site by creating a .conf file pointing to it.

Note that if your index is signed, you will need to properly fill gpgkey=.. in your .conf
file, making sure to deploy also the GPG key file.

virt-builder --source https://example.com/builder/index.asc \
--fingerprint 'AAAA BBBB ...' \
--list

You can host this on any web or FTP server, or a local or network filesystem.

Встановлення ключа GPG

If you don't have a GnuPG key, you will need to set one up. (Strictly speaking this is
optional, but if your index and template files are not signed then virt-builder users will
have to use the --no-check-signature flag every time they use virt-builder.)

Інструкцію зі створення ключа можна знайти у підручнику з GPG:
http://www.gnupg.org/gph/en/manual.html.

Експортувати ваш відкрити ключ GPG:

gpg --export -a "you@example.com" > pubkey

Створення шаблонів

There are many ways to create the templates. For example you could clone existing guests
(see virt-sysprep(1)), or you could install a guest by hand (virt-install(1)). To see how
the templates were created for virt-builder, look at the scripts in "builder/templates"

Virt-builder supports any image format (e.g. raw, qcow2, etc) as template, both as-is, and
compressed as XZ. This way, existing images (e.g. cleaned using virt-sysprep(1)) can be
used as templates.

For best results when compressing the templates, use the following xz options (see
nbdkit-xz-plugin(1) for further explanation):

xz --best --block-size=16777216 disk

Створення і підписування файла покажчика

The index file has a simple text format (shown here without the digital signature):

[fedora-18]
name=Fedora® 18
osinfo=fedora18
arch=x86_64
file=fedora-18.xz
checksum[sha512]=...
format=raw
size=6442450944
compressed_size=148947524
expand=/dev/sda3

[fedora-19]
name=Fedora® 19
osinfo=fedora19
arch=x86_64
file=fedora-19.xz
checksum[sha512]=...
revision=3
format=raw
size=4294967296
compressed_size=172190964
expand=/dev/sda3

The part in square brackets is the "os-version", which is the same string that is used on
the virt-builder command line to build that OS.

After preparing the "index" file in the correct format, clearsign it using the following
command:

gpg --clearsign --armor index

This will create the final file called index.asc which can be uploaded to the server (and
is the uri=.. URL). As noted above, signing the index file is optional, but recommended.

Можуть з’явитися такі поля:

"name=НАЗВА"
The user-friendly name of this template. This is displayed in the --list output but
is otherwise not significant.

"osinfo=ІДЕНТИФІКАТОР"
This optional field maps the operating system to the associated libosinfo ID. Virt-
builder does not use it (yet).

"arch=АРХІТЕКТУРА"
The architecture of the operating system installed within the template. This field is
required.

"file=ШЛЯХ"
Шлях (відносно покажчика) стисненого xz шаблона.

Note that absolute paths or URIs are not permitted here. This is because virt-builder
has a "same origin" policy for templates so they cannot come from other servers.

"sig=ШЛЯХ"
This option is deprecated. Use the checksum field instead.

The path (relative to the index) of the GPG detached signature of the xz file.

Note that absolute paths or URIs are not permitted here. This is because virt-builder
has a "same origin" policy for templates so they cannot come from other servers.

Файл можна створити такою командою:

gpg --detach-sign --armor -o disk.xz.sig disk.xz

"checksum[sha512]=7b882fe9b82eb0fef..."
The SHA-512 checksum of the file specified in file=.. is checked after it is
downloaded. To work out the signature, do:

sha512sum disk.xz

Note if you use this, you don't need to sign the file, ie. don't use "sig". This
option overrides "sig".

"checksum=7b882fe9b82eb0fef..."
"checksum" is an alias for "checksum[sha512]".

If you need to interoperate with virt-builder = 1.24.0 then you have to use "checksum"
because that version would give a parse error with square brackets and numbers in the
key of a field. This is fixed in virt-builder ≥ 1.24.1.

"revision=N"
The revision is an integer which is used to control the template cache. Increasing
the revision number causes clients to download the template again even if they have a
copy in the cache.

Номер модифікації є необов’язковим. Якщо його не вказано, типовим значенням вважається
1.

"format=raw"
"format=qcow2"
Specify the format of the disk image; in case it is compressed, that is the format
before the compression. If not given, the format is autodetected, but generally it is
better to be explicit about the intended format.

Note this is the source format, which is different from the --format option (requested
output format). Virt-builder does on-the-fly conversion from the source format to the
requested output format.

"size=NNN"
The virtual size of the image in bytes. This is the size of the image when
uncompressed. If using a non-raw format such as qcow2 then it means the virtual disk
size, not the size of the qcow2 file.

Це поле слід заповнити.

Virt-builder also uses this as the minimum size that users can request via the --size
option, or as the default size if there is no --size option.

"compressed_size=NNN"
The actual size of the disk image in bytes, i.e. what was specified in file=... This
is just used for information (when using "long", and "json" formats of --list).

"expand=/dev/sdaX"
When expanding the image to its final size, instruct virt-resize(1) to expand the
named partition in the guest image to fill up all available space. This works like
the virt-resize --expand option.

You should usually put the device name of the guest's root filesystem here.

It's a good idea to use this, but not required. If the field is omitted then virt-
resize will create an extra partition at the end of the disk to cover the free space,
which is much less user-friendly.

"lvexpand=/пристрій/група_томів/логічний_том"
When expanding the image to its final size, instruct virt-resize(1) to expand the
named logical volume in the guest image to fill up all available space. This works
like the virt-resize --lv-expand option.

If the guest uses LVM2 you should usually put the LV of the guest's root filesystem
here. If the guest does not use LVM2 or its root filesystem is not on an LV, don't
use this option.

"notes=НОТАТКИ"
Any notes that go with this image, especially notes describing what packages are in
the image, how the image was prepared, and licensing information.

Ці дані буде виведено у режимах --notes і --list --long.

You can use multi-line notes here by indenting each new line with at least one
character of whitespace (even on blank lines):

notes=This image was prepared using
the following kickstart script:
<-- one space at beginning of line
part /boot --fstype ext3
...

"hidden=true"
Using the hidden flag prevents the template from being listed by the --list option
(but it is still installable). This is used for test images.

"aliases=ПСЕВДОНІМ1 ПСЕВДОНІМ2 ..."
This optional field specifies a list of aliases, separated by spaces, for the image.
For example, an alias could be used to always point to the latest version of a certain
image, leaving the old versions available in the index instead of updating the same
image (see the "revision" field).

Запуск virt-builder для декількох джерел одночасно

It is possible to use multiple sources with virt-builder. The recommended way is to
deploy .conf files pointing to the index files. Another way is to specify the sources
using multiple --source and/or --fingerprint options:

virt-builder \
--source http://example.com/s1/index.asc \
--source http://example.com/s2/index.asc

You can provide N or 1 fingerprints. In the case where you provide N fingerprints, N =
number of sources and there is a 1-1 correspondence between each source and each
fingerprint:

virt-builder \
--source http://example.com/s1/index.asc --fingerprint '0123 ...' \
--source http://example.com/s2/index.asc --fingerprint '9876 ...'

In the case where you provide 1 fingerprint, the same fingerprint is used for all sources.

Вам "слід" надати принаймні 1 відбиток.

Ліцензування шаблонів

You should be aware of the licensing of images that you distribute. For open source
guests, provide a link to the source code in the "notes" field and comply with other
requirements (eg. around trademarks).

Формальна специфікація файла покажчика

The index file format has a formal specification defined by the flex scanner and bison
parser used to parse the file. This can be found in the following files in the libguestfs
source tree:

builder/index-scan.l
builder/index-parse.y

A tool called virt-index-validate(1) is available to validate the index file to ensure it
is correct.

Note that the parser and tool can work on either the signed or unsigned index file (ie.
index or index.asc).

Кодуванням покажчика завжди є UTF-8.

КЕШУВАННЯ
Кешування шаблонів

Since the templates are usually very large, downloaded templates are cached in the user's
home directory.

The location of the cache is $XDG_CACHE_HOME/virt-builder/ or $HOME/.cache/virt-builder.

You can print out information about the cache directory, including which guests are
currently cached, by doing:

virt-builder --print-cache

Кеш можна вилучити з метою економії місця на диску такою командою:

virt-builder --delete-cache

Ви можете отримати усі (поточні) шаблони до локального кешу командою:

virt-builder --cache-all-templates

Щоб вимкнути кешування шаблонів, скористайтеся параметром --no-cache.

Кешуванню підлягають лише шаблони. Для покажчика та цифрових підписів кешування не
використовується.

Кешування пакунків

Virt-builder uses curl(1) to download files and it also uses the current "http_proxy"
(etc) settings when installing packages (--install, --update).

You may therefore want to set those environment variables in order to maximize the amount
of local caching that happens. See "ENVIRONMENT VARIABLES" and curl(1).

Локальні дзеркала

To increase both speed and reliability of installing packages, you can set up a local
mirror of the target distribution, and point the guest package manager at that.

Використання локального дзеркала з Fedora

Для встановлення гостьової системи Fedora за допомогою локального дзеркала:

virt-builder fedora-25 \
--edit '/etc/yum.repos.d/fedora.repo:
s{.*baseurl=.*}{baseurl=http://example.com/mirror/};
s{.*metalink=.*}{};
' \
--edit '/etc/yum.repos.d/fedora-updates.repo:
s{.*baseurl=.*}{baseurl=http://example.com/mirror-updates/};
s{.*metalink=.*}{};
' \
--run-command 'dnf -y update' \
--install 'pkg1,pkg2,...'

Використання локального дзеркала з Debian

Assuming that you are using "apt-proxy" to mirror the repository, you should create a new
sources.list file to point to your proxy (see https://help.ubuntu.com/community/AptProxy)
and then do:

virt-builder debian-8 \
--upload sources.list:/etc/apt/sources.list \
--run-command 'apt-get -y update' \
--install 'pkg1,pkg2,...'

ЦИФРОВІ ПІДПИСИ
Virt-builder uses GNU Privacy Guard (GnuPG or gpg) to verify that the index and templates
have not been tampered with.

The source points to an index file, which is optionally signed.

Virt-builder downloads the index and checks that the signature is valid and the signer's
fingerprint matches the specified fingerprint (ie. the one specified in gpgkey=.. in the
.conf, or with --fingerprint, in that order).

For checking against the built-in public key/fingerprint, this requires importing the
public key into the user's local gpg keyring (that's just the way that gpg works).

When a template is downloaded, its signature is checked in the same way.

Although the signatures are optional, if you don't have them then virt-builder users will
have to use --no-check-signature on the command line. This prevents an attacker from
replacing the signed index file with an unsigned index file and having virt-builder
silently work without checking the signature. In any case it is highly recommended that
you always create signed index and templates.

АРХІТЕКТУРА
Virt-builder can build a guest for any architecture no matter what the host architecture
is. For example an x86-64 guest on an ARM host.

However certain options may not work, specifically options that require running commands
in the guest during the build process: --install, --update, --run, --run-command. You may
need to replace these with their firstboot-equivalents.

An x86-64 host building 32 bit i686 guests should work without any special steps.

БЕЗПЕКА
Virt-builder does not need to run as root (in fact, should not be run as root), and
doesn't use setuid, "sudo" or any similar mechanism.

--install, --update, --run and --run-command are implemented using an appliance (a small
virtual machine) so these commands do not run on the host. If you are using the
libguestfs libvirt backend and have SELinux enabled then the virtual machine is
additionally encapsulated in an SELinux container (sVirt).

However these options will have access to the host's network and since the template may
contain untrusted code, the code might try to access host network resources which it
should not. You can use --no-network to prevent this.

Firstboot commands run in the context of the guest when it is booted, and so the security
of your hypervisor / cloud should be considered.

Virt-builder injects a random seed into every guest which it builds. This helps to ensure
that TCP sequence numbers, UUIDs, ssh host keys etc are truly random when the guest boots.

You should check digital signatures and not ignore any signing errors.

КЛОНИ
If you wish to create many new guests of the same type, it is tempting to run virt-builder
once and then copy the output file. You should not do this. You should run virt-builder
once for each new guest you need.

The reason is that each clone needs to have (at least) a separate random seed, and
possibly other unique features (such as filesystem UUIDs) in future versions of virt-
builder.

Another thing you should not do is to boot the guest, then clone the booted disk image.
The reason is that some guests create unique machine IDs, SSH host keys and so on at first
boot, and you would not want clones to have duplicate identities.

Див. також virt-sysprep(1).

ШВИДКОДІЯ
The most important aspect of getting good performance is caching. Templates gets
downloaded into the cache the first time they are used, or if you use the
--cache-all-templates option. See "CACHING" above for further information.

Packages required for the --install and --update options are downloaded using the host
network connection. Setting the "http_proxy", "https_proxy" and "ftp_proxy" environment
variables to point to a local web cache may ensure they only need to be downloaded once.
You can also try using a local package repository, although this can be complex to set up
and varies according to which Linux distro you are trying to install.

Користування --no-sync

Скористайтеся --no-sync. Втім, ознайомтеся із можливими проблемами, описаними у розділі
"ПАРАМЕТРИ" вище, оскільки це може призвести до пошкодження даних на диску, якщо
використовувати неправильно.

Пропускання virt-resize

За певних умов virt-builder може пропускати крок virt-resize. Це значно пришвидшує роботу
virt-builder. Умови пропускання є такими:

• дані слід виводити до звичайного файла (не на блоковий пристрій), і

• користувачем не використано параметр --size, і

• формат виведення є тим самим, що і формат шаблона (зазвичай raw).

pxzcat

Virt-builder uses an internal implementation of pxzcat (parallel xzcat) if liblzma was
found at build time. If liblzma was not found at build time, regular "xzcat" is used
which is single-threaded.

User-Mode Linux

You can use virt-builder with the User-Mode Linux (UML) backend. This may be faster when
running virt-builder inside a virtual machine (eg. in the cloud).

Щоб увімкунути модуль UML, ознайомтеся із настановами у розділі "USER-MODE LINUX BACKEND"
in guestfs(3).

У поточній версії вам слід користуватися параметром --no-network. Це буде виправлено у
майбутній версії.

Підтримки формату виведення результатів qcow2 у UML не передбачено. Ви можете створювати
гостьові системи лише у форматі raw.

SELINUX
Guests which use SELinux (such as Fedora and Red Hat Enterprise Linux) require that each
file has a correct SELinux label.

Virt-builder does not know how to give new files a label, so there are two possible
strategies it can use to ensure correct labelling:

Користування --selinux-relabel
This runs setfiles(8) just before finalizing the guest, which sets SELinux labels
correctly in the disk image.

Це рекомендований метод.

--touch /.autorelabel
Guest templates may already contain a file called /.autorelabel or you may touch it.

For guests that use SELinux, this causes restorecon(8) to run at first boot. Guests
will reboot themselves once the first time you use them, which is normal and harmless.

Please note that if your guest uses SELinux, and you are doing operations on it which
might create new files or change existing ones, you are recommended to use
--selinux-relabel. This will help in making sure that files have the right SELinux
labels.

MACHINE READABLE OUTPUT

       The --machine-readable option can be used to make the output more machine friendly, which
       is useful when calling virt-builder from other programs, GUIs etc.

       Скористайтеся цим параметром окремо, щоб опитати систему щодо можливостей виконуваного
       файла virt-builder.  Типово виведені дані виглядатимуть якось так:

        $ virt-builder --machine-readable
        virt-builder
        arch
        config-file
        customize
        json-list
        pxzcat

       Виводиться список можливостей, по одній на рядок, і програма завершує роботу зі станом 0.

ЗМІННІ СЕРЕДОВИЩА

For other environment variables which affect all libguestfs programs, see "ENVIRONMENT
VARIABLES" in guestfs(3).

"http_proxy"
"https_proxy"
"no_proxy"
Встановити проксі-сервер для отримання даних. Ці змінні середовища (та інші) насправді
обробляються curl(1), а не virt-builder.

"HOME"
Використовується для визначення місця кешу шаблонів та місця джерел користувача. Див.
"КЕШУВАННЯ" і "ДЖЕРЕЛА ШАБЛОНІВ".

"VIRT_TOOLS_DATA_DIR"
This can point to the directory containing data files used for Windows firstboot
installation.

Зазвичай, потреби у встановленні власного значення немає. Якщо значення не
встановлено, буде використано вбудоване типове значення (щось схоже на
/usr/share/virt-tools).

Цей каталог може містити такі файли:

rhsrvany.exe
This is the RHSrvAny Windows binary, used to install a "firstboot" script in
Windows guests. It is required if you intend to use the --firstboot or
--firstboot-command options with Windows guests.

Див. також "https://github.com/rwmjones/rhsrvany"

pvvxsvc.exe
This is a Windows binary shipped with SUSE VMDP, used to install a "firstboot"
script in Windows guests. It is required if you intend to use the --firstboot or
--firstboot-command options with Windows guests.

"XDG_CACHE_HOME"
Використовується для визначення місця кешу шаблонів. Див. "КЕШУВАННЯ".

"XDG_CONFIG_HOME"
Використовується для визначення місця джерел користувача. Див. "ДЖЕРЕЛА ШАБЛОНІВ".

"XDG_CONFIG_DIRS"
Використовується для визначення місця джерел системи. Див. "ДЖЕРЕЛА ШАБЛОНІВ".

СТАН ВИХОДУ

       Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо
       сталася помилка.

ТАКОЖ ПЕРЕГЛЯНЬТЕ

       guestfs(3), guestfish(1), guestmount(1), virt-copy-out(1), virt-customize(1),
       virt-get-kernel(1), virt-install(1), virt-rescue(1), virt-resize(1), virt-sysprep(1),
       oz-install(1), gpg(1), gpg2(1), curl(1), virt-make-fs(1), genisoimage(1),
       http://libguestfs.org/.

АВТОР

       Richard W.M. Jones http://people.redhat.com/~rjones/

АВТОРСЬКІ ПРАВА

       © Red Hat Inc., 2013

LICENSE

       This program is free software; you can redistribute it and/or modify it under the terms of
       the GNU General Public License as published by the Free Software Foundation; either
       version 2 of the License, or (at your option) any later version.

       This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY;
       without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
       See the GNU General Public License for more details.

       You should have received a copy of the GNU General Public License along with this program;
       if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
       Boston, MA 02110-1301 USA.

BUGS

       To get a list of bugs against libguestfs, use this link:
       https://bugzilla.redhat.com/buglist.cgi?component=libguestfs&product=Virtualization+Tools

       To report a new bug against libguestfs, use this link:
       https://bugzilla.redhat.com/enter_bug.cgi?component=libguestfs&product=Virtualization+Tools

       When reporting a bug, please supply:

       •   The version of libguestfs.

       •   Where you got libguestfs (eg. which Linux distro, compiled from source, etc)

       •   Describe the bug accurately and give a way to reproduce it.

       •   Run libguestfs-test-tool(1) and paste the complete, unedited output into the bug
           report.