Solaris / OpenSolarisThis forum is for the discussion of Solaris, OpenSolaris, OpenIndiana, and illumos.
General Sun, SunOS and Sparc related questions also go here. Any Solaris fork or distribution is welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have installed OpenSolaris 052008 within a VM on Virtualbox-2.0.4. When I bootup the VM I'll get the following message:
NOTICE: MPO disabled because memory is interleaved
BIOS microcode patch for AMD Opteron erratum 131 was not detected (I forget the rest)
I had also installed Solaris10u6 on another VM and I'll get the first line message only. Are either of these a serious problem and how can I go about fixing both?
Also, I have found that the Solaris10u6 will not boot when I have the VT-x/AMD-V option set, in fact during the install when it went to reboot it hung, yet OpenSolaris has trouble running if the same option is not set.
My physical machine is based on a Gig-A-Byte MoBo with an AMD Athlon X2 64 with 4GB RAM. The OS=Fedora 9, uname -r; 2.6.27.5-37.fc9.x86_64. I thought that using the 64bit version of Virtualbox that you had to have hdwe virtualization enabled in the BIOS as well as the option selected for VM options for 64bit guest OSes to work properly?
The MPO error is not a worry, the Memory Placement Optimization (MPO) is ignored as the memory is interleaved and therefore already Optimized by the hardware.
I'm assuming that AMD have some BIOS patch which you need to apply to the Hardware which the OS needs, but will work without it. It wojuld be best to have a look on the Manu's site for the patch as it should improve the systems stability.
What about the 2nd message of the erratum 131 error, or is that what you are referring to in your 2nd sentence?
"I'm assuming that AMD have some BIOS patch which you need to apply to the Hardware which the OS needs, but will work without it. It wojuld be best to have a look on the Manu's site for the patch as it should improve the systems stability."
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.