On Wednesday, April 19, 2017 at 11:23:26 AM UTC-4, Joonas Lehtonen wrote: > Marek Marczykowski-Górecki: > > 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)? > > Qubes Manager showed the new kernel (4.4.55-11) while qvm-ls -k showed > the old (removed) kernel. > > Qubes Manager got restarted automatically during updating dom0.
I'm thinking more its what Reg said I have a felling all my affected vms were created at the same time. My debian clone is newer then my fedora clone. Obviously I don't back up the sys vms or untrusteds. and those were only ones not affected. -- 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/9e5edb46-27a2-4ca7-9901-ecbec07c2779%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
