[Fixed] "memory could not be read" when saving VM state after upgrade to VirtualBox 6.0.10

Discussions about using Linux guests in VirtualBox.

[Fixed] "memory could not be read" when saving VM state after upgrade to VirtualBox 6.0.10

Postby igorsol » 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:
---------------------------
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
---------------------------

After that VM's state in VirtualBox Manger is "aborted".
Before upgrade I was able to save VM's state without any issues.
Is this known problem? Are there any fixes?
Last edited by socratis on 19. Sep 2019, 15:54, edited 1 time in total.
Reason: Marked as [Fixed].
igorsol
 
Posts: 3
Joined: 26. Jul 2019, 12:51

Re: "memory could not be read" when saving VM state after upgrade to VirtualBox 6.0.10

Postby socratis » 27. Jul 2019, 08:41

We need to see a complete VBox.log, from a complete VM run, where the problem occurs:
  • Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
  • With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
  • Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.
Image
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 25828
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: "memory could not be read" when saving VM state after upgrade to VirtualBox 6.0.10

Postby igorsol » 29. Jul 2019, 12:04

Thank you for the response. The attached file is the requested log.
Attachments
Ubuntu (64-bit)-2019-07-29-12-58-19.log.zip
requested log
(34.05 KiB) Downloaded 12 times
igorsol
 
Posts: 3
Joined: 26. Jul 2019, 12:51

Re: "memory could not be read" when saving VM state after upgrade to VirtualBox 6.0.10

Postby igorsol » 19. Sep 2019, 14:27

The issue has disappeared after upgrade to VirtualBox 6.0.12
igorsol
 
Posts: 3
Joined: 26. Jul 2019, 12:51

Re: "memory could not be read" when saving VM state after upgrade to VirtualBox 6.0.10

Postby socratis » 19. Sep 2019, 15:54

igorsol,
Thank you for the feedback, glad everything is back to normal! Marking as [Fixed].
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 25828
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5


Return to Linux Guests

Who is online

Users browsing this forum: No registered users and 14 guests