Hi!
I wonder: What sense is in updating the kernel in a VM (e.g. fedora-32)
when that kernel isn't used when booting the VM?
For example:
user@sys-firewall ~]$ rpm -qa kernel\*
kernel-core-5.9.11-100.fc32.x86_64
kernel-5.9.12-100.fc32.x86_64
kernel-modules-5.9.14-100.fc32.x86_64
kernel-modules-5.9.11-100.fc32.x86_64
kernel-headers-5.9.13-100.fc32.x86_64
kernel-devel-5.9.11-100.fc32.x86_64
kernel-debug-devel-5.9.11-100.fc32.x86_64
kernel-modules-5.9.12-100.fc32.x86_64
kernel-devel-5.9.12-100.fc32.x86_64
kernel-devel-5.9.14-100.fc32.x86_64
kernel-core-5.9.12-100.fc32.x86_64
kernel-5.9.14-100.fc32.x86_64
kernel-core-5.9.14-100.fc32.x86_64
kernel-debug-devel-5.9.14-100.fc32.x86_64
kernel-5.9.11-100.fc32.x86_64
kernel-debug-devel-5.9.12-100.fc32.x86_64
[user@sys-firewall ~]$ uname -a
Linux sys-firewall 4.19.155-1.pvops.qubes.x86_64 #1 SMP Mon Nov 9
06:37:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Regards,
Ulrich
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/8ce2c3b5-220c-8d0f-b49e-17bbf8ed6baa%40rz.uni-regensburg.de.
