From: Stefan Hajnoczi <stefanha@gmail.com>
To: Matt Broadstone <mbroadst@gmail.com>
Cc: qemu_mail <qemu-discuss@nongnu.org>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] virtio-serial guest agent channel timing requirements
Date: Fri, 4 Nov 2016 22:18:34 +0000 [thread overview]
Message-ID: <CAJSP0QUt_oBxfWaxYvZX4ySu9t-5OLjr3n9vJkUPX9QZN=_mHQ@mail.gmail.com> (raw)
In-Reply-To: <CAMsD-yCyjqP8_j0x3nV=u=_-P-SgvZX_3_QgoAp-Z=jzEa0+uA@mail.gmail.com>
On Fri, Nov 4, 2016 at 9:46 PM, Matt Broadstone <mbroadst@gmail.com> wrote:
> I've progressed with creating my own agent, and have successfully been
> able to communicate over virtio-serial channels in order to provide
> two-way communication between hypervisor and guest. My problem now
> seems to be related to _when_ to start listening to the domain sockets
> - specifically it seems that if I start listening to the domain
> sockets on the hypervisor side before the guest (in this case windows
> guest) is fully loaded, communication will fail over the channel until
> both sides hangup and try again. Is there any documentation on this
> behavior, or guidelines I should be following for when to begin
> communication over the channels?
That sounds odd. I'd expect communicate to work as soon as both host
and guest are ready.
Have you tried a Linux guest instead of a Windows guest? Perhaps it's
a bug in the virtio-win drivers.
Stefan
next parent reply other threads:[~2016-11-04 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMsD-yCyjqP8_j0x3nV=u=_-P-SgvZX_3_QgoAp-Z=jzEa0+uA@mail.gmail.com>
2016-11-04 22:18 ` Stefan Hajnoczi [this message]
2016-11-05 0:01 ` [Qemu-devel] virtio-serial guest agent channel timing requirements Laszlo Ersek
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='CAJSP0QUt_oBxfWaxYvZX4ySu9t-5OLjr3n9vJkUPX9QZN=_mHQ@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=mbroadst@gmail.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@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).