I hope this message finds you well. I am writing to report an issue I've encountered with my VM running on our Linux host. The problem is that the VM is going into an "aborted" state intermittently, and I'm seeking assistance to resolve this issue.
I have attached the log file of the recently crashed/aborted VM.
VM Going into Aborted Mode on Linux Host
-
Sarhan Aashir
- Posts: 1
- Joined: 12. Sep 2023, 08:11
VM Going into Aborted Mode on Linux Host
- Attachments
-
neir-web-2023-09-11-13-38-43.log- (79.38 KiB) Downloaded 8 times
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: VM Going into Aborted Mode on Linux Host
Not a "Using VirtualBox" question. Topic moved to "Linux Hosts".
I would start with the fact that you are close to over-allocating RAM (too close for stability). You can only give a VM resources that are not already in use.
On the other hand you have paid no attention to graphics RAM: a desktop OS will need more than 16MB. I would max this out (128MB).
Please note that allocating idle CPU cores to the VM will make it run slower. Make sure the additional cores are actually needed. Many of us find that 2 cores is nearly always best unless you're doing lengthy batch compiles.
I would start with the fact that you are close to over-allocating RAM (too close for stability). You can only give a VM resources that are not already in use.
I would reduce the VM's RAM allocation to 8192MB.00:00:00.221439 Host RAM: 32093MB (31.3GB) total, 12234MB (11.9GB) available
...
00:00:00.769293 RamSize <integer> = 0x00000002ef800000 (12 608 077 824, 11.7 GiB)
On the other hand you have paid no attention to graphics RAM: a desktop OS will need more than 16MB. I would max this out (128MB).
Please note that allocating idle CPU cores to the VM will make it run slower. Make sure the additional cores are actually needed. Many of us find that 2 cores is nearly always best unless you're doing lengthy batch compiles.