update 10 supported?

[stevegszabo]

I'm able to boot off the update 9 iso without any issues however when I use the same vm to boot off update 10 it hangs.

I get to the SunOS Release banner then it hangs.

Has anyone booted update 10 ?

[Ramshankar]

Tried bumping the VM's RAM limit?

[DAGwyn]

I found the same behavior when attempting to install the latest Solaris 10 download from Oracle into VB 4.1.4 on a 64-bit Windows 7 host: Immediately after the OS banner ("Generic" etc.) it hangs, before what should have been "configuring devices". Installing from the update 9 disk worked fine.
I suspect Oracle doesn't test at least its own products for compatibility before releasing them.

[apljavaman]

Seeing the same behavior. Running VirtualBox 4.1.4, hangs on the initial boot screen for Update 10, both 32 and 64 bit.

Update: Try changing the controller from SATA to SAS. Once I did this, it continued to boot. Must be a bad SATA controller module.

[Ramshankar]

Well please upload a VBox.log for the hanging VM session. Without knowing things like how much RAM was assigned and other VM settings, we can't really say much.

[Mandi]

Hi

I have had similar problems with update 10.
Running VirtualBox 4.0.14 on Solaris 10 update 9, the VM hangs on the initial boot screen.

I used the default VM settings that you get when you select "Solaris 10 10/09 and later (64 bit)".
I tried adjusting some of the VM settings like nested paging and even increasing the RAM to 1024MB, but it made no difference.
As a last roll of the dice, I increased the RAM to 2048MB and that solved the problem.

Attached is a logs for one of the "hangs".

[Ramshankar]

Same issue as https://www.virtualbox.org/ticket/9805

This is a Solaris 10 U10 bug which hangs the VM instead of reporting insufficient memory, not much VirtualBox can do other than increasing the default VM RAM limit for the guest OS type (which we will do, if it's not checked in already).

TL;DR: Use 1.5 GB or more of RAM for the S10 U10 VM.

[jhelling]

Hi,
VBOX 4.1.20: Had the same problem, but with memory set at 2048MB.
Increased to 3029MB and than the config succeeded and passed the detecting devices phase.
New to solaris ... so can't give further info ... yet