From nobody Sat Feb 24 08:56:33 2024 X-Original-To: freebsd-virtualization@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4ThgjK2M56z5CMwv for ; Sat, 24 Feb 2024 08:56:37 +0000 (UTC) (envelope-from jo@durchholz.org) Received: from www382.your-server.de (www382.your-server.de [78.46.146.228]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4ThgjJ3N6rz4QHf for ; Sat, 24 Feb 2024 08:56:36 +0000 (UTC) (envelope-from jo@durchholz.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=durchholz.org header.s=default2202 header.b=dAMfrM4B; dmarc=none; spf=pass (mx1.freebsd.org: domain of jo@durchholz.org designates 78.46.146.228 as permitted sender) smtp.mailfrom=jo@durchholz.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=durchholz.org; s=default2202; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:References:To:Subject:From:MIME-Version:Date:Message-ID:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=wb+tgFUg5Qoh5ff0WbHeqLgqRITNHufngtGUcNh10oY=; b=dAMfrM4Bt0eUO7inIps152UZkg YifbAePulI6Qzmjiq23Dxg7hQU4WNbqKGBZ2vczAF7t9nZZwS3djR7GTu1XQli4lIlThmuL3ynnFb HCrVeIshxPSpK6I8XrY17JI85lT+zW07KAZ5NQEdnBJVEux/Nalbi1CrwFJUc0dx7T/5uncleRDGH aWrzLp5WgOk7X9ibJBoPmlWc4yoROGpj/mQ613iIJQCHuH9+0HQkqpQstkfT8b6I+nqroG2o0YFEq mOBbVvfFK3AGL0yumimPE0/3SA13up57nYTwqK9akRhD8tnD3qZaSOwiKSIGIecHVRKJbLu22m6ez 9+weDcJg==; Received: from sslproxy01.your-server.de ([78.46.139.224]) by www382.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rdnph-000I7B-Ny for freebsd-virtualization@freebsd.org; Sat, 24 Feb 2024 09:56:33 +0100 Received: from [81.221.201.210] (helo=[192.168.178.48]) by sslproxy01.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1rdnph-00EfZN-1q for freebsd-virtualization@freebsd.org; Sat, 24 Feb 2024 09:56:33 +0100 Message-ID: <7e5bc32c-dddb-4d33-96e9-99a955eed572@durchholz.org> Date: Sat, 24 Feb 2024 09:56:33 +0100 List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Jo Durchholz Subject: Re: Best way to have a FreeBSD VM for automated testing? Content-Language: en-US To: "freebsd-virtualization@FreeBSD.org" References: <163e57a9-0b61-414c-a8f7-109f5ac90f69@durchholz.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Authenticated-Sender: jo@durchholz.org X-Virus-Scanned: Clear (ClamAV 0.103.10/27194/Fri Feb 23 10:32:16 2024) X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.58 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.990]; R_DKIM_ALLOW(-0.20)[durchholz.org:s=default2202]; R_SPF_ALLOW(-0.20)[+a]; RCVD_IN_DNSWL_LOW(-0.10)[78.46.139.224:received]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; ASN(0.00)[asn:24940, ipnet:78.46.0.0/15, country:DE]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[durchholz.org]; HAS_X_AS(0.00)[]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_EQ_ADDR_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-virtualization@freebsd.org]; DKIM_TRACE(0.00)[durchholz.org:+] X-Rspamd-Queue-Id: 4ThgjJ3N6rz4QHf On 24.02.24 07:41, Mark Blackman wrote: > > If an Amazon firecracker environment works for you, there’s > https://www.freebsd.org/status/report-2023-04-2023-06/boot-performance/ Oh. Thanks. 20 ms boot time sounds good enough to me :-D ... aww, the PDF link to the slides is broken :-( https://wiki.freebsd.org/BootTime (Colin Percival) works and reports ~8 seconds on FreeBSD 14.0. http://www.daemonology.net/blog/2021-08-12-EC2-boot-time-benchmarking.html (again, Colin Percival 2021) tells me that the best boot-to-TCP time was about 1.23 s, while typical boot times would be around 10-15 s. Those 8 seconds are actually good, unless the competition has sped up as well :-) (This benchmarks just TCP availability, I don't know or how much needs to be added for ssh availability.) There's a conclusion here: While those improvements are awesome, 8 seconds are nowhere near the do-not-disrupt-developer-workflow threshold, so the VM snapshot it will be. Oh. Wait. These links talk about FreeBSD's boot time. I don't know how this relates to Firecracker. OTOH Firecracker is very new, so I'm somewhat reluctant to jump that bandwagon anyway. > of course, there’s more to booting than the kernel. Definitely. In my own testing, something that vaguely sounded like a mail subsystem had a full minute-long wait. Some tweaking will be needed to get rid of that behaviour. I'm comfortable with that, though not with having to put those tweaks into a setup script and keeping it up-to-date with every new FreeBSD version. I haven't seen an OS or distro that does not have this kind of problem though, so I'll just have to live with that. > I’d guess some of those improvements could apply to more generic VM hypervisors too. Probably, but as much as I like exploring rabbit holes, I already have a too-long list of these to add yet another one :-) Regards, Jo