From: Feng Yang <fyang@redhat.com>
To: Michael Goldish <mgoldish@redhat.com>
Cc: autotest@test.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM Test: add -w parameter in nc command in kvm_utils.py
Date: Wed, 20 Oct 2010 06:18:43 -0400 (EDT) [thread overview]
Message-ID: <949282996.997051287569923273.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <692004637.996981287569640055.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com>
----- "Michael Goldish" <mgoldish@redhat.com> wrote:
> From: "Michael Goldish" <mgoldish@redhat.com>
> To: "Feng Yang" <fyang@redhat.com>
> Cc: autotest@test.kernel.org, kvm@vger.kernel.org
> Sent: Wednesday, October 20, 2010 5:11:32 PM GMT +08:00 Beijing / Chongqing / Hong Kong / Urumqi
> Subject: Re: [PATCH] KVM Test: add -w parameter in nc command in kvm_utils.py
>
> On 10/20/2010 08:55 AM, Feng Yang wrote:
> > If a connection and stdin are idle for more than timeout seconds,
> > then the connection is silently closed. withou this paramter,
> > nc will listen forever for a connection. This may cause our test
> > hang. redmine issue:
> > http://redmine.englab.nay.redhat.com/issues/show/6947
> > Add -w parameter should fix this issue.
> >
> > Signed-off-by: Feng Yang <fyang@redhat.com>
> > ---
> > client/tests/kvm/kvm_utils.py | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/client/tests/kvm/kvm_utils.py
> b/client/tests/kvm/kvm_utils.py
> > index a51c857..526d38d 100644
> > --- a/client/tests/kvm/kvm_utils.py
> > +++ b/client/tests/kvm/kvm_utils.py
> > @@ -733,7 +733,7 @@ def remote_login(client, host, port, username,
> password, prompt, linesep="\n",
> > elif client == "telnet":
> > cmd = "telnet -l %s %s %s" % (username, host, port)
> > elif client == "nc":
> > - cmd = "nc %s %s" % (host, port)
> > + cmd = "nc %s %s -w %s" % (host, port, timeout)
> > else:
> > logging.error("Unknown remote shell client: %s" % client)
> > return
>
> I don't understand how remote_login() can stall here.
> kvm_utils._remote_login() doesn't rely on nc's self-termination. If
> no
> shell prompt is available after 10 seconds, nc is forcefully
> terminated
> and _remote_login() fails. If it somehow stalls this might indicate
> a
> bug somewhere.
It is really rarely reproduce. Only meet this issue when guest panic or core dump.
nc stall. Do not know why it is not terminated after 10s.
I think -w parameter is helpful in this situation.
If it does not cause other issue, we'd better add -w in nc command.
Thanks for your command. What do you think?
Feng Yang
next parent reply other threads:[~2010-10-20 10:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <692004637.996981287569640055.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com>
2010-10-20 10:18 ` Feng Yang [this message]
2010-10-20 10:48 ` [PATCH] KVM Test: add -w parameter in nc command in kvm_utils.py Michael Goldish
[not found] <816063419.1092631287625722129.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com>
2010-10-21 1:57 ` Feng Yang
2010-10-21 7:38 ` Michael Goldish
2010-10-20 6:55 Feng Yang
2010-10-20 9:11 ` Michael Goldish
2010-10-27 20:26 ` Lucas Meneghel Rodrigues
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=949282996.997051287569923273.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com \
--to=fyang@redhat.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mgoldish@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