i’m using Oracle VM VirtualBox Manager 4.3.26 r98988
my host is Linux Opensuse13.2 64bit gnome
linux.site 3.16.7-21-desktop #1 SMP PREEMPT Tue Apr 14 07:11:37 UTC 2015 (93c1539) x86_64
i have also tried opensuse default virtualbox with the same result
after analysing the kernel panic log by increasing the ram from the default 512mb to 1024mb i was able to boot the system and right now i’m installing which me luck
so thats my solution i hope it helps …
this topic explains how to redirect the Linux guest kernel console to a serial port / file https://www.virtualbox.org/wiki/Serial_redirect
i don’t know if i sholud report this as a bug in the oracle virtualbox bugtracker or not
I assume you’re talking about the RAM allocated to the Guest (There is also a setting somewhere for overall RAM allocation to the entire app but in VBox that’s hidden and hard to find).
First, my SOP is to hardly ever use a recommended default setting. I think carefully about the disk requirements as well as the RAM to be allocated. Note that allocating CPU virtual cores will rarely have any kind of effect because of how practically all modern OS work. IMO multiple CPU cores are useful only if you are running an app that that can be specially configured but even then there is no affinity to real CPU cores so it’s questionable what can be achieved.
My general guideline for recommended Guest RAM
No Desktop, ie running “text mode” and likely running a single LOB app… 512-716MB. At most 1024MB.
The closest I come to running a Gnome Desktop on openSUSE is to run XFCE (which installs Gnome apps). I would guess that if you’re running Gnome Desktop proper, you should add another 512-1024MB at least to what I recommend for XFCE.
The above configurations will typically support no latency high performance. Of course if you’re going to run an unusually high load app, the configuration may need to be changed. So far I have found the above applies to VMware, VBox and KVM but probably applies to practically any/all paravirtualization with very little running on the HostOS.
As for reporting to a bugtracker…
Although this is a very common issue in many virtualization managers (not necessarily recommending appropriate defaults), IMO most people will look upon it as a pitta. As I described above, the default probably depends on what kind of Desktop is installed and that’s going to be a personal preference.
