qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: John Snow <jsnow@redhat.com>,
	kwolf@redhat.com, qemu-block@nongnu.org, qemu-devel@nongnu.org,
	mreitz@redhat.com, Pino Toscano <ptoscano@redhat.com>,
	asn@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v3] ssh: switch from libssh2 to libssh
Date: Tue, 19 Dec 2017 10:24:18 -0500	[thread overview]
Message-ID: <20171219152418.GB20944@localhost.localdomain> (raw)
In-Reply-To: <20171218213140.GT2787@redhat.com>

On Mon, Dec 18, 2017 at 09:31:40PM +0000, Richard W.M. Jones wrote:
> On Mon, Dec 18, 2017 at 01:43:39PM -0500, John Snow wrote:
> > Hi, friendly ping:
> > 
> > It's been over a month with no replies, so it's safe to say this has
> > gotten lost in the 2.11 release shuffle.
> > 
> > Recommend you re-send it for the 2.12 window.
> 
> Actually there is an interop problem with the ssh daemon on ESXi which
> I've not resolved yet.  Unfortunately there was no response to my
> upstream message about collecting debugging info:
> 
> https://www.libssh.org/archive/libssh/2017-12/0000000.html
> 
> Since liberating guests from VMware is a prime reason to have an ssh
> driver in qemu, I'd really like this to be fixed first ...
> 
> Rich.

I also sent a review, and found an issue with at least libssh 0.7-4 (not
getting EOF on short reads).

  parent reply	other threads:[~2017-12-19 15:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15 16:26 [Qemu-devel] [PATCH v3] ssh: switch from libssh2 to libssh Pino Toscano
2017-11-15 17:10 ` Richard W.M. Jones
2017-12-18 18:43 ` [Qemu-devel] [Qemu-block] " John Snow
2017-12-18 21:31   ` Richard W.M. Jones
2017-12-18 23:19     ` Andreas Schneider
2017-12-19 15:24     ` Jeff Cody [this message]
2017-12-19 16:15       ` Richard W.M. Jones
2017-12-18 19:55 ` [Qemu-devel] " Jeff Cody
2018-01-18 16:26   ` Pino Toscano

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=20171219152418.GB20944@localhost.localdomain \
    --to=jcody@redhat.com \
    --cc=asn@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=ptoscano@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.com \
    /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).