qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Michal Privoznik <mprivozn@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Is guest agent socket being closed upon reboot?
Date: Mon, 16 Jan 2012 09:11:09 -0600	[thread overview]
Message-ID: <4F143E0D.10608@linux.vnet.ibm.com> (raw)
In-Reply-To: <4F1425A2.3050906@redhat.com>

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!

  reply	other threads:[~2012-01-16 15:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-16 13:26 [Qemu-devel] Is guest agent socket being closed upon reboot? Michal Privoznik
2012-01-16 15:11 ` Michael Roth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-01-16 13:11 Michal Privoznik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F143E0D.10608@linux.vnet.ibm.com \
    --to=mdroth@linux.vnet.ibm.com \
    --cc=mprivozn@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).