virtualbox.org

Since i use VirtualBox 5.0.xx, i have some problem with my virtual machine.
Sometime, (often when i reboot a VM) the VM abort. I join the VBoxHardening.log in the topic.
No problem in VirtualBox 4.3.xx.
All the VM i use are in linux.

Thanks in advance for your reply.

You have provided the hardening log - why do you think the abort is related to hardening? If you don't have a good reason to believe that then I'd prefer to see the VBox.log file (zipped please).

Thks for your reply.

I have posted the VboxHardening.log because when the VM freeze after reboot (and abort), VboxHardening.log become bigger.
I join all the VBox.log of the day in the zipped file in that post.
If i have the problem today, I'll re-post the two log files.

I just have the problem. I send the two logs.

VBox.log wrote: 00:00:00.985974 Host RAM: 8130MB total, 4942MB available
...
00:00:01.365249 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 GB)
00:00:01.365474 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)

That is uncomfortably high RAM utilization. IMHO it invites instability. I would cut that to 2GB.

VBox.log wrote: 00:00:01.365246 NumCPUs <integer> = 0x0000000000000004 (4)
...
00:00:02.002169 CPUM: Physical host cores: 4

I guess you didn't read any of the advice that threads are not cores, and leaving the host with 0 cores for its exclusive use will not improve system performance. Again I would cut this in half: 2 cores to the guest.

VBox.log wrote: 03:08:08.901224 OHCI: Software reset
03:08:08.973395 TM: Switching TSC mode from 'RealTscOffset' to 'VirtTscEmulated'
03:08:08.978471 ACPI: Reset initiated by ACPI
03:08:08.978668 Changing the VM state from 'RUNNING' to 'RESETTING'

This is the only immediate issue I see in the log - and AFAICT it isn't a VirtualBox crash or bug, it's a reset initiated by an OS feature. What that would be I can't say. You might want to look at your power saving settings inside the guest.

I change the settings of ma VM:
- RAM 2Go
- 2 CPU

And some RAM on my PC

But still the same problem.

Here's my new logs.

Since virtualBox 5.0.10, I don't have any problem.