Article ID: 123000, created on Sep 24, 2014, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo 6.0


Windows EFI VMs fails to start if it has assigned RAM more than 64256 MB (63.75 GB).

The guest OS reboots in the cycle, it is not possible to manage the VM via VNC or using PMC.

In the log file of VM, the following log records can be found every time the guest OS tries to start:

10-08 18:08:38.529 F /vm:739012:816091/ Sending question = PRL_ERR_CPU_RESTART
SystemReset by triple-fault
10-08 18:08:38.530 F /vm:739012:816091/ VM state(VmStateRunning): enqueued 'VmLocalCmdHardwareReset'(20009) command
10-08 18:08:38.530 F /vm:739012:816091/ VCPU0 state(VcpuStateRunning): enqueued 'VcpuCmdTerminate'(6) command


This issue has been confirmed and the internal request #PSBM-26752 submitted to have this issue fixed in future updates.


There are two possible workarounds.

  1. Disable EFI boot for this VM. The installation of Windows should be repaired for proper boot.

    ~# prlctl set VMName --efi-boot no
  2. Extract the attached archive with EFI boot image on the server, and restart VM via stop/start.

    ~# wget
    ~# tar zxf lin-efi64.tar.gz -C /usr/lib64/parallels-server/
    ~# prlctl stop VMName
    ~# prlctl start VMName

    Note: It is necessary to remove this file once the official fix is released: no special check is done during updates for presence of this file. Watch the release notes for the fix of #PSBM-26752.

    ~# rm /usr/lib64/parallels-server/efi64.bin
    ~# yum update

Search Words

SystemReset by triple-fault



the virtual machine processor was reset by the operating system parallels

cant stop vm

c62e8726973f80975db0531f1ed5c6a2 2897d76d56d2010f4e3a28f864d69223 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF