Article ID: 123058, created on Oct 3, 2014, last review on Sep 10, 2015

  • Applies to:
  • Virtuozzo 6.0
  • Virtuozzo hypervisor

Symptoms

A virtual machine fails to boot after Guest Tools installation, the following errors can be found in /var/parallels/VM_Name.pvm/parallels.log:

Capv_Win64Patch_Deadline
PhyMemRemoveGuestPhyPagesRange(f0300) for non-existent range
PhyMemRemoveGuestPhyPagesRange(f0300) for non-existent range
PhyMemRemoveGuestPhyPagesRange(f0300) for non-existent range
PhyMemRemoveGuestPhyPagesRange(f0300) for non-existent range
PhyMemRemoveGuestPhyPagesRange(f0300) for non-existent range
PhyMemRemoveGuestPhyPagesRange(f0300) for non-existent range
Enable AHCI mode
Capv_Win64Patch_Deadline

Cause

The virtual machine is unable to boot due to the AHCI driver error.

Solution

The virtual machine should be able to boot in Safe Mode with AHCI disabled.

Follow these steps to boot the VM in Safe Mode:

  1. Change hdd(and cdrom, if required) type to ide:

    # prlctl set VM_Name --device-set hdd0 --iface ide
    # prlctl set VM_Name --device-set cdrom0 --iface ide
    
  2. Add the 'devices.ahci.enable=0' boot flag o the virtual machine's configuration.

    Boot flag can be added using either of the following ways:

    • Parallels Management Console (Select the VM -> Configure -> Hardware -> Boot Order -> Boot flags field)
    • Virtual Automation (Select the VM -> Hardware Settings -> CPU -> System flags field)
    • Manually modifying the virtual machine's configuration file (config.pvs):

      # grep SystemFlags /var/parallels/VM_Name.pvm/config.pvs
           <SystemFlags>devices.ahci.enable=0</SystemFlags>
      
  3. Start the VM in Safe Mode and re-install Parallels Tools.

Additional information

Be aware that the installation of Guest Tools in an unsupported guest OS may affect the booting with similar symptoms.

Please refer to the list of Supported Guest Operating Systems:

Virtuozzo 6

Virtuozzo hypervisor 5

Search Words

parallels tools

vm does not boot after parallels tools install

install

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 c62e8726973f80975db0531f1ed5c6a2 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF