From owner-freebsd-cloud@freebsd.org Fri Sep 1 21:33:10 2017 Return-Path: Delivered-To: freebsd-cloud@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18A99E0853E for ; Fri, 1 Sep 2017 21:33:10 +0000 (UTC) (envelope-from 0100015e3f5c9ca6-5867960d-56cb-4292-965a-eb57b007fe4b-000000@amazonses.com) Received: from a8-56.smtp-out.amazonses.com (a8-56.smtp-out.amazonses.com [54.240.8.56]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D279F649D3 for ; Fri, 1 Sep 2017 21:33:09 +0000 (UTC) (envelope-from 0100015e3f5c9ca6-5867960d-56cb-4292-965a-eb57b007fe4b-000000@amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ae7m2yrxjw65l2cqdpjxuucyrvy564tn; d=tarsnap.com; t=1504301587; h=Subject:To:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; bh=YJ+vET1SaqaP8sb7tkJTitRYRtWjDrjK4XJ65NcS1i0=; b=YFZ9kPPHExsyu/HjmCX44Zw9GF+EpQFewTjvW6e7baDXY+p+CKlbIahAQfoKIEFQ WD7R0YHXEOWPMfx2FKCkgEWF5rcySpZCgNUuNr//VsE01ciugO3pJBMETiyndwASeOW lUGhbLZ1U8dFCw07iLRTgHBY4eyjxw5QAkW0unYw= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1504301587; h=Subject:To:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:Feedback-ID; bh=YJ+vET1SaqaP8sb7tkJTitRYRtWjDrjK4XJ65NcS1i0=; b=Gfz0ayYQ62rfETH+FOffeZGG+fLqhbsgsCCwtWEF5Y6byfHKvi1e7NxjTKGvgcGx vseeJpAOE+ppWvnRLx87CH4TTMwOsnojnvV/dUmgfBcLG6DvVsIM3yWhg9va4EwMlz7 sVGEtdZXKCvAGgZHczPugNDSogkuSoweiRLKLbNg= Subject: Re: Launch and boot times of AWS FreeBSD AMI To: Rafal Lukawiecki , freebsd-cloud@freebsd.org References: From: Colin Percival Message-ID: <0100015e3f5c9ca6-5867960d-56cb-4292-965a-eb57b007fe4b-000000@email.amazonses.com> Date: Fri, 1 Sep 2017 21:33:07 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-SES-Outgoing: 2017.09.01-54.240.8.56 Feedback-ID: 1.us-east-1.Lv9FVjaNvvR5llaqfLoOVbo2VxOELl7cjN0AOyXnPlk=:AmazonSES X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2017 21:33:10 -0000 On 09/01/17 14:24, Rafal Lukawiecki wrote: > I wonder if there is any possibility to shorten the launch and reboot times > of the FreeBSD AMI. I understand that it is necessary to have the first > post-install and update reboot, after the initial launch, but it seems to > take a longish time compared to Amazon Linux. Without any solid > measurements, it seems, from the “VGA” console, that it does pause a bit > after printing the SSH fingerprint and starting cron, sendmail, configuring > vt, scheduling a background fsck in 60 secs, and printing these odd > messages: Yes, it is annoyingly slow. Part of this is the initial freebsd-update pulling down updates, but there are definitely things which should be faster. > [: =: unexpected operator > [: =: unexpected operator > mount: /dev/gpt/rootfs: Device busy > [: =: unexpected operator I've been meaning to track down where these are coming from. Setting rc_debug=YES in /etc/rc.conf might help... > I wonder if it could be optimised, somehow. It would be nice to shave a > minute or more from the waits, if possible. I am also curious what those > errors are. One issue I *have* tracked down is that on large systems we spend a crazy amount of time initializing VM -- around 45 seconds on a x1.32xlarge. I tested a patch from markj last week but I don't think it has gone into the tree yet. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid