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 regards, Joonas Installed: 1000:kernel-qubes-vm-4.4.55-11.pvops.qubes.x86_64 Updated: qubes-gui-dom0-3.2.10-1.fc23.x86_64 Installed: 1000:kernel-4.4.55-11.pvops.qubes.x86_64 Updated: qubes-mgmt-salt-dom0-qvm-3.2.1-1.fc23.noarch [..] Updated: qubes-manager-3.2.11-1.fc23.x86_64 -- 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/a98e3ee3-5808-ce2e-f231-42b5d8b1b83d%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature