I had successfully installed Oracle 11.02.03 on a Virtual Machine, and then the Virtual Machine crashed
The error in the Log file is Guru Meditation -2701 (VERR_VMM_RING0_ASSERTION)
Host Box
Operating System: Solaris 10 Generic_150401-03
64 Bit Operating System, Memory: 32763 MB
Virtual Box Version: 4.3.4r91027
Virtual Box Extension is installed
Guest Box
Operating System: Solaris 11, 11.1
Memory: 12000 MB
Guest Additions Installed
The log file was too big for the forum even compressed, so I split it in two pieces and compress the pieces
Oracle 11 database crashes Virtual Box
Oracle 11 database crashes Virtual Box
- Attachments
-
- VBox3ab.gz
- part 2 of 2
- (56.17 KiB) Downloaded 34 times
-
- VBox3aa.gz
- Part 1 of 2
- (127.7 KiB) Downloaded 39 times
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Oracle 11 database crashes Virtual Box
Same issue!
You proved this to yourself in your last string of posts. If it will not install at >9GB why would it run at >9GB?
Try putting the memory at your last known good and wait for the ticket to be resolved.
viewtopic.php?f=11&t=59965&p=279066#p279156
You proved this to yourself in your last string of posts. If it will not install at >9GB why would it run at >9GB?
Try putting the memory at your last known good and wait for the ticket to be resolved.
viewtopic.php?f=11&t=59965&p=279066#p279156
Re: Oracle 11 database crashes Virtual Box
This time it installed at 12000 MB, and ran for a couple of hours. It crashed after the installation was complete.. I was using a host with a different operating system and a different version of Virtual Box so it might be caused by a different problem.
Re: Oracle 11 database crashes Virtual Box
I had a similar case which was entered as bug 12676, where the Virtual Box crashed during installation.
THe fix recommended in the bug tracker was to run the following command for the Virtual Machine
VBoxManage setextradata VM_NAME "VBoxInternal/MM/CanUseLargerHeap" 1
I tried doing that for this Virtual Machine before starting it up. I've been running oracle for 2+ days so far and it is still up. YMMV, as I am not doing anything with the database just leaving it on waiting on a crash.
THe fix recommended in the bug tracker was to run the following command for the Virtual Machine
VBoxManage setextradata VM_NAME "VBoxInternal/MM/CanUseLargerHeap" 1
I tried doing that for this Virtual Machine before starting it up. I've been running oracle for 2+ days so far and it is still up. YMMV, as I am not doing anything with the database just leaving it on waiting on a crash.