virtualbox.org

Hello,

I'm running Ubuntu 20.04 on Windows 10 Pro 10.0.19041 Build 19041. Since i installed a Windows Update about a week ago i randomly encounter this guru meditation error. Just now it happened while I clicked out of the VM and back in and it just appeared again. It wont close either, i have to do that via the task manager.

Thanks in advance

That's a very unhappy VM you have there.

Trying to use RAM you don't have:

00:00:02.487952 Host RAM: 16315MB (15.9GB) total, 8323MB (8.1GB) available
...
00:00:02.763515 RamSize <integer> = 0x00000002c6a00000 (11 922 309 120, 11 370 MB, 11.1 GB)

Likewise, assigning 100% of available cores to the VM. What is the host OS supposed to run on?

00:00:02.763513 NumCPUs <integer> = 0x0000000000000006 (6)
...
00:00:03.498906 CPUM: Physical host cores: 6

Yes, I'm aware that your CPU has 12 threads, but threads are not cores. If they were then none of us would need more than 1 core, and we'd all use the cheaper threads option.

Finally, this particular error seems to be related to upgrading VirtualBox on the host, or upgrading the host OS, while the VM was suspended, invalidating the data in the SAV file. You need to right click the VM in the manager and discard the saved state.

Thank you for your reply.

I changed the ram to 4GB and the cores to 2. If you have better suggestions I would like to hear them. The "Discard Saved State..." button however is greyed out. What can I do about that?

The only time I have seen the Discard Saved State grayed out is if the selected machine does not have a saved state (ie it is shut down), or if no guest is selected.

ah, ok, that's what it means. Well, i properly shut the vm down before changing the ram and core settings. That should be enough, right?

my VM hasnt crashed yet, but it freezes every now and then, likely because of th less cores and ram.
The strange thing is that in the log file it states that I have only 8 GB of ram, but I have 16.
Any suggestions for better settings configurations or any other way to fix this?

As mpack described the Log didn't say you have a total of 8GB RAM it said you have about that amount available for the Guest, the rest was being used by whatever was going on in the Host. If you want/need more memory available for the guest than you would have to cut down on what the Host is using.

Hello,
I encountered a criritical errror again. The cores are still set to 2 and th VM still uses 4 GB RAM. Between my last post and today I tried to find some good settings that worked, but in the end I still ended up on these settings.
I also put another 8 GB of RAM into my computer, which were from a friend which he had left after he replaced his RAM.

The problem now is that the logfile ist too big to be attached to this post (VBox.log, 438 KB). Did I look up the wrong file?

Thank You for your time

Always zip logs before attaching them.

Alright, thank you. I've attached it to this reply.

Try discarding the saved state. I recommend that for the future you get into the habit of shutting down the VM after every session. With today's SSDs there are few good reasons to risk suspending the VM.

Ok, I'll do that. If I should get this error again anyways I'll post another reply here.

Thank You very much.

Another question that came to my mind. Could I safely assign more RAM to the Vm, now that I have an extra 8GB? Or would that still be too unstable?

Well, if the last log is typical then you could go to 6GB for the VM, but is there a good reason to do that? Is the guest OS struggling with only 4096MB RAM? In general you shouldn't give a VM more resources than it really needs. It's the host that's doing all the real work.

I'm using th VM to write Java Code and my IDE (IntelliJ Idea) was complaining about low memory.
If I happen to also have a web browser open it can be a little bit slow, but with bidirectional copy-paste I guess I could just have the IDE open.