Long-Term Supported Versions

    Common Problems and Solutions

    1. After the nvwa update command is executed, the system is not upgraded.

      Cause: An error occurs when the running information is retained or the kernel is replaced.

      Solution: View logs to find the error cause.

    2. After the acceleration feature is enabled, the nvwa command fails to be executed.

      Cause: nvwa provides many acceleration features, including quick kexec, memory pinning, and CPU park. These features involve configurations using CLI and memory allocation. When selecting the memory, run cat /proc/iomem to ensure that the selected memory does not conflict with that of other programs. If necessary, run the dmesg command to check whether error logs exist after the feature is enabled.

    3. After the live upgrade, the related process is not recovered.

      Cause: Check whether the nvwa service is running. If the nvwa service is running, the service or process may fail to be recovered.

      Solution: Run the service nvwa status command to view the NVWA logs. If the service fails to be started, check whether the service is enabled, and then run the systemd command to view the logs of the corresponding service. Further logs are stored in the process or service folder named after the path specified by criu_dir. The dump.log file stores the logs generated when the running information is retained, and the restore.log file stores the logs generated for process recovery.

    4. The recovery fails, and the log displays "Can't fork for 948: File exists."

      Cause: The kernel live upgrade tool finds that the PID of the program is occupied during program recovery.

      Solution: The current kernel does not provide a mechanism for retaining PIDs. Related policies are being developed. This restriction will be resolved in later kernel versions. Currently, you can only manually restart related processes.

    5. When the nvwa command is used to save and recover a simple program (such as hello world), the system displays a message indicating that the operation fails or the program is not running.

      Cause: There are many restrictions on the use of CRIU.

      Solution: View the NVWA logs. If the error is related to the CRIU, check the dump.log or restore.log file in the corresponding directories. For details about the usage restrictions related to the CRIU, see CRIU WiKi.

    Bug Catching

    Buggy Content

    Bug Description

    Submit As Issue

    It's a little complicated....

    I'd like to ask someone.


    Just a small problem.

    I can fix it online!

    Bug Type
    Specifications and Common Mistakes

    ● Misspellings or punctuation mistakes;

    ● Incorrect links, empty cells, or wrong formats;

    ● Chinese characters in English context;

    ● Minor inconsistencies between the UI and descriptions;

    ● Low writing fluency that does not affect understanding;

    ● Incorrect version numbers, including software package names and version numbers on the UI.


    ● Incorrect or missing key steps;

    ● Missing prerequisites or precautions;

    ● Ambiguous figures, tables, or texts;

    ● Unclear logic, such as missing classifications, items, and steps.


    ● Technical principles, function descriptions, or specifications inconsistent with those of the software;

    ● Incorrect schematic or architecture diagrams;

    ● Incorrect commands or command parameters;

    ● Incorrect code;

    ● Commands inconsistent with the functions;

    ● Wrong screenshots.

    Risk Warnings

    ● Lack of risk warnings for operations that may damage the system or important data.

    Content Compliance

    ● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

    ● Copyright infringement.

    How satisfied are you with this document

    Not satisfied at all
    Very satisfied
    Click to create an issue. An issue template will be automatically generated based on your feedback.
    Bug Catching
    编组 3备份