Troubleshooting Conditions That Might Prevent Fast Reboot From Working

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:

Sep 18 13:19:12 too-cool genunix: WARNING: nvidia has no quiesce()
reboot: not all drivers have implemented quiesce(9E)

Note -
To find out if a driver supports the quiesce function, use the following command:

# grep quiesce /var/adm/messages

For drivers that do not yet support the quiesce fucntion, file a bug against quiesce(9E).

If the graphics drivers are the only drivers that do not support the quiesce function, you can attempt to force a fast reboot by running the following commands:
```
# echo "force_fastreboot/W 1" | mdb -kw
# echo "set force_fastreboot = 1" >> /etc/system
```
If the driver for the network interface card (NIC) does not implement the quiesce function, you can try to unplumb the interface first, then attempt a fast reboot of the system.
```
# ifconfig <your-nic-interface> unplumb
# reboot -f
```
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.
```
Fastboot: Couldn't allocate size below PA 1G to do fast reboot
Fastboot: Couldn't allocate size below PA 64G to do fast reboot
```
System is among those platforms that are "Blacklisted".
Unsupported environment
Fast reboot functionality is not currently supported in the following environments:
- Solaris xVM dom0 domains
- Solaris xVM PV domU domains
- Non-global zones

For more information: