diff --git a/user/advanced-configuration/managing-vm-kernel.md b/user/advanced-configuration/managing-vm-kernel.md index d6cddacf..2df4598d 100644 --- a/user/advanced-configuration/managing-vm-kernel.md +++ b/user/advanced-configuration/managing-vm-kernel.md @@ -9,7 +9,9 @@ redirect_from: VM kernel managed by dom0 ========================= -By default, VMs kernels are provided by dom0. This means that: +By default, VMs kernels are provided by dom0. +(See [here][dom0-kernel-upgrade] for information about upgrading kernels in dom0.) +This means that: 1. You can select the kernel version (using GUI VM Settings tool or `qvm-prefs` commandline tool); 2. You can modify kernel options (using `qvm-prefs` commandline tool); @@ -331,3 +333,6 @@ In any case you can later access the VM's logs (especially the VM console log `/ You can always set the kernel back to some dom0-provided value to fix a VM kernel installation. + +[dom0-kernel-upgrade]: /doc/software-update-dom0/#kernel-upgrade + diff --git a/user/advanced-configuration/newer-hardware-troubleshooting.md b/user/advanced-configuration/newer-hardware-troubleshooting.md index 23bd35d4..4ed30ba8 100644 --- a/user/advanced-configuration/newer-hardware-troubleshooting.md +++ b/user/advanced-configuration/newer-hardware-troubleshooting.md @@ -10,8 +10,8 @@ Troubleshooting newer hardware By default, the kernel that is installed in dom0 comes from the `kernel` package, which is an older Linux LTS kernel. For most cases this works fine since the Linux kernel developers backport fixes to this kernel, but for some newer hardware, you may run into issues. For example, the audio might not work if the sound card is too new for the LTS kernel. - -To fix this, you can try the `kernel-latest` package - though be aware that it's less tested! +To fix this, you can try the `kernel-latest` package -- though be aware that it's less tested! +(See [here][dom0-kernel-upgrade] for more information about upgrading kernels in dom0.) In dom0: ~~~ @@ -23,3 +23,7 @@ You can double-check that the boot used the newer kernel with `uname -r`, which Compare this with the output of `rpm -q kernel`. If the start of `uname -r` matches one of the versions printed by `rpm`, then you're still using the Linux LTS kernel, and you'll probably need to manually fix your boot settings. If `uname -r` reports a higher version number, then you've successfully booted with the kernel shipped by `kernel-latest`. + + +[dom0-kernel-upgrade]: /doc/software-update-dom0/#kernel-upgrade +