From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:55012) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RmoJu-0001IS-Lr for qemu-devel@nongnu.org; Mon, 16 Jan 2012 10:18:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RmoJs-0008VP-Cj for qemu-devel@nongnu.org; Mon, 16 Jan 2012 10:18:01 -0500 Received: from e3.ny.us.ibm.com ([32.97.182.143]:42542) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RmoJr-0008Tg-Gq for qemu-devel@nongnu.org; Mon, 16 Jan 2012 10:17:59 -0500 Received: from /spool/local by e3.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Mon, 16 Jan 2012 10:14:11 -0500 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d01relay06.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q0GFBVmY2207836 for ; Mon, 16 Jan 2012 10:11:32 -0500 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q0GFBK4A005316 for ; Mon, 16 Jan 2012 08:11:20 -0700 Message-ID: <4F143E0D.10608@linux.vnet.ibm.com> Date: Mon, 16 Jan 2012 09:11:09 -0600 From: Michael Roth MIME-Version: 1.0 References: <4F1425A2.3050906@redhat.com> In-Reply-To: <4F1425A2.3050906@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Is guest agent socket being closed upon reboot? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Michal Privoznik Cc: qemu-devel@nongnu.org On 01/16/2012 07:26 AM, Michal Privoznik wrote: > 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 > Hi Michal, In my testing this doesn't seem to be the case, the host socket connection persists throughout reboots, guest agent restarts, etc. I'm not sure what would trigger the close either, the chr->chr_guest_close/chr->chr_guest_open events do not seem to be initialised at any point, which AFAICT are the only things that would affect the char frontend/socket connection during reboot. Can you provide more details on your setup? What version/commit you're running and what sequence induces the behavior? Thanks!