Page 1 of 1

Guest Debian 5 crashes (GuruMeditation) Vbox 5.1.26 on Debian 8

Posted: 2. Aug 2017, 02:34
by KareemMahgoub
Hello All
I am getting GuruMeditation problem with guest Debian 5 running on host Debian 8 with VirtualBox 5.1.26. The problem happens every 1-2 days wthout specific reason and it is not related to load.
The log file attached.
Thanks

Re: Guest Debian 5 crashes (GuruMeditation) Vbox 5.1.26 on Debian 8

Posted: 2. Aug 2017, 12:42
by Perryg
Debian 5 ( lenny ) reached its end of life in Feb of 2012 and as such not much is done to keep it working. That said I would try enabling PAE in the guest settings and see if that makes a difference.

Re: Guest Debian 5 crashes (GuruMeditation) Vbox 5.1.26 on Debian 8

Posted: 2. Aug 2017, 15:29
by KareemMahgoub
Thanks perryg for looking into the case.
I know that lenny reached its end of life long time ago but I have an app running on it and I have the same setup on different HW and it doesn't show the same problem. Does the log show where the problem is happening? I mean is it related to memory, CPU, ...?
for enabling PAE, I have tried it and the results weren't promising as I was getting almost the same rate.
I will try it again and will send the log if you have time to check it
Thanks again

Re: Guest Debian 5 crashes (GuruMeditation) Vbox 5.1.26 on Debian 8

Posted: 2. Aug 2017, 15:36
by Perryg
Hard to say with out debugging enabled and seeing exactly what causes the assertion error. It looks like CPU calls but that may be a red herring. As you say running on different hardware does not show the problem which may point to the actual hardware being the real reason. VirtualBox tries to adjust R0-R3 code to accommodate the hardware age but it does not update all that much for older hardware or OSes. You might post the issue to the DEVs on bugtracker and see if they can find time to help with this.

Re: Guest Debian 5 crashes (GuruMeditation) Vbox 5.1.26 on Debian 8

Posted: 2. Aug 2017, 16:44
by KareemMahgoub
Thanks so much for your reply. I will try the following
1- Enabling PAE
2- Checking similar problem I have found on bugtracker "ticket number 10745"
3- Trying another HW
4- Opening a ticket if all the above didn't work.
I will post the results in case someone is facing a similar problem