[Fixed] "memory could not be read" when saving VM state after upgrade to VirtualBox 6.0.10
Posted: 26. Jul 2019, 13:03
Recently I upgraded from VirtualBox 5.2.30 to VirtualBox 6.0.10 (on Windows 10 host)
I have Ubuntu 16.04 and Ubuntu 18.04 virtual machines.
After upgrade when I chose to save VM's state (instead of shutting down the guest system) the save progress goes to 100% and then message window with this text appears:
Before upgrade I was able to save VM's state without any issues.
Is this known problem? Are there any fixes?
I have Ubuntu 16.04 and Ubuntu 18.04 virtual machines.
After upgrade when I chose to save VM's state (instead of shutting down the guest system) the save progress goes to 100% and then message window with this text appears:
After that VM's state in VirtualBox Manger is "aborted".---------------------------
VirtualBoxVM.exe - Application Error
---------------------------
The instruction at 0x00007FFA5B81CB3E referenced memory at 0x0000000000002DD0. The memory could not be read.
Click on OK to terminate the program
Click on CANCEL to debug the program
---------------------------
OK Cancel
---------------------------
Before upgrade I was able to save VM's state without any issues.
Is this known problem? Are there any fixes?