From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56990) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dl46N-0003W1-TH for qemu-devel@nongnu.org; Thu, 24 Aug 2017 22:12:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dl46M-00012d-Vv for qemu-devel@nongnu.org; Thu, 24 Aug 2017 22:12:03 -0400 Received: from mail-qt0-x22f.google.com ([2607:f8b0:400d:c0d::22f]:37716) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dl46M-00011N-Qk for qemu-devel@nongnu.org; Thu, 24 Aug 2017 22:12:02 -0400 Received: by mail-qt0-x22f.google.com with SMTP id d15so5780832qta.4 for ; Thu, 24 Aug 2017 19:12:00 -0700 (PDT) MIME-Version: 1.0 From: Sam Date: Fri, 25 Aug 2017 10:11:59 +0800 Message-ID: Content-Type: text/plain; charset="UTF-8" Subject: [Qemu-devel] [QGA] Bug of qga? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi all, I'm using qga to send `route -n` and `ping` command to guest. But I found SOMETIMES, the second `ping` command's result is the same as `route -n` command. So I guess is there some cache mechanism of qga command result? So when I send the second command, and receive from qga socket, I receive the result of first command. Or is this bug happened because of I use async mechanism of python code to operate qga socket? This is the python code I use to operate on this qga socket: try: > sock=socket(AF_UNIX, SOCK_STREAM) > sock.settimeout(20) > sock.connect(vm_qga_sockpath) > sock.send(cmd) > while True: > res = sock.recv(1024) > if len(res): > break > except Exception as e: > res = -1 > finally: > sock.settimeout(None) > sock.close()