Critical Error on Hitting Start

Discussions related to using VirtualBox on Linux hosts.
Post Reply
Kalraken
Posts: 1
Joined: 22. Feb 2016, 05:04

Critical Error on Hitting Start

Post by Kalraken »

on Debian 8

including log
Attachments
VBoxlog.rar
(135.35 KiB) Downloaded 6 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Critical Error on Hitting Start

Post by mpack »

There is no need to provide four logs. Just one that exhibits the problem will do. Replace the 3 redundant logs with a more complete description of the problem.
VBox.log wrote: 00:00:10.367358 AssertLogRel /home/vbox/vbox-5.0.14/src/VBox/VMM/VMMR3/PGMPhys.cpp(4367) int PGMR3PhysAllocateHandyPages(PVM): RT_SUCCESS(rc)
00:00:10.367377 8/128: idPage=0x2c0236 HCPhysGCPhys=0000000c2468c000 rc=VERR_NO_MEMORY
00:00:10.367398 AssertLogRel /home/vbox/vbox-5.0.14/src/VBox/VMM/VMMR3/PGMPhys.cpp(4367) int PGMR3PhysAllocateHandyPages(PVM): RT_SUCCESS(rc)
00:00:10.367401 8/128: idPage=0x2c02ae HCPhysGCPhys=0000000c24704000 rc=VERR_NO_MEMORY
00:00:10.367419 AssertLogRel /home/vbox/vbox-5.0.14/src/VBox/VMM/VMMR3/PGMPhys.cpp(4367) int PGMR3PhysAllocateHandyPages(PVM): RT_SUCCESS(rc)
00:00:10.367421 8/128: idPage=0x2c0326 HCPhysGCPhys=0000000c2477c000 rc=VERR_NO_MEMORY
00:00:10.367497 AssertLogRel /home/vbox/vbox-5.0.14/src/VBox/VMM/VMMR3/PGMPhys.cpp(4367) int PGMR3PhysAllocateHandyPages(PVM): RT_SUCCESS(rc)
00:00:10.367500 8/128: idPage=0x2c039e HCPhysGCPhys=0000000c247f4000 rc=VERR_NO_MEMORY
00:00:10.367526 AssertLogRel /home/vbox/vbox-5.0.14/src/VBox/VMM/VMMR3/PGMPhys.cpp(4367) int PGMR3PhysAllocateHandyPages(PVM): RT_SUCCESS(rc)
00:00:10.367529 28/128: idPage=0x2c0416 HCPhysGCPhys=0000000c30c71000 rc=VERR_NO_MEMORY
00:00:10.367556 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:10.367556 !!
00:00:10.367557 !! Guru Meditation -8 (VERR_NO_MEMORY)
00:00:10.367557 !!
00:00:10.367573 !!
00:00:10.367574 !! {mappings, <NULL>}
00:00:10.367574 !!
00:00:10.367581
You seem to be having a problem allocating kernel memory. I have no idea why, I'm not a Linux user. Some kind of permission problem? Was this VM previously working on the same host?
Post Reply