>>The problem is the timeout if guest agent is not running (not the overhead). >>But maybe it is not a big problem, and not worth the efforts?
>>1.) send guest command like shutdown, freeze, unfreeze I think it's not a problem here. a small extra 1s timeout on guest-sync is ok I Think. (and if guest-sync timeout, we can fallback on old method (acpi shutdown, vm pause) >>2.) query guest status timeout could be a problem in pvestatd (not sure where you want to query guest status) ----- Mail original ----- De: "Dietmar Maurer" <diet...@proxmox.com> À: "Alexandre DERUMIER" <aderum...@odiso.com> Cc: pve-devel@pve.proxmox.com, "Wolfgang Link" <wolfg...@linksystems.org> Envoyé: Lundi 24 Novembre 2014 20:54:01 Objet: RE: [PATCH 2/2] now if the QMP command starts with guest-+ , it will bind dynamicly to the VMID.qga socket. To test the function vmtime is implemented which return the vm UNIX Time. > What do we want to do you qga ? 1.) send guest command like shutdown, freeze, unfreeze 2.) query guest status > if it's only to send some commands like filesystem freeze|unfreeze, > stop[start , I > think that calling guest-sync before it's not a big overhead. The problem is the timeout if guest agent is not running (not the overhead). But maybe it is not a big problem, and not worth the efforts? _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
