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 ?
update 10 supported?
-
- Posts: 1
- Joined: 20. Sep 2011, 17:03
- Primary OS: MS Windows XP
- VBox Version: OSE other
- Guest OSses: Solaris
-
- Oracle Corporation
- Posts: 793
- Joined: 7. Jan 2008, 16:17
-
- Posts: 3
- Joined: 12. Oct 2011, 06:36
- Primary OS: MS Windows 7
- VBox Version: OSE other
- Guest OSses: Solaris, Plan9, Ubuntu, Fedora
Re: update 10 supported?
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.
I suspect Oracle doesn't test at least its own products for compatibility before releasing them.
-
- Posts: 15
- Joined: 7. Jan 2009, 19:19
- Primary OS: Solaris
- VBox Version: OSE other
- Guest OSses: Windows, Linux, Solaris
- Location: Maryland
Re: update 10 supported?
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.
Update: Try changing the controller from SATA to SAS. Once I did this, it continued to boot. Must be a bad SATA controller module.
-
- Oracle Corporation
- Posts: 793
- Joined: 7. Jan 2008, 16:17
Re: update 10 supported?
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.
Oracle Corp.
Re: update 10 supported?
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".
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".
- Attachments
-
- VBox.log
- (70.07 KiB) Downloaded 46 times
-
- Oracle Corporation
- Posts: 793
- Joined: 7. Jan 2008, 16:17
Re: update 10 supported?
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.
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.
Oracle Corp.
-
- Posts: 9
- Joined: 7. Aug 2012, 11:29
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: 4.3
Re: update 10 supported?
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
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