Crash Report
-
- Posts: 9
- Joined: 5. Nov 2015, 19:35
Crash Report
I turned the monitor on this morning and was welcomed to a pop-up window that Virtualbox has crashed and I was suppose to report it.
Where do I send the log file and the image?
Thanks in advance.
Where do I send the log file and the image?
Thanks in advance.
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Crash Report
Here would be the proper place to start.
Post the report and the guests log file ( as an attachment ) that was produced during this event.
Post the report and the guests log file ( as an attachment ) that was produced during this event.
-
- Posts: 9
- Joined: 5. Nov 2015, 19:35
Re: Crash Report
Cant attach the file getting an error The file is too big, maximum allowed size is 128 KiB.Perryg wrote:Here would be the proper place to start.
Post the report and the guests log file ( as an attachment ) that was produced during this event.
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Crash Report
Even compressed?
-
- Posts: 9
- Joined: 5. Nov 2015, 19:35
Re: Crash Report
Perryg wrote:Even compressed?
Never seen a forums with so low of upload limits.....
- Attachments
-
- VBox.log.tar.gz
- (79.77 KiB) Downloaded 3 times
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Crash Report
1135MB - 768MB - 128MB = 239MB remaining. Assuming that nothing else was loaded on the host this might get by but you are critically low on available memory.
- 00:00:06.056110 Host RAM: 1749MB total, 1135MB available
00:00:06.690975 RamSize <integer> = 0x0000000030000000 (805 306 368, 768 MB)
00:00:06.692891 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)
- 00:00:06.690952 NumCPUs <integer> = 0x0000000000000002 (2)
00:00:07.523328 Physical host cores: 2
- 13:44:14.124904 !! Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)
-
- Posts: 9
- Joined: 5. Nov 2015, 19:35
Re: Crash Report
On thanks, I had left firefox and Nemo running.Perryg wrote:1135MB - 768MB - 128MB = 239MB remaining. Assuming that nothing else was loaded on the host this might get by but you are critically low on available memory.
Assigning all of the host cores to the guest is never a good idea. It can cause issues like what you are having.
- 00:00:06.056110 Host RAM: 1749MB total, 1135MB available
00:00:06.690975 RamSize <integer> = 0x0000000030000000 (805 306 368, 768 MB)
00:00:06.692891 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)
- 00:00:06.690952 NumCPUs <integer> = 0x0000000000000002 (2)
00:00:07.523328 Physical host cores: 2Another thing to watch out for is power saving features on the host and the guest. These have been know to not play well in a virtual environment.
- 13:44:14.124904 !! Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)
I will set the CPU to 1 I might seek out more ram for this machine but its quite old might end up using a different computer for the Virtualbox thing.
If I move it to my other computer that has a AMD 4 core 2.0ghz i should not assign all 4 CPU's ? This box has 16 GB ram.
I thought I had all the power saving things turned off I will recheck.
Thanks for the help.
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Crash Report
Rule of thumb is to allocate no more than half of the available cores ( not to be confused with threads ) but at the very least leave one core for the host. The => part from the host side is what is the host going to be doing. If it is to stay idle then you can get away with only one core reserved for the host. Keep in mind that the host side of VirtualBox resides and operates in the host using the reserved core too.
-
- Posts: 9
- Joined: 5. Nov 2015, 19:35
Re: Crash Report
Ok thanks so much for the info.Perryg wrote:Rule of thumb is to allocate no more than half of the available cores ( not to be confused with threads ) but at the very least leave one core for the host. The => part from the host side is what is the host going to be doing. If it is to stay idle then you can get away with only one core reserved for the host. Keep in mind that the host side of VirtualBox resides and operates in the host using the reserved core too.
On this machine, the one that crashed...
I went through some old hardware a friend gave me and found two gig memory sticks that work in this PC so now it has 4 gig,
I went back into the Virtualbox settings for the machine I was running and switched the memory to 2048 and the CPU to 1
I will give it another try before I abandon.
On other machine, the 4 core, is their a way to test what the demands of the VM are while its in use maybe it only needs to be using only 1 core?
Thanks again.
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Crash Report
I rarely assign more than two cores to a guest although I have 12 available. The most I have ever used was 4 and those guests are for rendering video or compiling.
-
- Posts: 9
- Joined: 5. Nov 2015, 19:35
Re: Crash Report
Thanks that's great to know I switched mine to 1 CPU and set the ram to 2048 its running along at 986 mib should I leave it at 2048? Doubling the ram from 2 gig to 4 gig seems to have made a huge difference, this all works out I will upgrade the whole computer..Perryg wrote:I rarely assign more than two cores to a guest although I have 12 available. The most I have ever used was 4 and those guests are for rendering video or compiling.
Thanks.