|
Last change
on this file since 98657 was 98549, checked in by vboxsync, 2 years ago |
|
Docs: bugref:10302. Uploading .dita user manual files we received from the doc team on 25th Jan.
|
-
Property svn:eol-style
set to
native
|
|
File size:
1.2 KB
|
| Line | |
|---|
| 1 | <?xml version='1.0' encoding='UTF-8'?>
|
|---|
| 2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
|---|
| 3 | <topic xml:lang="en-us" id="ts_solaris-10-guest-slow-boot-smp">
|
|---|
| 4 | <title>Certain Oracle Solaris 10 Releases May Take a Long Time to Boot with SMP</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>
|
|---|
| 8 | When using more than one CPU, Oracle Solaris 10 10/08, and
|
|---|
| 9 | Oracle Solaris 10 5/09 may take a long time to boot and may
|
|---|
| 10 | print warnings on the system console regarding failures to read
|
|---|
| 11 | from disk. This is a bug in Oracle Solaris 10 which affects
|
|---|
| 12 | specific physical and virtual configurations. It is caused by
|
|---|
| 13 | trying to read microcode updates from the boot disk when the
|
|---|
| 14 | disk interrupt is reassigned to a not yet fully initialized
|
|---|
| 15 | secondary CPU. Disk reads will time out and fail, triggering
|
|---|
| 16 | delays of about 45 seconds and warnings.
|
|---|
| 17 | </p>
|
|---|
| 18 | <p>
|
|---|
| 19 | The recommended solution is upgrading to at least Oracle Solaris
|
|---|
| 20 | 10 10/09 which includes a fix for this problem. Alternative
|
|---|
| 21 | solutions include restricting the number of virtual CPUs to one
|
|---|
| 22 | or possibly using a different storage controller.
|
|---|
| 23 | </p>
|
|---|
| 24 | </body>
|
|---|
| 25 |
|
|---|
| 26 | </topic>
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
