Hi Alex, As a sys admin - I would rexommend to thoroughly check the 'journalctl' if it is permanent. If not - check libvirt logs (/var/log/something/qemu/VM-name.log -> this is based on memory). Also, if you run out of memory - the OOM killer kicked in and it will be reporting details kn /var/log/messages. Best Regards, Strahil NikolovOn Jun 2, 2019 06:37, Alex McWhirter <alex@triadic.us> wrote:
After moving from 4.2 -> 4.3 libvirtd seems to be leaking memory, it recently crashed a host by eating 123GB of RAM. Seems to follow one specific VM around, this is the only VM i have created since 4.3, the others were all made in 4.2 them upgraded to 4.3
What logs would be applicable?
Libvirt 4.5.0 _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/SB75R63BMUEWC5...