KVM: virKeepAliveTimerInternal:156 : No response from client
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
KVM: virKeepAliveTimerInternal:156 : No response from client
Hi Friends,
I am new to this forum site and I have newly created virtual machines using KVM few months back. But today after checking log file of libvirt i found that there is a warning being appeared on a random basis which informs that no response from client is recieved to virKeepAliveTimerInternal.
Sample Logs are below:
2015-05-28 06:30:44.398+0000: 4292: warning : virKeepAliveTimerInternal:156 : No response from client 0x25d3190 after 5 keepalive messages in 30 seconds
2015-05-28 06:30:44.398+0000: 4292: warning : virKeepAliveTimerInternal:156 : No response from client 0x25d6500 after 5 keepalive messages in 30 seconds
2015-05-28 06:30:44.398+0000: 4292: warning : virKeepAliveTimerInternal:156 : No response from client 0x25cf040 after 5 keepalive messages in 30 seconds
2015-05-28 06:30:44.398+0000: 4292: warning : virKeepAliveTimerInternal:156 : No response from client 0x25d3f00 after 5 keepalive messages in 30 seconds
2015-05-28 06:30:44.398+0000: 4292: warning : virKeepAliveTimerInternal:156 : No response from client 0x25cd280 after 5 keepalive messages in 30 seconds
2015-05-28 06:30:44.398+0000: 4292: warning : virKeepAliveTimerInternal:156 : No response from client 0x25d76d0 after 5 keepalive messages in 30 seconds
Hey Kamal,
Welcome to LQ, a little reading suggests the first step might be to make sure you're running the most recent version of libvirt (this "die queitly" issue was a known bug in 2013 that was supposedly fixed in subsequent versions).
Thanks for support!
but this is to bring in your information that i am using 0.10.2 version of libvirt. SO if I upgrades it to 1.2.16 version will the specification that i have customised with this version would be gettting affected or not(like storage pool, attached device and all)?
Probably not, Kamal. I've been working with it through a couple of revisions and other than a little tinkering here and there, I haven't had that problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.