From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: Olaf van der Spek <olafvdspek@gmail.com>,
Alok Kataria <akataria@vmware.com>,
Hans de Goede <hdegoede@redhat.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: 912087@bugs.debian.org, Michael Biebl <biebl@debian.org>,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: Bug#912087: reassign to systemd #912087 | openssh-server: Slow startup after the upgrade to 7.9p1
Date: Thu, 29 Nov 2018 14:54:48 +0100 [thread overview]
Message-ID: <20181129135446.jsrckfmy2urcsb5g@breakpoint.cc> (raw)
In-Reply-To: <CAA7U3HN8aV-BrYGS4XNgXsfAL8eFcxdjReM-5VZOSnJntVanJw@mail.gmail.com>
On 2018-11-28 13:43:07 [+0100], Olaf van der Spek wrote:
> > > They might just as well install haveged or configure virtio-rng in such
> > > a case.
> >
> > Right. Do you think, that it would necessary to add something to the
> > release notes?
>
> I do. ;)
> What's the workaround for VMware?
>
> Does it just take longer to start or do some services not start at all?
It will take longer to start, it will start. Let me pass that workaround
question to someone from vmware/virtualbox and #912087:
On a recent kernel you see something like that:
[ 68.823013] random: crng init done
which means it took almost 69 seconds for the system to initialize its
rng. OpenSSH 7.9 can be compilied against OpenSSL 1.1.1 which in turn
switched to getrandom() (for its randomness).
This syscall will block until kernel's rng is ready which took in this
example almost 69 seconds.
Those "high" numbers are not a problem on decent/recent HW but occur
oftern on in virtualized environments.
For KVM we have CONFIG_HW_RANDOM_VIRTIO. Are there any plans to get
something similar for VMware/Vbox?
[0] http://bugs.debian.org/912087
Sebastian
parent reply other threads:[~2018-11-29 13:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAA7U3HN8aV-BrYGS4XNgXsfAL8eFcxdjReM-5VZOSnJntVanJw@mail.gmail.com>]
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=20181129135446.jsrckfmy2urcsb5g@breakpoint.cc \
--to=sebastian@breakpoint.cc \
--cc=912087@bugs.debian.org \
--cc=akataria@vmware.com \
--cc=arnd@arndb.de \
--cc=biebl@debian.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olafvdspek@gmail.com \
--cc=virtualization@lists.linux-foundation.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
all inboxes | Powered by JetHome®