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.
** Changed in: virtualbox (Ubuntu)
Status: Incomplete => Fix Released
-
still an issue with newer vbox version?
** Changed in: virtualbox (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820575
Title:
i386 VMs abort with NS_ERROR
Sigh, it's just done it again on my bionic i386 VM.
** Changed in: virtualbox (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820575
Title:
i386 VMs abort with
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.
** Changed in: virtualbox (Ubuntu)
That looks more like https://www.virtualbox.org/ticket/18331.
Attaching my log file.
** Bug watch added: Virtualbox Trac #18331
http://www.virtualbox.org/ticket/18331
** Attachment added: "xenial i386-2019-03-20-17-35-52.log"
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/182057
@osomon, can you please check if you suffer from this issue?
https://www.virtualbox.org/ticket/18263
** Bug watch added: Virtualbox Trac #18263
http://www.virtualbox.org/ticket/18263
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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.
** Changed in: virtualbox (Ubuntu)
Status: Incomplete => New
--
You receive
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)
** Changed in: virtualbox (Ubuntu)
Status: New
