QEMU/KVM ACPI Guest Shutdown: Difference between revisions
(Added to Qemu/KVM and added headlines + cleaned up language a bit. todo: adding something about ACPI to pve-docs?) |
(finished sentence) |
||
| Line 1: | Line 1: | ||
= Introduction = | = Introduction = | ||
Proxmox VE uses ACPI to send | Proxmox VE uses ACPI to send shutdown signals to the Virtual Machines (QEMU/KVM). | ||
Thus your Virtual Machines | Thus your Virtual Machines needs to support ACPI so that it may react to such signals. | ||
You should check if your VM reacts properly to the ACPI signals | You should check if your VM reacts properly to the ACPI signals. Else the VM may not shutdown and Proxmox VE will stop it after a timeout on some API calls. Such a stop can lead to data loss in the worst case. | ||
= Linux = | = Linux = | ||
Revision as of 12:01, 4 October 2016
Introduction
Proxmox VE uses ACPI to send shutdown signals to the Virtual Machines (QEMU/KVM). Thus your Virtual Machines needs to support ACPI so that it may react to such signals.
You should check if your VM reacts properly to the ACPI signals. Else the VM may not shutdown and Proxmox VE will stop it after a timeout on some API calls. Such a stop can lead to data loss in the worst case.
Linux
For Linux Virtual Machines, make sure that the ACPI event daemon is installed and running. Desktop distributions should already have it, but minimal or Server distributions may not.
For Ubuntu and Debian install the 'acpid' package in the Virtual Machine.
Windows
For Windows, make sure an ACPI HAL is installed.
On Windows server 2003/8 also make sure to change policy to allow shutdown without being logged into the system. Start -> Run:
gpedit.msc
Find the following key:
Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Shutdown: Allow system to be shut down without having to log on
Change it to Enabled.