On 1/1/21 1:53 PM, Gregory Nowak wrote: > On Fri, Jan 01, 2021 at 12:24:38AM -0600, David C. Rankin wrote: >> If I boot with the Arch .iso and mount the current directories, is there >> anything other than the new 6.1.17 guest addition kernel modules I can >> manually wipe to give the guest the best chance of starting? > > You shouldn't need to wipe anything. Simply setting your boot loader > to boot the old kernel by default should get you back into a > functioning system. > > Greg > >
I recovered the guest. Since Arch doesn't keep the prior kernel, it was a bit more involved. Booting from the Arch .iso I was able to chroot the guest and use the vbox-uninstall-guest-additions to remove the guest additions from 5.10.3. As you can probably suspect, that didn't help. So booting from the arch .iso again, chrooting the guest and doing a manual downgrade of the kernel to 5.9.14 and rebooting fixed the issue. Guest additions reinstalled and all is well. But... that brings up the question of why it cratered the guest. The build of 5.10.3 modules from the 6.1.17 testcase on the host went as the testcase module builds had done 10 times before. Launching the guest and updating the guest kernel to 5.10.3 to all appearances went fine too. If I recall correctly booting the guest on 5.10.3 worked as well, but after installing the guest additions it all went to hell in a handbasket... So is this just a problem with the testcase guest-addition .iso? Obviously I'll have to go though this process again (after making a snapshot...), but if anybody has any idea of why this happened, I would welcome any thoughts you have. Right now, Archlinux host running 5.10.3 and Arch guest running 5.9.14 and all is happy again with 1.1.16 patched for 5.10. -- David C. Rankin, J.D.,P.E. _______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe