Article ID: 127433, created on Nov 15, 2015, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo 6.0

Symptoms

Virtual machine cannot resume after updating to Virtuozzo 6 update 10.

The following messages can be found in /var/log/parallels.log:

11-15 11:24:20.214 F /disp:2728:19627/ Recieved event PET_DSP_EVT_VM_RESUMING (100013) from vm {0d861cdf-a18c-44a3-bf05-fb4b9ec883dc} (name='MyVM')
11-15 11:24:20.219 F /disp:2728:19627/ Recieved event PET_DSP_EVT_VM_ABOUT_TO_START_INIT (100040) from vm {0d861cdf-a18c-44a3-bf05-fb4b9ec883dc} (name='MyVM')
11-15 11:24:20.225 F /disp:2728:19627/ Received response PRL_ERR_VM_START_FAILED (0x80000041) for DspCmdVmStart(1001) request from vm {0d861cdf-a18c-44a3-bf05-fb4b9ec883dc} (name='MyVM')
11-15 11:24:20.225 F /disp:2728:19627/ Command DspCmdVmStart(1001) was failed. Rollback VM to previous state VMS_SUSPENDED(0x30000009)VmUuid={0d861cdf-a18c-44a3-bf05-fb4b9ec883dc} (name=MyVM)
11-15 11:24:20.227 F /disp:2728:19627/ Vm state was changed from VMS_RESUMING to VMS_RESETTING for vm {0d861cdf-a18c-44a3-bf05-fb4b9ec883dc} (name='MyVM'), to powerState 0(vpsNormal)
11-15 11:24:20.227 F /disp:2728:19627/ Response package was successfully routed to client
11-15 11:24:20.228 F /disp:2728:19637/ Task '18Task_StopVncServer' with uuid = {9bf76c32-c950-4c0a-8e56-16501b82c1a5} was started. Flags = 0
11-15 11:24:20.228 F /disp:2728:19637/ Failed to stop VNC server with error code: 80035005 'PRL_ERR_VNC_SERVER_NOT_STARTED'
11-15 11:24:20.228 F /disp:2728:19637/ Task '18Task_StopVncServer' with uuid = {9bf76c32-c950-4c0a-8e56-16501b82c1a5} was finished with result PRL_ERR_SUCCESS (0) )
11-15 11:24:20.234 F /disp:2728:5300/ Processing command 'DspCmdGetVmConfigById' 2173 (PJOC_SRV_GET_VM_CONFIG)
11-15 11:24:20.235 F /disp:2728:19600/ Processing command 'DspCmdUserLogoff' 2042 (PJOC_SRV_LOGOFF)
11-15 11:24:20.235 F /disp:2728:19600/ Parallels user [root@.] successfully logged off. [sessionId = {18d4f375-694b-428a-b87b-669655a8a73a} ]
11-15 11:24:20.236 W /disp:2728:19600/ handleClientDisconnected
11-15 11:24:20.237 F /disp:2728:19627/ Recieved event PET_VM_EVT_TIS_BACKUP_WRITE (101600) from vm {0d861cdf-a18c-44a3-bf05-fb4b9ec883dc} (name='MyVM')
11-15 11:24:20.279 F /disp:2728:19627/ Recieved event PET_DSP_EVT_VM_ABORTED (100009) from vm {0d861cdf-a18c-44a3-bf05-fb4b9ec883dc} (name='MyVM')
11-15 11:24:20.280 F /disp:2728:5299/ Processing command 'DspCmdDirGetVmList' 2029 (PJOC_SRV_GET_VM_LIST)
11-15 11:24:20.281 F /disp:2728:19627/ Vm state was changed from VMS_RESETTING to VMS_STOPPING for vm {0d861cdf-a18c-44a3-bf05-fb4b9ec883dc} (name='MyVM'), to powerState 0(vpsNormal)
...
11-15 11:24:45.015 F /disp:2728:19627/ Received response PRL_ERR_FAILURE (0x80000009) for DspIllegalCommand(0) request from vm {0d861cdf-a18c-44a3-bf0
5-fb4b9ec883dc} (name='MyVM')
11-15 11:24:45.015 F /disp:2728:19627/ Response package was successfully routed to client
11-15 11:24:45.016 F /disp:2728:19627/ Recieved event PET_DSP_EVT_VM_SUSPENDED (100012) from vm {0d861cdf-a18c-44a3-bf05-fb4b9ec883dc} (name='MyVM')
11-15 11:24:45.037 F /disp:2728:19627/ Vm state was changed from VMS_STOPPING to VMS_SUSPENDING_SYNC for vm {0d861cdf-a18c-44a3-bf05-fb4b9ec883dc} (name='MyVM'), to powerState 0(vpsNormal)
..
11-15 11:24:45.474 F /disp:2728:19627/ Vm state was changed from VMS_SUSPENDING_SYNC to VMS_SUSPENDED for vm {0d861cdf-a18c-44a3-bf05-fb4b9ec883dc} (n
ame='MyVM'), to powerState 0(vpsNormal)

The following messages can be found in the Virtual Machine's parallels.log (e.g. /var/parallels/MyVM.pvm/parallels.log):

11-15 11:24:20.214 F /vm:19623:19632/ [Profile] Event Loop initialization (driver open) time is 0 msecs
11-15 11:24:20.214 F /vm:19623:19632/ HVT is accessible. Status 0x1
11-15 11:24:20.214 F /vm:19623:19632/ CPU lacks NX (Execute Disable) support, guest OSes may crash or misbehave
11-15 11:24:20.214 F /vm:19623:19632/ refusing to start. Enable NX bit in the BIOS and try again
11-15 11:24:20.214 F /MCDException:19623:19632/ (!) Error: Throwing exception id=2147483713 (PRL_ERR_VM_START_FAILED).
11-15 11:24:20.214 F /vm:19623:19632/ SARE state(SareStateStart): enqueued 'SareCmdTerminate'(8) command
11-15 11:24:20.214 F /vm:19623:19632/ VM state(VmStateInit): completed 'VmLocalCmdStart'(20001) command with result 0x80000041
11-15 11:24:20.216 F /vm:19623:19631/ SaRe action 0x2000000 is finished (Status=0x80020018)
11-15 11:24:20.216 F /vm:19623:19631/ VM state(VmStateInit): enqueued 'VmLocalEventSaReFinished'(20036) command
11-15 11:24:20.216 F /vm:19623:19631/ SARE state(SareStateStart): completed 'SareCmdTerminate'(8) command with result 0x80000009
11-15 11:24:20.224 F /vm:19623:19632/ VM state(VmStateInit): changed to VmStateStopped

Cause

NX support is not enabled in host CPU.

Resolution

Use CPU which has NX support. For more information refer to the following Microsoft Knowledge Base article: PAE/NX/SSE2 Support Requirement Guide for Windows 8

If the CPU has the execution prevention mechanism (NX or XD) support, then it is necessary to enable the feature in BIOS. Refer to the hardware vendor documentation for more details on how to enable "No execute" feature.

Search Words

PET_DSP_EVT_VM_ABOUT_TO_START_INIT

CPU lacks NX

Enable NX bit

VM Won't start

c62e8726973f80975db0531f1ed5c6a2 2897d76d56d2010f4e3a28f864d69223 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF