see https://bugs.archlinux.org/task/16702 for possible workarounds
]]>I find myself in the situation that a administrator before my time, installed Arch Linux on one of our servers. I am planning to keep it that way and use the server as virtualization host with qemu/kvm.
One thing I noticed during my time messing with libvirt is, that when I upgraded the kernel and did not reboot the server, the default network which comes with libvirt cannot start. This raises the question how do you guys handle kernel upgrades, so that there is a minimal downtime, if possible no down time? The current solution suggested by the administrator before me, is to just ignore all kernel upgrades until the next even release number is reached. E.g: Upgrade when 5.18 is released and then again when 5.20 is released. If that method is considered good, then my follow up question would be, on what development number shall I keep the 5.18 kernel? And is it okay to ignore the kernel upgrades via pacman.conf, or does this encourage "partial upgrades"
Thank you for your time and tips
Kind regards
Grigorios
]]>