VirtualBox for OpenSolaris

Discussions related to using VirtualBox on Solaris hosts.
Locked
sandervl
Volunteer
Posts: 1064
Joined: 10. May 2007, 10:27
Primary OS: MS Windows Vista
VBox Version: PUEL
Guest OSses: Windows, Linux, Solaris

VirtualBox for OpenSolaris

Post by sandervl »

innotek has just released the first beta of VirtualBox for OpenSolaris.

The binary for 64 bits AMD/Intel OpenSolaris can be downloaded here: http://virtualbox.org/wiki/Downloads.
Last edited by sandervl on 5. Sep 2008, 12:08, edited 1 time in total.
GE-Tec
Posts: 6
Joined: 26. Feb 2008, 09:06

Post by GE-Tec »

Is there any documentation for VirtualBox on openSolaris?

Is there a GUI front-end for VirtualBox?

If yes, which program needs to be run to start the GUI front-end on openSolaris

Thanks for VirtualBox. A really nice alternative to VMWare.

Cheers

Gary
sandervl
Volunteer
Posts: 1064
Joined: 10. May 2007, 10:27
Primary OS: MS Windows Vista
VBox Version: PUEL
Guest OSses: Windows, Linux, Solaris

Post by sandervl »

GE-Tec
Posts: 6
Joined: 26. Feb 2008, 09:06

Post by GE-Tec »

I am getting there!

I am now installing Windows XP in a VirtualBox on openSolaris 8)

Great stuff! :D

Thanks

Gary
paulm27
Posts: 5
Joined: 2. Mar 2008, 02:51

Post by paulm27 »

Just installed the beta version on a b81 system with a few zones.

On installing had to use "pkgadd -G -d ...." to prevent pkgadd touching my zones and ignoring the global zone.

Another thing with this build is the additions CD... it is not included and there is not an exact match version match... Had a choice of the 1.5.4 and 1.5.6, went the 1.5.6 version, any issues on this?

I'll open another topic about CPU being pegged to 80% on an idle VM...

So far this product looks better for the casual user than hvm (xen).

--
Paul
Karsten Bolz
Posts: 5
Joined: 5. Mar 2008, 11:54

Windows shows blue screen during start

Post by Karsten Bolz »

After installing VirtualBox 1.5.51 on my Solaris notebook (Toschiba Tecra M5 running Solaris 11 Nevada build 66) I encountered a blue screen when starting a preconfigured Windows image. I found that the problem was related to "intelppm.sys", After doing some research, I found a hint to set:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Processor

Or

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intelppm

And changing the 'Start' value to '4'.

See this blog for detailed information:
http://blogs.msdn.com/virtual_pc_guy/ar ... 84461.aspx
Locked