On 04/18/2017 12:23 PM, Marek Marczykowski-Górecki wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On Tue, Apr 18, 2017 at 10:54:00AM +0000, Joonas Lehtonen wrote: >> >> Joonas Lehtonen: >>> Hi, >>> >>> just a quick notice about todays kernel update. >>> >>> After upgrading, the new kernel 4.4.55 became the new default for all >>> VMs that previously used the default kernel, but >>> VMs would no longer boot because they claim that an old kernel the one >>> that got removed during the upgrade (4.4.11?) is no longer present even >>> though the VM was configured to boot the default (4.4.55). >> This was mainly an UI thing. qvm-ls -k displayed it correctly. These >> affected VMs used to have the now-removed kernel version 4.4.14-11. >> Qubes Manager just can not display not installed kernels. > So, Qubes Manager shows still old kernel? Have you tried restarting it > (Qubes Manager)? > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQEcBAEBCAAGBQJY9lm9AAoJENuP0xzK19csoA8H/jNou25t/3/ebbOHPjWTCmEd > FT6fouXFm7tN4oDw+SlUx6Hf+h/gzVhQuJc2SZIGgFT1Xk1Isj2aQvEHJvI0WLfG > XCjoe3EzYRuT6WIo77Zcbbl5+oJbeQ2Hu4Kf0kT1oWx0fL+CfzY05sIhwZrgiMLV > EnHEdOVra2aVuV67BU830rK6iu1H7TOw56ckIhrwPEdeKNamveYlh9a8Uvw7LTqo > RhVZX8wuA49/8ZJP8F31ftZoz5YDWFjxJ/jNt4V1ycAdMh5AV8BTQzf50JAlWOiy > ov1ZOKFYtNrrbJ893pTq70qYIIanK/r8MZhjhyLiaR5id05MAx90F1Ml7MzPDWs= > =Bqzx > -----END PGP SIGNATURE----- > I've posted my experiences up on the GitHub issue, but here it is too:
I've actually noticed this in my kernel testing, but I never reported it because I figured it had something to do with me going off script in compiling my own kernels. Anyway, what I've noticed: It only really occurs whenever dnf removes an older version of kernel-qubes-vm whenever dnf's installonly_limit threshold is exceeded. If you up that number higher or don't reach it, it doesn't occur and VMs set to use the default kernel get updated to use the new default kernel whenever a newer version of kernel-qubes-vm is installed. Specifically, a VM that's set to use the "default" kernel doesn't change properly to a new default whenever an older kernel-qubes-vm package is removed, even if qvm-prefs shows that VM is set to use the kernel currently set to default in Qubes Manager. If that VM had been set to use a specific kernel version prior to installation (i.e. not set to default or to pvgrub2), it's fine and the setting stays after uninstallation (although I never tested what happens if it's set to use a specific kernel version and then you uninstall that version). So I think it might have to do with the kernel-qubes-vm uninstall scripts not cleaning things up properly, however, fixing that may not necessarily fix any VMs that are currently misconfigured (in which case, a user would need to toggle switching between kernels in Qubes Manager in order for it to stick again, which is how I've been working around it). -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/od5luh%24j1f%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
