Guests on Proxmox v3.4 won't shutdown gracefully on node reboot or stop! :(

[AndydnA]

Hi all,

I have recently installed Proxmox v3.4 on a couple of DELL systems in my office and on another two into the Paris OVH's datacenter.
All the installations have been updated (no commercial licensing) just yesterday with the latest community kernel.
The issue is that if I try to shutdown or reboot any node (from bash or also from the web admin interface) the various VMs, that are all Linux (CentOS, Debian, OpenSUSE, etc.), begin to be destroyed and the system stops in few seconds. In other words, Proxmox doesn't perform a graceful shutdown of the various guests.
This is terrible! In particular if you have guests with running databases, you will corrupt them all at 100%!
N.B.: This happen on all PVE servers also before that I have updated all of them.
The system seem to feel correctly the shutdown ("Stop all VMs and Containers" is showed inside the logs), but then it doesn't show the shutdown of etch single VMs ("VMXXX - Shutdown" messages didn't show/exist), because it didn't do it!
Have you any advice? Do you know if this is a bug?

Thanks,

Andy

 

[tom]

your guests seems to NOT support anonymous ACPI shutdowns.

proxmox ve sends the shutdown, if your guests does not accepts this the VM will be stopped (forced).

=> configure your guests. e.g. on a Debian VM, just install acpid (apt-get install acpid)

 

[sigxcpu]

@tom: if you have a working solution for Windows VMs (no, the policy edit for unattended shutdowns is not working) I will be forever grateful.

 

[AndydnA]

Hi Tom,

acpid is already installed into my VMs.
I don't have any problem to shutdown those VMs gracefully from admin panel or with qm command.
Theoretically if I can shutdown the guests in this way, Proxmox should shutdown them when I reboot/shutdown the node, but it doesn't.

Andy

 

[tom]

@tom: if you have a working solution for Windows VMs (no, the policy edit for unattended shutdowns is not working) I will be forever grateful.

configuring windows can be tricky here, there are several policies, consult a windows guy (and search this forum, already discussed several times)

 

[sigxcpu]

As I already told you. I've applied all the policies for unattended shutdown and such. Sometimes you can get a shutdown without a user logged in. No chance when there is a session suspended.
Of course this means Windows is a stupid OS, because nowadays it is pretty stupid to assume that you will always run the single instance on bare metal.