i386 VMs abort with NS_ERROR_FAILURE (0x80004005) after upgrading host to disco

[Olivier Tilloy]

I recently upgraded my laptop from cosmic to disco. After finishing the upgrade, my Ubuntu i386 virtual machines (trusty, xenial, bionic, cosmic) all fail to resume, with error code NS_ERROR_FAILURE (0x80004005). x86-64 virtual machines are not affected.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: virtualbox 6.0.4-dfsg-7
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 18 10:32:27 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-07-02 (988 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: virtualbox
UpgradeStatus: Upgraded to disco on 2019-03-16 (1 days ago)

[Gianfranco Costamagna (costamagnagianfranco)]

Hello, did you try to shutdown and save again?
from 5.x to 6.x the saved store format has changed, this is an incompatible change that is making the restore fail on some cases (it has been fixed in 6.0.4, but maybe there are a few more cases)

[Olivier Tilloy (osomon)]

That works (forgetting the current state of the snapshot, effectively rebooting the VM).
However after taking a new, updated snapshot and shutting down the VM, trying to restore it exhibits the same issue again.

[Gianfranco Costamagna (costamagnagianfranco)]

@osomon, can you please check if you suffer from this issue?
https://www.virtualbox.org/ticket/18263

[Olivier Tilloy (osomon)]

That looks more like https://www.virtualbox.org/ticket/18331.
Attaching my log file.

[Olivier Tilloy (osomon)]

This appears to be fixed, somehow, despite the fact that virtualbox hasn't been updated since I reported the issue.

There was a kernel update on 2019-03-31 (from 5.0.0.7.8 to 5.0.0.8.9), maybe related?

Closing for now, will re-open if the issue surfaces again.

[Olivier Tilloy (osomon)]

Sigh, it's just done it again on my bionic i386 VM.

[Gianfranco Costamagna (costamagnagianfranco)]

still an issue with newer vbox version?

[Olivier Tilloy (osomon)]

I haven't seen this issue for a while now (I'd say at least 3 months). I've been running eoan on my laptop since early in the development cycle, and I have used and regularly upgraded several i386 VMs without problems.