-
Notifications
You must be signed in to change notification settings - Fork 498
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
Improve VM Monitoring with qemu-guest agent information #6645
Milestone
Comments
We should try to also include:
Examples:
If possible, these values should also be extended to the Prometheus probe. |
dann1
added a commit
to dann1/docs
that referenced
this issue
Jul 15, 2024
2 tasks
dann1
added a commit
to dann1/docs
that referenced
this issue
Jul 16, 2024
rsmontero
pushed a commit
to OpenNebula/docs
that referenced
this issue
Jul 29, 2024
rsmontero
pushed a commit
that referenced
this issue
Aug 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue to keep track of the investigation on qemu-ga usage and its integration possibilities within the linux context packages.
VM crashing detection
The current monitoring system can not detect a VM crashing. This was tested with a kernel-panicked VM. With qemu-ga installed in the VM, a crash can be detected by the hypervisor. We can check if the VM has crashed with:
virsh qemu-agent-command one- '{"execute":"guest-ping"}'
The VM is not crashed if the exit code of the command is 0, meaning that the VM is replying to the qemu "ping".
The text was updated successfully, but these errors were encountered: