I haven’t touched anything related to VMs in ages, and haven’t used them in a couple weeks.
Now, after an upgrade (which I assume is the cause), all I get from any VM is
The VM session was aborted.
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
I am fond of maximally non-specific error messages…
I switched from dkms (I have linux, -lts and -zen) to modules-arch just in case, to no avail.
I have no issue on vbox with the latest updates. I am not using zen but i don’t believe that would be an issue. Did you reboot after doing the updates? Mine is reporting the same info.
That was automatic for me. So i never tried v-box before the update so probably yes that is the OP’s issue. I just assume that they would already have the update as i did. But maybe they haven’t updated yet.
Of course, I rebooted multiple times (once after each operation).
I have zen, but, like lts, it’s just a backup in case of breakage (that never happened), I don’t run it day to day.
I downloaded the new Extension Pack, and suddenly it works. Thanks @kwg !
Which raises the subsidiary question, how could that upgrade have been automatic ? I don’t see a corresponding package on
If I remember correctly, the EnOS’ team used to add the virtualbox-ext-oracle to EnOS’ repo before, so it got automatically updated with the rest of the system. They dropped it some time ago.
True. We found out that having it in our repo may not be OK with the usage terms, so we dropped it.
However, it is easy to install or update using e.g. yay or paru.
I now have it installed from the AUR and (after a quick resolution for the conflict with the manually installed version) everything works nicely. Problem fully solved.
Thank you all for the kind help, and no thanks at all to VBox for using such an uninformative error message (NS_ERROR_FAILURE) for what should be an obvious versions mismatch.