Troubleshooting Conditions That Might Prevent Fast Reboot From Working

Version 9 by jheieck
on Jan 16, 2009 10:05.

compared with
Current by jheieck
on Nov 04, 2009 01:20.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (4)

View page history
The following are possible conditions under which the Fast Reboot feature might not work:

* GRUB menu cannot be processed.
* Driver does not implement the {{quiesce}} function
If you attempt a fast reboot of a system with an unsupported driver, a message similar to the following is displayed:
# reboot -f
{code}
* Insufficient memory
* System cannot allocate enough memory
If there is not enough memory on the system, below 1G (0x40000000) for building the page tables, or not enough free memory to load the new kernel and the boot archive, the fast reboot attempt fails with the following messages, then falls back to regular reboot.
{code}
Fastboot: Couldn't allocate size below PA 64G to do fast reboot
{code}
* System is among those platforms that are "Blacklisted".
* Unsupported environment
Fast reboot functionality is not currently supported in the following environments:

The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence
Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact