search for: admin_keepalive_interv

...o : virKeepAliveMessage:107 : RPC_KEEPALIVE_SEND: ka=0x55b2bb937740 client=0x55b2bb930d50 prog=1801807216 vers=1 proc=1 > > There seems to be a kind of a countdown. From googleing i found that this may be related to libvirtd.conf: > > # Keepalive settings for the admin interface > #admin_keepalive_interval = 5 > #admin_keepalive_count = 5 > > What is meant by the "admin interface" ? virsh ? virsh-admin, which you can use to change some admin settings of libvirtd, e.g. log_level. You are interested in the keepalive settings above those ones in libvirtd.conf, specifically #kee...

Hi, i have a two-node cluster with several domains as resources. During testing i tried several times to migrate some domains concurrently. Usually it suceeded, but rarely it failed. I found one clue in the log: Dec 03 16:03:02 ha-idg-1 libvirtd[3252]: 2018-12-03 15:03:02.758+0000: 3252: error : virKeepAliveTimerInternal:143 : internal error: connection closed due to keepalive timeout The

...5:07.455+0000: 12553: info : virKeepAliveMessage:107 : RPC_KEEPALIVE_SEND: ka=0x55b2bb937740 client=0x55b2bb930d50 prog=1801807216 vers=1 proc=1 There seems to be a kind of a countdown. From googleing i found that this may be related to libvirtd.conf: # Keepalive settings for the admin interface #admin_keepalive_interval = 5 #admin_keepalive_count = 5 What is meant by the "admin interface" ? virsh ? What is meant by "client" in libvirtd.conf ? virsh ? Why do i have regular timeouts although my two hosts are very performant ? 128GB RAM, 16 cores, 2 1GBit/s network adapter on each host in bondi...

...>> RAM, 16 cores, 2 1GBit/s network adapter on each host in bonding. >> During migration i don't see much load, although nearly no waiting for IO. > > I'd think concurrently migrating 3 VMs on a 1G network might cause some > congestion :-). > >> Should i set admin_keepalive_interval to -1 ? > > You should try 'keepalive_interval = -1'. You can also avoid sending keepalive > messages from virsh with the '-k' option, e.g. 'virsh -k 0 migrate ...'. > > If this doesn't help, are you in a position to test a newer libvirt, preferably &g...