Marek Marczykowski: > On Tue, Apr 18, 2017 at 05:33:00PM +0000, Michael Carbone 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). >>> >>> Easy workaround: >>> configure the VM to boot 4.4.38 and save. >>> reopen the preferences and configure it to boot the latest default >>> -> boot the vm > >> Encountered the same issues on update. There was also a broken pipe >> error during the update process. > >> Workaround works, needs to be done manually for each affected VM (which >> qvm-ls -k lists). > > Do we have an issue for this on github? I can't find one.
Just made one: https://github.com/QubesOS/qubes-issues/issues/2757 -- Michael Carbone Qubes OS | https://www.qubes-os.org @QubesOS <https://www.twitter.com/QubesOS> PGP fingerprint: D3D8 BEBF ECE8 91AC 46A7 30DE 63FC 4D26 84A7 33B4 -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6b05ecb8-3f1b-a9fb-9eb3-0e7428255356%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
