kvm does not shut down

yep that is there:
Code:
mediawiki  ~ # ls -l /proc/acpi
total 0
-rw-r--r-- 1 root root 0 Jan  6 05:25 wakeup

That's strange, it should work.

you can also try to send "system_powerdown" in vm monitor. This is the command that proxmox sent to qemu for the shutdown
 
so tried a stop mode backup at 3.1 . that failed
Code:
 36106: Jan 06 08:51:42 INFO: Starting Backup of VM 36106 (qemu)
  36106: Jan 06 08:51:42 INFO: status = running
  36106: Jan 06 08:51:42 INFO: update VM 36106: -lock backup
  36106: Jan 06 08:51:42 INFO: backup mode: stop
  36106: Jan 06 08:51:42 INFO: ionice priority: 7
  36106: Jan 06 08:51:42 INFO: stopping vm
  36106: Jan 06 09:01:43 INFO: VM quit/powerdown failed
  36106: Jan 06 09:01:43 ERROR: Backup of VM 36106 failed - command 'qm shutdown 36106 --skiplock --keepActive
--timeout 600' failed: exit code 255

any ideas on how to debug this?
 
so tried a stop mode backup at 3.1 . that failed
[...]
36106: Jan 06 09:01:43 ERROR: Backup of VM 36106 failed - command 'qm shutdown 36106 --skiplock --keepActive
--timeout 600' failed: exit code 255

[...]
Jan 6 03:28:00 sys3 qm[23442]: <root@pam> starting task UPID:sys3:00005B93:0070F7DD:568CD010:qmshutdown:106:root@pam:
Jan 6 03:28:00 sys3 qm[23443]: shutdown VM 106: UPID:sys3:00005B93:0070F7DD:568CD010:qmshutdown:106:root@pam:
[...]
[...]

I asked this before (qm stop vmID), but the output you gave seemed to have been for "qm shutdown vmID"


just to be on the safe side and making sure you tested it.

Issue
"qm stop vmID" via CLI
post the output from Proxmox-Syslog and VM-Syslog.
 
I asked this before (qm stop vmID), but the output you gave seemed to have been for "qm shutdown vmID"


just to be on the safe side and making sure you tested it.

Issue
"qm stop vmID" via CLI
post the output from Proxmox-Syslog and VM-Syslog.

that works on 3.1 not 4.1
 
to clarify,
  • on pve 3.1 "qm stop ID" shuts down the VM properly.
  • on pve 4.1 "qm stop ID" does not shut down the VM at all ? or you can not issue said command ?
and the issue was on a 3.1 based host only? Or you have it on a 4.1 host as well ?
 
qm stop 106

is working now.

stop does not work from pve.

there may be a sequence of events that caused the issue. I'll try to recreate.

else it was something I did wrong.