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.
VirtualBox for OpenSolaris
-
- 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
Last edited by sandervl on 5. Sep 2008, 12:08, edited 1 time in total.
-
- Volunteer
- Posts: 1064
- Joined: 10. May 2007, 10:27
- Primary OS: MS Windows Vista
- VBox Version: PUEL
- Guest OSses: Windows, Linux, Solaris
Yes and yes. See our manual: http://195.34.175.98/download/UserManual.pdf
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
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
-
- Posts: 5
- Joined: 5. Mar 2008, 11:54
Windows shows blue screen during start
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
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