Error after running VM once.
v1.6 still does it with 4GB RAM...
00:00:10.864 SUP: Loaded VMMR0.r0 (/Applications/VirtualBox.app/Contents/MacOS/../Resources/VirtualBoxVM.app/Contents/MacOS/VMMR0.r0) at 0x7ab4b060 - ModuleInit at 7ab564b0 and ModuleTerm at 7ab564f0
00:00:10.865 SUP: VMMR0EntryEx located at 7ab56df0, VMMR0EntryFast at 7ab567f0 and VMMR0EntryInt at 7ab56570
00:00:10.866 ERROR [COM]: aRC=0x80004005 aIID={d5a1cbda-f5d7-4824-9afe-d640c94c7dcf} aComponent={Console} aText={VM creation failed (GVMM).
00:00:10.866 VBox status code: -32 (VERR_INTERNAL_ERROR)} aWarning=false, preserve=false
00:00:10.875 Power up failed (vrc=VERR_INTERNAL_ERROR, hrc=0x80004005)
May 5 15:31:25 igMBP kernel[0]: VBoxDrvDarwinOpen: pid=8170 'VirtualBoxVM' pSession=0x6d6e410 rc=0
May 5 15:31:25 igMBP kernel[0]: SUPR0GipMap: returns 0 *pHCPhysGip=3b985000 *ppGip=0x2a5000 GipMapObjR3
May 5 15:31:26 igMBP kernel[0]: GVMMR0CreateVM: failed, rc=-32
00:00:10.864 SUP: Loaded VMMR0.r0 (/Applications/VirtualBox.app/Contents/MacOS/../Resources/VirtualBoxVM.app/Contents/MacOS/VMMR0.r0) at 0x7ab4b060 - ModuleInit at 7ab564b0 and ModuleTerm at 7ab564f0
00:00:10.865 SUP: VMMR0EntryEx located at 7ab56df0, VMMR0EntryFast at 7ab567f0 and VMMR0EntryInt at 7ab56570
00:00:10.866 ERROR [COM]: aRC=0x80004005 aIID={d5a1cbda-f5d7-4824-9afe-d640c94c7dcf} aComponent={Console} aText={VM creation failed (GVMM).
00:00:10.866 VBox status code: -32 (VERR_INTERNAL_ERROR)} aWarning=false, preserve=false
00:00:10.875 Power up failed (vrc=VERR_INTERNAL_ERROR, hrc=0x80004005)
May 5 15:31:25 igMBP kernel[0]: VBoxDrvDarwinOpen: pid=8170 'VirtualBoxVM' pSession=0x6d6e410 rc=0
May 5 15:31:25 igMBP kernel[0]: SUPR0GipMap: returns 0 *pHCPhysGip=3b985000 *ppGip=0x2a5000 GipMapObjR3
May 5 15:31:26 igMBP kernel[0]: GVMMR0CreateVM: failed, rc=-32
-
- Posts: 6
- Joined: 20. Apr 2008, 21:28
That would be great! I'm currently running 5GB of RAM, which is less than 1/3 of what I eventually expect to install. VirtualBox is still happily humming along on my 2GB Mini.bird wrote:The VERR_INTERNAL_ERROR is caused by having 4>GB of RAM and bad luck. This error might crop up at installation time as well as VM startup time. It will be fixed in 1.6.2.
Thanks bird!
Bucky
-
- Posts: 6
- Joined: 20. Apr 2008, 21:28
bjvetter,
Since this seems to be the "...on Mac OS X Hosts" topic area, you may not get your answer here.
I've also got Virtual box on a Kubuntu Linux installation that runs well. It has only 2GB of RAM though so that's no help. A quick search on the forums didn't turn up any >2GB RAM issues, but that doesn't mean that there aren't any.
I use my additional RAM more than I use an alternate OS on my primary machine so . . . it shouldn't be difficult to guess what I've done here.
Bucky
Since this seems to be the "...on Mac OS X Hosts" topic area, you may not get your answer here.
I've also got Virtual box on a Kubuntu Linux installation that runs well. It has only 2GB of RAM though so that's no help. A quick search on the forums didn't turn up any >2GB RAM issues, but that doesn't mean that there aren't any.
I use my additional RAM more than I use an alternate OS on my primary machine so . . . it shouldn't be difficult to guess what I've done here.
Bucky
-
- Posts: 6
- Joined: 20. Apr 2008, 21:28
Yes, the version 1.6.2 seems to have also solved the problem of my MacPro having too much memory (5 GB). I was able to start up the Win2K virtual machine that I had created under 1.5.n. I haven't stress tested VirtualBox in this situation, but the initial problem seems to have been overcome.
A RedHat 9 VB didn't automagically start up, but then I can't say that it was properly installed in the first place.
Kudos to the VB team!
Bucky
A RedHat 9 VB didn't automagically start up, but then I can't say that it was properly installed in the first place.
Kudos to the VB team!
Bucky