[pve-devel] pvedaemon hanging because of qga retry

[Alexandre DERUMIER]

>>I think that will not work. I already tried to explain why in my previous post: 

>>The problem is that there is no way to decide if qga agent is running or not. 
>>You will simply run into the 'short' timeout as soon as there is some load on 
>>the 
>>server. 

What do you mean my "some load" ? 

"totally unresponsive" ?  I have try with cpu benchmark simulator, with crazy load, and guest agent is still responding.

if the guest is so loaded, than it can't even send reponse to guest-ping (with a "short" timeout of some seconds, not ms!),
if think we shouldn't try to send after that the other command with 1 hour timeout...



----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "aderumier" <aderumier at odiso.com>
Cc: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Dimanche 20 Mai 2018 08:16:25
Objet: Re: [pve-devel] pvedaemon hanging because of qga retry

> On May 20, 2018 at 3:22 AM Alexandre DERUMIER <aderumier at odiso.com> wrote: 
> 
> 
> I have notice something when agent daemon is down: 
> 
> #qm agent 124 ping 
> VM 124 qmp command 'guest-ping' failed - got timeout 
> #qm agent 124 ping 
> VM 124 qmp command 'guest-ping' failed - got timeout 
> #qm agent 124 ping 
> VM 124 qmp command 'guest-ping' failed - got timeout 
> #qm agent 124 ping 
> VM 124 qmp command 'guest-ping' failed - unable to connect to VM 124 qga 
> socket - timeout after 11 retries 
> 
> 
> Seem that after 3 request, we can't connect anymore to socket. 
> (I'm seeing same thing with socat directly to qga socket) 
> 
> 
> What I would like to have , to avoid big timeout (mainly for fsfreeze, this is 
> the biggest with 1hour), 
> is to send first a guest-ping or maybe better guest-info, with a short 
> timeout. 
> if it's succesfull, then send the other query. 

I think that will not work. I already tried to explain why in my previous post: 

The problem is that there is no way to decide if qga agent is running or not. 
You will simply run into the 'short' timeout as soon as there is some load on 
the 
server.