From d4c615b7686186708c840d3261fbeb0a7619d650 Mon Sep 17 00:00:00 2001 From: Randy <177127055+RandyTheOtter@users.noreply.github.com> Date: Mon, 22 Dec 2025 21:57:34 +0000 Subject: [PATCH 1/9] managing-vm-kernels.rst : update first usage example with its modern equivalent --- user/advanced-topics/managing-vm-kernels.rst | 21 +++++++++----------- 1 file changed, 9 insertions(+), 12 deletions(-) diff --git a/user/advanced-topics/managing-vm-kernels.rst b/user/advanced-topics/managing-vm-kernels.rst index 3a5cfb241..d17af014e 100644 --- a/user/advanced-topics/managing-vm-kernels.rst +++ b/user/advanced-topics/managing-vm-kernels.rst @@ -24,18 +24,15 @@ To select which kernel a given VM will use, you can either use Qubes Manager (VM .. code:: console - [user@dom0 ~]$ qvm-prefs -s my-appvm kernel - Missing kernel version argument! - Possible values: - 1) default - 2) none (kernels subdir in VM) - 3) , one of: - - 3.18.16-3 - - 3.18.17-4 - - 3.19.fc20 - - 3.18.10-2 - [user@dom0 ~]$ qvm-prefs -s my-appvm kernel 3.18.17-4 - [user@dom0 ~]$ qvm-prefs -s my-appvm kernel default + [user@dom0 ~]$ dnf list --installed kernel + Installed Packages + kernel.x86_64 1000:6.12.47-1.qubes.fc37 @qubes-dom0-cached + kernel.x86_64 1000:6.12.54-1.qubes.fc37 @qubes-dom0-cached + kernel.x86_64 1000:6.12.59-1.qubes.fc37 @qubes-dom0-cached + [user@dom0 ~]$ qvm-prefs my-appvm kernel + 6.12.59-1.fc37 + [user@dom0 ~]$ qvm-prefs my-appvm kernel 6.12.54-1.fc37 + [user@dom0 ~]$ qvm-prefs -D my-appvm kernel To check/change the default kernel you can either go to “Global settings” in Qubes Manager, or use the ``qubes-prefs`` tool: From 32d5ee102caf6efb4e6c7498860b7e3faf16be71 Mon Sep 17 00:00:00 2001 From: Randy <177127055+RandyTheOtter@users.noreply.github.com> Date: Mon, 22 Dec 2025 22:06:40 +0000 Subject: [PATCH 2/9] managing-vm-kernels.rst : update kernel setting and listing --- user/advanced-topics/managing-vm-kernels.rst | 32 ++++++++++---------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/user/advanced-topics/managing-vm-kernels.rst b/user/advanced-topics/managing-vm-kernels.rst index d17af014e..d6e0db70e 100644 --- a/user/advanced-topics/managing-vm-kernels.rst +++ b/user/advanced-topics/managing-vm-kernels.rst @@ -39,37 +39,37 @@ To check/change the default kernel you can either go to “Global settings” in .. code:: console - [user@dom0 ~]$ qubes-prefs - clockvm : sys-net - default-fw-netvm : sys-net - default-kernel : 3.18.17-4 - default-netvm : sys-firewall - default-template : fedora-21 - updatevm : sys-firewall - [user@dom0 ~]$ qubes-prefs -s default-kernel 3.19.fc20 + [user@dom0 ~]$ qubes-prefs default-kernel + 6.12.59-1.fc37 + [user@dom0 ~]$ qubes-prefs default-kernel 6.12.54-1.fc37 To view kernel options, you can use the GUI VM Settings tool; to view and change them, use ``qvm-prefs`` commandline tool: .. code:: console - [user@dom0 ~]$ qvm-prefs -g work kernelopts - nopat - [user@dom0 ~]$ qvm-prefs -s work kernelopts "nopat apparmor=1 security=apparmor" + [user@dom0 ~]$ qvm-prefs my-appvm kernelopts + swiotlb=2048 + [user@dom0 ~]$ qvm-prefs my-appvm kernelopts "swiotlb=10240 apparmor=1 security=apparmor" Installing different kernel using Qubes kernel package ------------------------------------------------------ -VM kernels are packaged by the Qubes team in the ``kernel-qubes-vm`` packages. Generally, the system will keep the three newest available versions. You can list them with the ``rpm`` command: +VM kernels are packaged by the Qubes team in the ``kernel`` packages. Generally, the system will keep the three newest available versions. You can list them using ``rpm`` or ``dnf`` commands: .. code:: console - [user@dom0 ~]$ rpm -qa 'kernel-qubes-vm*' - kernel-qubes-vm-3.18.10-2.pvops.qubes.x86_64 - kernel-qubes-vm-3.18.16-3.pvops.qubes.x86_64 - kernel-qubes-vm-3.18.17-4.pvops.qubes.x86_64 + [user@dom0 ~]$ rpm -qa 'kernel' + kernel-6.12.47-1.qubes.fc37.x86_64 + kernel-6.12.54-1.qubes.fc37.x86_64 + kernel-6.12.59-1.qubes.fc37.x86_64 + [user@dom0 ~]$ dnf list --installed kernel + Installed Packages + kernel.x86_64 1000:6.12.47-1.qubes.fc37 @qubes-dom0-cached + kernel.x86_64 1000:6.12.54-1.qubes.fc37 @qubes-dom0-cached + kernel.x86_64 1000:6.12.59-1.qubes.fc37 @qubes-dom0-cached If you want a more recent version, you can check the ``qubes-dom0-unstable`` repository. There is also the ``kernel-latest-qubes-vm`` package which should provide a more recent (non-LTS) kernel, but has received much less testing. As the names suggest, keep in mind that those packages may be less stable than the default ones. From c8b5cf6df26f05b6534553cec180ded320dc7032 Mon Sep 17 00:00:00 2001 From: Randy <177127055+RandyTheOtter@users.noreply.github.com> Date: Tue, 23 Dec 2025 00:49:02 +0000 Subject: [PATCH 3/9] managing-vm-kernels.rst : remove `kernel-devel` requirement It works without `kernel-devel` package --- user/advanced-topics/managing-vm-kernels.rst | 3 --- 1 file changed, 3 deletions(-) diff --git a/user/advanced-topics/managing-vm-kernels.rst b/user/advanced-topics/managing-vm-kernels.rst index d6e0db70e..f377dd372 100644 --- a/user/advanced-topics/managing-vm-kernels.rst +++ b/user/advanced-topics/managing-vm-kernels.rst @@ -253,9 +253,6 @@ If you’d like to use a different kernel than default, continue reading. Installing kernel in Fedora VM ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Install whatever kernel you want. You need to also ensure you have the ``kernel-devel`` package for the same kernel version installed. - If you are using a distribution kernel package (``kernel`` package), the initramfs and kernel modules may be handled automatically. If you are using a manually built kernel, you need to handle this on your own. Take a look at the ``dkms`` documentation, especially the ``dkms autoinstall`` command may be useful. If you did not see the ``kernel`` install rebuild your initramfs, or are using a manually built kernel, you will need to rebuild it yourself. Replace the version numbers in the example below with the ones appropriate to the kernel you are installing: .. code:: console From 52cecdfd53920cba4fa970939efbdcfec8219872 Mon Sep 17 00:00:00 2001 From: Randy <177127055+RandyTheOtter@users.noreply.github.com> Date: Tue, 23 Dec 2025 01:03:47 +0000 Subject: [PATCH 4/9] managing-vm-kernels.rst : Add instructions for fedora distribution kernel --- user/advanced-topics/managing-vm-kernels.rst | 32 +++++++++++++++++++- 1 file changed, 31 insertions(+), 1 deletion(-) diff --git a/user/advanced-topics/managing-vm-kernels.rst b/user/advanced-topics/managing-vm-kernels.rst index f377dd372..00485694a 100644 --- a/user/advanced-topics/managing-vm-kernels.rst +++ b/user/advanced-topics/managing-vm-kernels.rst @@ -253,7 +253,37 @@ If you’d like to use a different kernel than default, continue reading. Installing kernel in Fedora VM ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -If you are using a distribution kernel package (``kernel`` package), the initramfs and kernel modules may be handled automatically. If you are using a manually built kernel, you need to handle this on your own. Take a look at the ``dkms`` documentation, especially the ``dkms autoinstall`` command may be useful. If you did not see the ``kernel`` install rebuild your initramfs, or are using a manually built kernel, you will need to rebuild it yourself. Replace the version numbers in the example below with the ones appropriate to the kernel you are installing: +Distribution kernel +^^^^^^^^^^^^^^^^^^^ + +Install kernel and the packages required to run vm with its own kernel: + +.. code: console + + [root@fedora-vm ~]# dnf install kernel qubes-kernel-vm-support grub2 + + + +Once the kernel is installed, you need to setup ``grub2`` by running: + +.. code:: console + + [root@fedora-vm ~]# grub2-install /dev/xvda + + + +Finally, you need to create a GRUB configuration. You may want to adjust some settings in ``/etc/default/grub``; for example, lower ``GRUB_TIMEOUT`` to speed up VM startup. Then, you need to generate the actual configuration. In Fedora it can be done using the ``grub2-mkconfig`` tool: + +.. code:: console + + [root@fedora-vm ~]# grub2-mkconfig -o /boot/grub2/grub.cfg + + + +Custom kernel +^^^^^^^^^^^^^ + +If you are using a manually built kernel, you need to handle the initramfs and kernel modules on your own. Take a look at the ``dkms`` documentation, especially the ``dkms autoinstall`` command may be useful. If you did not see the ``kernel`` install rebuild your initramfs, or are using a manually built kernel, you will need to rebuild it yourself. Replace the version numbers in the example below with the ones appropriate to the kernel you are installing: .. code:: console From 7618c742bd8747be89e18a285a90a7a215756856 Mon Sep 17 00:00:00 2001 From: Randy <177127055+RandyTheOtter@users.noreply.github.com> Date: Tue, 23 Dec 2025 22:20:27 +0000 Subject: [PATCH 5/9] managing-vm-kernels.rst : various (read extended) 1. Update "Using kernel installed in the VM" section: - Align user prompt to the rest of the document - Remove template version numbers - Remove note about installing custom kernel (both default and custom kernel instructions are provided now) - Clarify that only non-minimal templates have necessary packages preinstalled 2. Fix typo in fedora distribution kernel code block --- user/advanced-topics/managing-vm-kernels.rst | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/user/advanced-topics/managing-vm-kernels.rst b/user/advanced-topics/managing-vm-kernels.rst index 00485694a..ee8f5bf57 100644 --- a/user/advanced-topics/managing-vm-kernels.rst +++ b/user/advanced-topics/managing-vm-kernels.rst @@ -239,17 +239,15 @@ Using kernel installed in the VM -------------------------------- -Both debian-9 and fedora-26 templates already have grub and related tools preinstalled so if you want to use one of the distribution kernels, all you need to do is clone either template to a new one, then: +Non-minimal debian and fedora templates already have grub and related tools preinstalled so if you want to use one of the distribution kernels, all you need to do is clone either template to a new one, then: .. code:: console - $ qvm-prefs virt_mode hvm - $ qvm-prefs kernel '' + [user@dom0 ~]$ qvm-prefs virt_mode hvm + [user@dom0 ~]$ qvm-prefs kernel '' -If you’d like to use a different kernel than default, continue reading. - Installing kernel in Fedora VM ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -258,7 +256,7 @@ Distribution kernel Install kernel and the packages required to run vm with its own kernel: -.. code: console +.. code:: console [root@fedora-vm ~]# dnf install kernel qubes-kernel-vm-support grub2 From 2f6b9c0157887ecfd9135560074de6a51d3287ec Mon Sep 17 00:00:00 2001 From: Randy <177127055+RandyTheOtter@users.noreply.github.com> Date: Tue, 23 Dec 2025 22:43:27 +0000 Subject: [PATCH 6/9] managing-vm-kernels.rst : make console code directives consistent use `[user@host ~]$` paradigm everywhere --- user/advanced-topics/managing-vm-kernels.rst | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/user/advanced-topics/managing-vm-kernels.rst b/user/advanced-topics/managing-vm-kernels.rst index ee8f5bf57..fd97a8520 100644 --- a/user/advanced-topics/managing-vm-kernels.rst +++ b/user/advanced-topics/managing-vm-kernels.rst @@ -285,7 +285,7 @@ If you are using a manually built kernel, you need to handle the initramfs and k .. code:: console - $ sudo dracut -f /boot/initramfs-4.15.14-200.fc26.x86_64.img 4.15.14-200.fc26.x86_64 + [root@fedora-vm ~]# dracut -f /boot/initramfs-4.15.14-200.fc26.x86_64.img 4.15.14-200.fc26.x86_64 @@ -293,7 +293,7 @@ Once the kernel is installed, you need to setup ``grub2`` by running: .. code:: console - $ sudo grub2-install /dev/xvda + [root@fedora-vm ~]# grub2-install /dev/xvda @@ -301,7 +301,7 @@ Finally, you need to create a GRUB configuration. You may want to adjust some se .. code:: console - $ sudo grub2-mkconfig -o /boot/grub2/grub.cfg + [root@fedora-vm ~]# grub2-mkconfig -o /boot/grub2/grub.cfg @@ -343,7 +343,7 @@ Install distribution kernel image, kernel headers and the grub. .. code:: console - $ sudo apt install linux-image-amd64 linux-headers-amd64 grub2 qubes-kernel-vm-support + [root@debian-vm ~]# apt install linux-image-amd64 linux-headers-amd64 grub2 qubes-kernel-vm-support @@ -351,7 +351,7 @@ If you are doing that on a qube based on “Debian Minimal” template, a grub g .. code:: console - $ sudo grub-install /dev/xvda + [root@debian-vm ~]# grub-install /dev/xvda @@ -405,7 +405,7 @@ Run DKMS. Replace this with actual kernel version. .. code:: console - $ sudo dkms autoinstall -k + [root@debian-vm ~]# dkms autoinstall -k For example. @@ -414,7 +414,7 @@ For example. .. code:: console - $ sudo dkms autoinstall -k 4.19.0-6-amd64 + [root@debian-vm ~]# dkms autoinstall -k 4.19.0-6-amd64 Update initramfs. @@ -423,14 +423,14 @@ Update initramfs. .. code:: console - $ sudo update-initramfs -u + [root@debian-vm ~]# update-initramfs -u The output should look like this: .. code:: console - $ sudo dkms autoinstall -k 3.16.0-4-amd64 + [root@debian-vm ~]# dkms autoinstall -k 3.16.0-4-amd64 u2mfn: Running module version sanity check. From b08d7811d12f7497df43ac5fb760262fe1a067d3 Mon Sep 17 00:00:00 2001 From: Randy <177127055+RandyTheOtter@users.noreply.github.com> Date: Fri, 26 Dec 2025 22:30:18 +0000 Subject: [PATCH 7/9] managing-vm-kernels.rst : update installation of unstable kernel --- user/advanced-topics/managing-vm-kernels.rst | 152 ++++++++++++------- 1 file changed, 100 insertions(+), 52 deletions(-) diff --git a/user/advanced-topics/managing-vm-kernels.rst b/user/advanced-topics/managing-vm-kernels.rst index fd97a8520..073373858 100644 --- a/user/advanced-topics/managing-vm-kernels.rst +++ b/user/advanced-topics/managing-vm-kernels.rst @@ -72,79 +72,127 @@ VM kernels are packaged by the Qubes team in the ``kernel`` packages. Generally, kernel.x86_64 1000:6.12.59-1.qubes.fc37 @qubes-dom0-cached -If you want a more recent version, you can check the ``qubes-dom0-unstable`` repository. There is also the ``kernel-latest-qubes-vm`` package which should provide a more recent (non-LTS) kernel, but has received much less testing. As the names suggest, keep in mind that those packages may be less stable than the default ones. +If you want a more recent version, you can check ``qubes-dom0-unstable`` and ``qubes-dom0-current-testing`` repositories. There is also ``kernel-latest`` package which should provide a more recent (non-LTS) kernel, but has received much less testing. As the names suggest, keep in mind that those packages may be less stable than the default ones. -To check available versions in the ``qubes-dom0-unstable`` repository: +To check available versions in the ``qubes-dom0-current-testing`` repository: .. code:: console - [user@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable --action=list kernel-qubes-vm - Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time... - Running command on VM: 'sys-firewall'... - Loaded plugins: langpacks, post-transaction-actions, yum-qubes-hooks - Installed Packages - kernel-qubes-vm.x86_64 1000:3.18.10-2.pvops.qubes installed - kernel-qubes-vm.x86_64 1000:3.18.16-3.pvops.qubes installed - kernel-qubes-vm.x86_64 1000:3.18.17-4.pvops.qubes installed - Available Packages - kernel-qubes-vm.x86_64 1000:4.1.12-6.pvops.qubes qubes-dom0-unstable + [root@dom0 ~]# qubes-dom0-update --enablerepo=qubes-dom0-current-testing --action=list kernel-latest kernel + Using sys-whonix as UpdateVM for Dom0 + Updating package lists. This may take a while... + Fedora 37 - x86_64 3.1 kB/s | 5.1 kB 00:01 + Fedora 37 - x86_64 - Updates 3.2 kB/s | 5.0 kB 00:01 + Qubes Host Repository (updates) 2.4 kB/s | 2.7 kB 00:01 + Qubes Host Repository (updates-testing) 3.1 kB/s | 2.8 kB 00:00 + Installed Packages + kernel.x86_64 1000:6.12.47-1.qubes.fc37 @System + kernel.x86_64 1000:6.12.54-1.qubes.fc37 @System + kernel.x86_64 1000:6.12.59-1.qubes.fc37 @System + Available Packages + kernel.src 1000:6.12.63-1.qubes.fc37 qubes-dom0-current-testing + kernel.x86_64 1000:6.12.63-1.qubes.fc37 qubes-dom0-current-testing + kernel-latest.src 1000:6.18.2-1.qubes.fc37 qubes-dom0-current-testing + kernel-latest.x86_64 1000:6.18.2-1.qubes.fc37 qubes-dom0-current-testing No packages downloaded - Installed Packages - kernel-qubes-vm.x86_64 1000:3.18.10-2.pvops.qubes @anaconda/R3.0 - kernel-qubes-vm.x86_64 1000:3.18.16-3.pvops.qubes @/kernel-qubes-vm-3.18.16-3.pvops.qubes.x86_64 - kernel-qubes-vm.x86_64 1000:3.18.17-4.pvops.qubes @qubes-dom0-cached -Installing a new version from ``qubes-dom0-unstable`` repository: +Installing a new version from ``qubes-dom0-current-testing`` repository: .. code:: console - [user@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable kernel-qubes-vm - Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time... - Running command on VM: 'sys-firewall'... - Loaded plugins: langpacks, post-transaction-actions, yum-qubes-hooks - Resolving Dependencies - (...) - - =========================================================================================== - Package Arch Version Repository Size - =========================================================================================== + [root@dom0 ~]# qubes-dom0-update --enablerepo=qubes-dom0-current-testing kernel + Using sys-whonix as UpdateVM for Dom0 + Downloading packages. This may take a while... + Fedora 37 - x86_64 1.8 kB/s | 5.1 kB 00:02 + Fedora 37 - x86_64 - Updates 3.5 kB/s | 5.0 kB 00:01 + Qubes Host Repository (updates) 2.1 kB/s | 2.7 kB 00:01 + Qubes Host Repository (updates-testing) 2.2 kB/s | 2.8 kB 00:01 + Last metadata expiration check: 0:00:01 ago on Fri Dec 26 21:49:54 2025. + Package kernel-1000:6.12.47-1.qubes.fc37.x86_64 is already installed. + Package kernel-1000:6.12.54-1.qubes.fc37.x86_64 is already installed. + Package kernel-1000:6.12.59-1.qubes.fc37.x86_64 is already installed. + Dependencies resolved. + ================================================================================ + Package Arch Version Repository Size + ================================================================================ + Installing: + kernel x86_64 1000:6.12.63-1.qubes.fc37 qubes-dom0-current-testing 13 M + kernel-modules + x86_64 1000:6.12.63-1.qubes.fc37 qubes-dom0-current-testing 84 M + Removing: + kernel x86_64 1000:6.12.47-1.qubes.fc37 @System 42 M + kernel-modules + x86_64 1000:6.12.47-1.qubes.fc37 @System 508 M + + Transaction Summary + ================================================================================ + Install 2 Packages + Remove 2 Packages + + Total download size: 97 M + DNF will only download packages for the transaction. + Downloading Packages: + + ... + + Complete! + The downloaded packages were saved in cache until the next successful transaction. + You can remove cached packages by executing 'dnf clean packages'. + Qubes OS Repository for Dom0 2.9 MB/s | 3.0 kB 00:00 + Qubes OS Repository for Dom0 2.2 MB/s | 66 kB 00:00 + Package kernel-1000:6.12.47-1.qubes.fc37.x86_64 is already installed. + Package kernel-1000:6.12.54-1.qubes.fc37.x86_64 is already installed. + Package kernel-1000:6.12.59-1.qubes.fc37.x86_64 is already installed. + Dependencies resolved. + Nothing to do. + Complete! + [root@dom0 ~]# dnf list kernel + Qubes OS Repository for Dom0 2.9 MB/s | 3.0 kB 00:00 + Installed Packages + kernel.x86_64 1000:6.12.47-1.qubes.fc37 @qubes-dom0-cached + kernel.x86_64 1000:6.12.54-1.qubes.fc37 @qubes-dom0-cached + kernel.x86_64 1000:6.12.59-1.qubes.fc37 @qubes-dom0-cached + Available Packages + kernel.x86_64 1000:6.12.63-1.qubes.fc37 qubes-dom0-cached + [root@dom0 ~]# dnf install kernel-1000:6.12.63-1.qubes.fc37 + Qubes OS Repository for Dom0 2.9 MB/s | 3.0 kB 00:00 + Dependencies resolved. + ================================================================================== + Package Arch Version Repository Size + ================================================================================== Installing: - kernel-qubes-vm x86_64 1000:4.1.12-6.pvops.qubes qubes-dom0-cached 40 M + kernel x86_64 1000:6.12.63-1.qubes.fc37 qubes-dom0-cached 13 M + kernel-modules x86_64 1000:6.12.63-1.qubes.fc37 qubes-dom0-cached 84 M Removing: - kernel-qubes-vm x86_64 1000:3.18.10-2.pvops.qubes @anaconda/R3.0 134 M + kernel x86_64 1000:6.12.47-1.qubes.fc37 @qubes-dom0-cached 42 M + kernel-modules x86_64 1000:6.12.47-1.qubes.fc37 @qubes-dom0-cached 508 M Transaction Summary - =========================================================================================== - Install 1 Package - Remove 1 Package - - Total download size: 40 M - Is this ok [y/d/N]: y - Downloading packages: + ================================================================================== + Install 2 Packages + Remove 2 Packages + + Total size: 97 M + Is this ok [y/N]: y + Downloading Packages: Running transaction check + Transaction check succeeded. Running transaction test - Transaction test succeeded - Running transaction (shutdown inhibited) - Installing : 1000:kernel-qubes-vm-4.1.12-6.pvops.qubes.x86_64 1/2 - mke2fs 1.42.12 (29-Aug-2014) - This kernel version is used by at least one VM, cannot remove - error: %preun(kernel-qubes-vm-1000:3.18.10-2.pvops.qubes.x86_64) scriptlet failed, exit status 1 - Error in PREUN scriptlet in rpm package 1000:kernel-qubes-vm-3.18.10-2.pvops.qubes.x86_64 - Verifying : 1000:kernel-qubes-vm-4.1.12-6.pvops.qubes.x86_64 1/2 - Verifying : 1000:kernel-qubes-vm-3.18.10-2.pvops.qubes.x86_64 2/2 + Transaction test succeeded. + Running transaction - Installed: - kernel-qubes-vm.x86_64 1000:4.1.12-6.pvops.qubes + ... - Failed: - kernel-qubes-vm.x86_64 1000:3.18.10-2.pvops.qubes + Installed: + kernel-1000:6.12.63-1.qubes.fc37.x86_64 + kernel-modules-1000:6.12.63-1.qubes.fc37.x86_64 + Removed: + kernel-1000:6.12.47-1.qubes.fc37.x86_64 + kernel-modules-1000:6.12.47-1.qubes.fc37.x86_64 Complete! - [user@dom0 ~]$ - -In the above example, it tries to remove the 3.18.10-2.pvops.qubes kernel (to keep only three installed), but since some VM uses it, it fails. Installation of the new package is unaffected by this event. The newly installed package is set as the default VM kernel. From 6bd49a25f331943c27e170b646577285799755d7 Mon Sep 17 00:00:00 2001 From: Randy <177127055+RandyTheOtter@users.noreply.github.com> Date: Fri, 26 Dec 2025 22:42:29 +0000 Subject: [PATCH 8/9] managing-vm-kernels.rst : add a note about setting memory Sometimes people forget to do this: https://forum.qubes-os.org/t/cannot-boot-to-native-fedora-42-kernel/38087/1 --- user/advanced-topics/managing-vm-kernels.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/user/advanced-topics/managing-vm-kernels.rst b/user/advanced-topics/managing-vm-kernels.rst index 073373858..7e97ee205 100644 --- a/user/advanced-topics/managing-vm-kernels.rst +++ b/user/advanced-topics/managing-vm-kernels.rst @@ -295,6 +295,12 @@ Non-minimal debian and fedora templates already have grub and related tools prei [user@dom0 ~]$ qvm-prefs kernel '' +Depending on vm and kernel you're running, you may also want to disable memory balancing and change the amount of memory vm has: +.. code:: console + + [user@dom0 ~]$ qvm-prefs maxmem 0 + [user@dom0 ~]$ qvm-prefs memory 2000 + Installing kernel in Fedora VM ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ From ca042ee6c3ff57e89aa0669b45401789d230fb9a Mon Sep 17 00:00:00 2001 From: Randy <177127055+RandyTheOtter@users.noreply.github.com> Date: Fri, 26 Dec 2025 22:45:08 +0000 Subject: [PATCH 9/9] managing-vm-kernels.rst : fix code block hopefully --- user/advanced-topics/managing-vm-kernels.rst | 1 + 1 file changed, 1 insertion(+) diff --git a/user/advanced-topics/managing-vm-kernels.rst b/user/advanced-topics/managing-vm-kernels.rst index 7e97ee205..2d2edf623 100644 --- a/user/advanced-topics/managing-vm-kernels.rst +++ b/user/advanced-topics/managing-vm-kernels.rst @@ -296,6 +296,7 @@ Non-minimal debian and fedora templates already have grub and related tools prei Depending on vm and kernel you're running, you may also want to disable memory balancing and change the amount of memory vm has: + .. code:: console [user@dom0 ~]$ qvm-prefs maxmem 0