search for: keepalive_count

...VE_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 #keepalive_interval = 5 #keepalive_cou...

...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 > > #keepalive_interval = 5 > #keepalive_count = 5 > >> What is meant by "client" in libvirtd.conf ? virsh ? > > Yes, virsh is a client, as is virt-manager or any application connecting to > libvirtd. > >> Why do i have regular timeouts although my two hosts are very performant ? 128GB >> RAM, 16 co...

Hello everyone, I have a issue about the KVM block migration. Please give me some help. 1) I use the "virsh create" command to start a KVM VM in source machine. 2) And then, I use "virsh migrate" cammand to start a block migration: # virsh migrate --live --copy-storage-all --verbose win7 qemu+ssh:// 186.100.8.136/system root at 186.100.8.136's password:

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