From 704f95484aecb3bebb74451a34fcd487d15a1c93 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marek=20Marczykowski-G=C3=B3recki?= Date: Thu, 4 Aug 2016 12:54:56 +0200 Subject: [PATCH] Fix ToC in managing-vm-kernel --- configuration/managing-vm-kernel.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/configuration/managing-vm-kernel.md b/configuration/managing-vm-kernel.md index 5f4f0e8b..a80384a6 100644 --- a/configuration/managing-vm-kernel.md +++ b/configuration/managing-vm-kernel.md @@ -7,7 +7,7 @@ redirect_from: --- VM kernel managed by dom0 -------------------------- +========================= By default VMs kernels are provided by dom0. This means that: @@ -47,7 +47,7 @@ updatevm : sys-firewall ~~~ Installing different kernel using Qubes kernel package -================================== +---------------------------------- VM kernels are packages by Qubes team in `kernel-qubes-vm` packages. Generally system will keep the 3 newest available versions. You can list them with the `rpm` command: @@ -135,7 +135,7 @@ In the above example, it tries to remove 3.18.10-2.pvops.qubes kernel (to keep o The newly installed package is set as default VM kernel. Installing different VM kernel based on dom0 kernel -=================================================== +--------------------------------------------------- It is possible to package kernel installed in dom0 as VM kernel. This makes it possible to use VM kernel, which is not packaged by Qubes team. This includes: @@ -203,7 +203,7 @@ mke2fs 1.42.12 (29-Aug-2014) ~~~ Using kernel installed in the VM -================================ +-------------------------------- **This option is available only in Qubes R3.1 or newer**