Article ID: 120375, created on Feb 27, 2014, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo 6.0
  • Virtuozzo hypervisor
  • Virtual Automation 6.0

Symptoms

  1. Windows 2012 was installed in a virtual machine successfully in the past and after some configuration change, the virtual machine does not boot with:

    No boot device avaialble, press Enter to continue
    

    no_boot

  2. The following error can be observed in the log file of the virtual machine MyVM (typically, in /var/parallels/MyVM.pvm/parallels.log):

    02-26 11:55:24.430 F /vm:912043:912315/ Virtual machine is ready to boot!
    02-26 11:55:24.488 F /LocalDevices:912043:912282/ [AHCI] max_delta increase: 7
    02-26 11:55:24.511 F /vm:912043:912315/ Sending question = PRL_WNG_NO_OPERATION_SYSTEM_INSTALLED
    02-26 13:54:56.678 F /IOCommunication:912043:78954/ IO server ctx [read thr] (cli_state 0x7fce08033e50, sender 1): IO protocol minor version number differs!
    02-26 13:56:03.160 F /IOCommunication:912043:83767/ IO server ctx [read thr] (cli_state 0x7fce08033e50, sender 1): IO protocol minor version number differs!
    
  3. The VM was created with OS type "Windows 2012" or "Windows 8".

Cause

Among the possible reasons, EFI boot has been disabled for this VM, checking from the SSH session to the hardware node:

~# prlctl list MyVM --info |grep EFI
EFI boot: off

Resolution

EFI can be enabled in different ways:

  • Using PVA MN interface, navigate to Infrastructure > HN hardware.node.name > Virtual Machine MyVM > Configure Hardware Settings in the General / Boot configuration, mark the ceckbox Use EFI and save the configuration as shown on the screenshot:

    Use EFI

  • From the SSH session to the hardware node, run the command:

    ~# prlctl set MyVM --efi-boot on
    The VM has been successfully configured.
    

Search Words

EFI

No boot device available

EFI Boot

PRL_WNG_NO_OPERATION_SYSTEM_INSTALLED

No boot device avaialble, press Enter to continue

windows 2012

Unable to download one or more packages to the source server. Check the repository settings on the source server.

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 319940068c5fa20655215d590b7be29b 0dd5b9380c7d4884d77587f3eb0fa8ef 0889ab60fa6494de107aa7338c3c38b6 c62e8726973f80975db0531f1ed5c6a2

Email subscription for changes to this article
Save as PDF