-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VM shutdown not detected #34
Comments
Thank you for the extensive error report, I have seen this problem in my instance as well. Will have a look pretty soon, as a workaround stopping the VM with the "stop" button after it has reached the poweroff target seems to work for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When shutting down a virtual machine (either via Proxmox or from within the vm itself), Proxmox does not detect that the vm has powered off. In this state it is still possible to connect to the console (see screenshot below), and
qm list
reports that the vm is still running. In this state the only way to actually power the machine off is to forcefully stop it. This is also problematic when shutting down or rebooting the host, because systemd would wait for all vms to shutdown (which it fails to detect) and then would time out after 90 seconds.I assume this might be related to the following error which occurs whenever a vm is started:
On my Debian based Proxmox host this socket does exist and seems to be managed by the qmeventd systemd service, which appears to be missing on proxmox-nixos.
The text was updated successfully, but these errors were encountered: