summaryrefslogtreecommitdiff
path: root/docs/installation/virtual/libvirt.rst
diff options
context:
space:
mode:
authorrebortg <github@ghlr.de>2020-12-11 22:39:26 +0100
committerrebortg <github@ghlr.de>2020-12-11 22:39:26 +0100
commit7a85ac512aadf03eb73242355757ca7184e17674 (patch)
treed837c2426c460234636abd623fd12563516caa1b /docs/installation/virtual/libvirt.rst
parentac6b335b1aeed78c087c27763c527d7d38093aca (diff)
downloadvyos-documentation-7a85ac512aadf03eb73242355757ca7184e17674.tar.gz
vyos-documentation-7a85ac512aadf03eb73242355757ca7184e17674.zip
installation: fix lint errors
Diffstat (limited to 'docs/installation/virtual/libvirt.rst')
-rw-r--r--docs/installation/virtual/libvirt.rst32
1 files changed, 20 insertions, 12 deletions
diff --git a/docs/installation/virtual/libvirt.rst b/docs/installation/virtual/libvirt.rst
index 0d624b94..ff896d07 100644
--- a/docs/installation/virtual/libvirt.rst
+++ b/docs/installation/virtual/libvirt.rst
@@ -4,9 +4,10 @@
Running on Libvirt Qemu/KVM
***************************
-Libvirt is an open-source API, daemon and management tool for managing platform virtualization.
-There are several ways to deploy VyOS on libvirt kvm. Use Virt-manager and native CLI.
-In an example we will be use use 4 gigabytes of memory, 2 cores CPU and default network virbr0.
+Libvirt is an open-source API, daemon and management tool for managing platform
+virtualization. There are several ways to deploy VyOS on libvirt kvm.
+Use Virt-manager and native CLI. In an example we will be use use 4 gigabytes
+of memory, 2 cores CPU and default network virbr0.
CLI
===
@@ -14,8 +15,9 @@ CLI
Deploy from ISO
---------------
-Create VM name ``vyos_r1``. You must specify the path to the ``ISO`` image, the disk ``qcow2`` will be created automatically.
-The ``default`` network is the virtual network (type Virtio) created by the hypervisor with NAT.
+Create VM name ``vyos_r1``. You must specify the path to the ``ISO`` image,
+the disk ``qcow2`` will be created automatically. The ``default`` network is
+the virtual network (type Virtio) created by the hypervisor with NAT.
.. code-block:: none
@@ -46,11 +48,13 @@ Connect to VM with command ``virsh console vyos_r1``
vyos@vyos:~$ install image
-After installation - exit from the console using the key combination ``Ctrl + ]`` and reboot the system.
+After installation - exit from the console using the key combination
+``Ctrl + ]`` and reboot the system.
Deploy from qcow2
-----------------
-The convenience of using :abbr:`KVM (Kernel-based Virtual Machine)` images is that they don't need to be installed.
+The convenience of using :abbr:`KVM (Kernel-based Virtual Machine)`
+images is that they don't need to be installed.
Download predefined VyOS.qcow2 image for ``KVM``
.. code-block:: none
@@ -92,13 +96,15 @@ The system is fully operational.
Virt-manager
============
-The virt-manager application is a desktop user interface for managing virtual machines through libvirt.
-On the linux open :abbr:`VMM (Virtual Machine Manager)`.
+The virt-manager application is a desktop user interface for managing virtual
+machines through libvirt. On the linux open
+:abbr:`VMM (Virtual Machine Manager)`.
Deploy from ISO
---------------
-1. Open :abbr:`VMM (Virtual Machine Manager)` and Create a new :abbr:`VM (Virtual Machine)`
+1. Open :abbr:`VMM (Virtual Machine Manager)` and Create a new
+ :abbr:`VM (Virtual Machine)`
2. Choose ``Local install media`` (ISO)
@@ -134,13 +140,15 @@ Download predefined VyOS.qcow2 image for ``KVM``
curl --url link_to_vyos_kvm.qcow2 --output /var/lib/libvirt/images/vyos_kvm.qcow2
-1. Open :abbr:`VMM (Virtual Machine Manager)` and Create a new :abbr:`VM (Virtual Machine)`
+1. Open :abbr:`VMM (Virtual Machine Manager)` and Create a new
+ :abbr:`VM (Virtual Machine)`
2. Choose ``Import existing disk`` image
.. figure:: /_static/images/virt-libvirt-qc-01.png
-3. Choose the path to the image ``vyos_kvm.qcow2`` that was previously downloaded . Operation System can be any Debian based.
+3. Choose the path to the image ``vyos_kvm.qcow2`` that was previously
+ downloaded . Operation System can be any Debian based.
.. figure:: /_static/images/virt-libvirt-qc-02.png