From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:41938) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rmmaa-0004ar-Hx for qemu-devel@nongnu.org; Mon, 16 Jan 2012 08:27:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RmmaV-00033q-Vr for qemu-devel@nongnu.org; Mon, 16 Jan 2012 08:27:08 -0500 Received: from mx1.redhat.com ([209.132.183.28]:3297) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RmmaV-00033b-Oq for qemu-devel@nongnu.org; Mon, 16 Jan 2012 08:27:03 -0500 Message-ID: <4F1425A2.3050906@redhat.com> Date: Mon, 16 Jan 2012 14:26:58 +0100 From: Michal Privoznik MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Is guest agent socket being closed upon reboot? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: mdroth@linux.vnet.ibm.com Hi, I'd like you to ask if/why is guest agent socked being closed upon guest reboot. I am using virtserialport to talk to guest agent: -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/f16x86_64.agent,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 I would understand if socket accept connection iff GA is up and running. However, this is not the case. One is perfectly able to connect to GA socket even without any GA inside guest. I think that GA socket should be as persistent as monitor. Even despite fact they address different areas. Application issuing monitor commands shouldn't be forced to reconnect on every guest reboot, should they? Or have I misunderstood the concept? Michal