Guest crash - probably host related
-
- Posts: 31
- Joined: 28. Nov 2018, 01:16
- Primary OS: Linux other
- VBox Version: OSE other
- Guest OSses: Debian, Devuan, OpenBSD, Windows
Guest crash - probably host related
Good morning everybody,
I'm having issue with a guest crashing on my systems - the first time fore almost a year, until then everybody went well. Here's my setup:
HP DL380 G6, 24G RAM, 8 physical cores, hyperthreading enables (should be off, I know, but it's a private system)
OS: Devuan Ascii
Virtualbox 5.2.12 r122591
Guests:
1. Debian, 4 cores, , 12G RAM (the workhorse)
2. Windows 7, 4 cores, 4G RAM
3. OpenBSD, 1 core, 1G RAM
4. Devuan, 1core, 1G RAM
5. Devuan, 2 cores, 4G RAM used as DMS
6. OpenBSD, 1 core, 1G RAM, TOR exit node
The actual work is being done on no. 1 and 3 4 (not more that 4 users at a time). As far as my monitoring shows, neither the host nor one of the guest machines is under uncommon load.
When I added machine no. 6 (a TOR exit node) yesterday, no. 1 crashed during install. When I later rebooted the host, all machines came up smoothly but no. 1 apparently failed to start or crashed after it. In both cases, I could start it manually without trouble.
The logfiles are available, but to be honest I wouldn't know what to look for. I see no obvious error in the log. Could someone point me to where to begin?
TIA
Matthias
I'm having issue with a guest crashing on my systems - the first time fore almost a year, until then everybody went well. Here's my setup:
HP DL380 G6, 24G RAM, 8 physical cores, hyperthreading enables (should be off, I know, but it's a private system)
OS: Devuan Ascii
Virtualbox 5.2.12 r122591
Guests:
1. Debian, 4 cores, , 12G RAM (the workhorse)
2. Windows 7, 4 cores, 4G RAM
3. OpenBSD, 1 core, 1G RAM
4. Devuan, 1core, 1G RAM
5. Devuan, 2 cores, 4G RAM used as DMS
6. OpenBSD, 1 core, 1G RAM, TOR exit node
The actual work is being done on no. 1 and 3 4 (not more that 4 users at a time). As far as my monitoring shows, neither the host nor one of the guest machines is under uncommon load.
When I added machine no. 6 (a TOR exit node) yesterday, no. 1 crashed during install. When I later rebooted the host, all machines came up smoothly but no. 1 apparently failed to start or crashed after it. In both cases, I could start it manually without trouble.
The logfiles are available, but to be honest I wouldn't know what to look for. I see no obvious error in the log. Could someone point me to where to begin?
TIA
Matthias
Last edited by mksmr on 22. Feb 2020, 18:38, edited 1 time in total.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Guest crash - probably host related
Yes, let us take a look.mksmr wrote:I see no obvious error in the log. Could someone point me to where to begin?
Get all your guests ready to start from cold boot, none of them should have a saved-sate. Run your whole startup sequence until you see the problem happen, then shut down the guests from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.
Please zip and post the one failing guest's vbox.log, using the forum's Upload Attachment tab.
Also, please explain this a little more:
The first sentence sounds like guest #1 exists already, but the second sentence sounds like guest #1 is being built fresh?mksmr wrote:The actual work is being done on no. 1 and 3 (not more that 4 users at a time)....When I added machine no. 6 (a TOR exit node) yesterday, no. 1 crashed during install.
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Guest crash - probably host related
What does your monitoring show regarding host memory usage? You assigned 23 GB RAM to your VMs in total, and VirtualBox and the host OS will also need some host memory ...mksmr wrote:As far as my monitoring shows, neither the host nor one of the guest machines is under uncommon load.
-
- Posts: 31
- Joined: 28. Nov 2018, 01:16
- Primary OS: Linux other
- VBox Version: OSE other
- Guest OSses: Debian, Devuan, OpenBSD, Windows
Re: Guest crash - probably host related
Will zip and upload the logs asap.
No. 1 crashed while I was installing no. 6. So no. 1 has been there all the time.
Memory usage on the host system is high (unsurprisingly) and free RAM drops as low as 1GB, but the system never attempts to swap. I'd rather expect that it would at least attempt that.
No. 1 crashed while I was installing no. 6. So no. 1 has been there all the time.
Memory usage on the host system is high (unsurprisingly) and free RAM drops as low as 1GB, but the system never attempts to swap. I'd rather expect that it would at least attempt that.
-
- Posts: 31
- Joined: 28. Nov 2018, 01:16
- Primary OS: Linux other
- VBox Version: OSE other
- Guest OSses: Debian, Devuan, OpenBSD, Windows
Re: Guest crash - probably host related
Reducing RAM on guest no. 1 from 12 to 8G now, just to make sure.
-
- Posts: 31
- Joined: 28. Nov 2018, 01:16
- Primary OS: Linux other
- VBox Version: OSE other
- Guest OSses: Debian, Devuan, OpenBSD, Windows
Re: Guest crash - probably host related
gzipped logfiles below
- Attachments
-
- VBox.log.2.gz
- (29.71 KiB) Downloaded 4 times
-
- VBox.log.1.gz
- (17.03 KiB) Downloaded 5 times
-
- VBox.log.gz
- (17.53 KiB) Downloaded 5 times
-
- Posts: 31
- Joined: 28. Nov 2018, 01:16
- Primary OS: Linux other
- VBox Version: OSE other
- Guest OSses: Debian, Devuan, OpenBSD, Windows
Re: Guest crash - probably host related
...and the fourth (could only upload 3 per post)
- Attachments
-
- VBox.log.3.gz
- (31.39 KiB) Downloaded 5 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Guest crash - probably host related
Please confirm that you ran the whole startup sequence again and that guest #1 died again while you were working on guest #6. If this is true, please identify which of the four log zips you posted is the one log of the failing guest #1.scottgus1 wrote:Run your whole startup sequence until you see the problem happen....Please zip and post the one failing guest's vbox.log, using the forum's Upload Attachment tab.
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Guest crash - probably host related
Start with the following lines in all of your VBox.log files:mksmr wrote:The logfiles are available, but to be honest I wouldn't know what to look for.
VBox.log file wrote:00:00:00.211168 Host RAM: 24101MB (23.5GB) total, 13140MB (12.8 GB) available 00:00:00.886535 RamSize <integer> = 0x0000000321000000 (13 438 550 016, 12 816 MB, 12.5 GB) 00:00:00.887322 VRamSize <integer> = 0x0000000010000000 (268 435 456, 256 MB)
-
- Posts: 31
- Joined: 28. Nov 2018, 01:16
- Primary OS: Linux other
- VBox Version: OSE other
- Guest OSses: Debian, Devuan, OpenBSD, Windows
Re: Guest crash - probably host related
Back after a while... and I have another crash (this time it's a Windows 7 guest, but it shouldn't matter).
Here's my setup:
HP DL 380G6
8 cores, multithreading enabled (I know... but it's an entirely private system)
64G RAM
Host OS: Devuan Ascii 2
Virtualbox 6.1.4 r136177 (Qt5.7.1)
Virtualbox Extension Pack as above present
Running 7 virtual machines, configured with 7 cores and 18GB RAM total
The crashed machine is Windows 7 (64bit)
8GB RAM
1 CPU, VT-x/AMD-V, Nested Paging, PAE/NX, Hyper-V virtualization
This used to run for about a year on a weaker host (DL380G6, too) with Virtualbox 5.x without any trouble.
Logfile is attached.
Any help with this would be greatly appreciated.
Matthias
Edit: Probably this one applies:
https://www.virtualbox.org/manual/ch03. ... alsettings
Here's my setup:
HP DL 380G6
8 cores, multithreading enabled (I know... but it's an entirely private system)
64G RAM
Host OS: Devuan Ascii 2
Virtualbox 6.1.4 r136177 (Qt5.7.1)
Virtualbox Extension Pack as above present
Running 7 virtual machines, configured with 7 cores and 18GB RAM total
The crashed machine is Windows 7 (64bit)
8GB RAM
1 CPU, VT-x/AMD-V, Nested Paging, PAE/NX, Hyper-V virtualization
This used to run for about a year on a weaker host (DL380G6, too) with Virtualbox 5.x without any trouble.
Logfile is attached.
Any help with this would be greatly appreciated.
Matthias
Edit: Probably this one applies:
https://www.virtualbox.org/manual/ch03. ... alsettings
The machine has eight physical cores, though, and the guests are using seven altogether. Does this line mean I cannot configure more than <number of physical cores> cores altogether, or <number of physical cores> per guest?You should not configure virtual machines to use more CPU cores than are available physically. This includes real cores, with no hyperthreads.
- Attachments
-
- VBox.log.gz
- most recent logfile
- (33.07 KiB) Downloaded 5 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Guest crash - probably host related
We never resolved the original situation and forum rules are "One issue per thread". If you want to let the old issue go without resolution, please start a new topic.
-
- Posts: 31
- Joined: 28. Nov 2018, 01:16
- Primary OS: Linux other
- VBox Version: OSE other
- Guest OSses: Debian, Devuan, OpenBSD, Windows
Re: Guest crash - probably host related
OK, let's drop this because the host will become obsolete soon and the problem never reappeared. The problem seems to be related, though.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Guest crash - probably host related
That sounds fine! Thanks for the update.