Search results

I did a lot of tests these past few days, and everything is ok now. qm stopall or qm shutdown, logged in guest or not, guest screen locked or not, are working like a charm. It wasn't the case when I opened the thread. I did nothing but installing a new Windows 2008 Server guest since. Strange.

Which prevent anonymous shutdown from qm stopall but allow anonymous shutdown from qm shutdown ? To have that behaviour, there is a need to receive different signals, isn't it ? If qm stopall and qm shutdown send the same ACPI event, how Windows can make a difference ?

I've just finished testing a fresh install of Windows 2008 Server. dm stopall works for it :confused: I still don't have explanation why the older one doesn't react to qm stopall, but does react from qm shutdown... It makes sense to believe something is wrong in the older guest, but what ...

Thank you for your comment :) Don't focus on the "qm stopall 30", I use this in my shutdown script after "qm shutdown"ing all the VMs and the maximum sleep of 5 mn, after what I may use qm stopall 0 if I want (already slept for 5 mn, I don't have to wait more to "hard" reboot the remaining...

Hello, I'm using Proxmox for 6 months now, with a very good experience so far, hosting 6 Linux (Ubuntu Server and CentOS 5.5) and 1 Windows Server 2008 guests (KVM only). I've a (small) issue with qm stopall and a Windows Server 2008 guest. When I use qm stopall, all guests but the...