From: Fam Zheng <famz@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
"patches@linaro.org" <patches@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH] tests/vm: Increase timeout waiting for VM to boot to 5 minutes
Date: Fri, 24 Aug 2018 21:51:51 +0800 [thread overview]
Message-ID: <20180824135151.GH31581@lemon.usersys.redhat.com> (raw)
In-Reply-To: <CAFEAcA82wxTeHiPkMKnO9XCDGYbtP1B9_HgZxJu+d6=XKdx+iw@mail.gmail.com>
On Fri, 08/24 13:45, Peter Maydell wrote:
> On 24 August 2018 at 13:02, Peter Maydell <peter.maydell@linaro.org> wrote:
> > On 23 August 2018 at 15:11, Fam Zheng <famz@redhat.com> wrote:
> >> On Thu, 08/23 12:21, Peter Maydell wrote:
> >>> The VM tests currently have a timeout of 2 minutes for trying
> >>> to connect to ssh. Since the guest VM has to boot from cold
> >>> to the point of accepting inbound ssh during this time, if the
> >>> host machine is heavily loaded it can spuriously time out.
> >>> Increase the timeout from 2 to 5 minutes.
> >>>
> >>> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> >>
> >> Acked-by: Fam Zheng <famz@redhat.com>
> >>
> >> Again, please apply this yourself. :)
> >
> > Applied, thanks.
>
> I'm still seeing the ssh login for a netbsd VM sometimes
> sit there apparently indefinitely. Is there some way to
> debug what the guest VM is actually doing when the
> log just sits there doing
> DEBUG:root:ssh_cmd: ssh -q -o StrictHostKeyChecking=no -o
> UserKnownHostsFile=/dev/null -o ConnectTimeout=1 -p 36947 -i
> /home/peter.maydell/qemu-netbsd/build/vm-test-g0SkVX.tmp/id_rsa
> qemu@127.0.0.1 exit 0
> DEBUG:root:ssh_cmd: ssh -q -o StrictHostKeyChecking=no -o
> UserKnownHostsFile=/dev/null -o ConnectTimeout=1 -p 36947 -i
> /home/peter.maydell/qemu-netbsd/build/vm-test-g0SkVX.tmp/id_rsa
> qemu@127.0.0.1 exit 0
>
> (eg a capture of its terminal output) ?
I need to investigate into it. Sometimes I see the timeout too with V=1, but not
if I omit it (i.e. on DEBUG: lines are echoed).
Fam
prev parent reply other threads:[~2018-08-24 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 11:21 [Qemu-devel] [PATCH] tests/vm: Increase timeout waiting for VM to boot to 5 minutes Peter Maydell
2018-08-23 14:11 ` Fam Zheng
2018-08-24 12:02 ` Peter Maydell
2018-08-24 12:45 ` Peter Maydell
2018-08-24 13:51 ` Fam Zheng [this message]
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=20180824135151.GH31581@lemon.usersys.redhat.com \
--to=famz@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.