From nobody Fri Feb 23 19:17:02 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 4ThKWl4pHzz5BLQ3 for ; Fri, 23 Feb 2024 19:17:07 +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 4ThKWj6WJfz5213 for ; Fri, 23 Feb 2024 19:17:05 +0000 (UTC) (envelope-from jo@durchholz.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=durchholz.org header.s=default2202 header.b=ppwS5QoG; 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: Subject:From:To: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:In-Reply-To:References; bh=1XkX2zpgDXTG8aQKIDESFF39Vs+B5uBqx/QygCeGDEQ=; b=ppwS5QoGSQ1ZO8SHAUcbtjdkWq tfji3lFxjZETidJ6Np4Sv/VAnpLt6/faP+3z1tFbNAbpWPRMzfwDFXtddvbXyvz6Wg6uvccy2CBNz 3oW5TNVPsAEjR67p0H9lm8+7Tu4AqDEx9sWKVJCTDDneFDRvsG3u7L0rCe3dAHSeFG1YQ5OrIipT5 y9xKQYMAYe1FRKsStM/+sb3m+/ec3FCfPc3VqneStwvjcFyT9wgQA5T4PXYUqy6cMSBtgk8OU64EZ 12XZKKQSZx4KyJgRJRders7MF0mj58+Sso/0Wg5L1ofxg2F0QDPaRYmRF7EqmZZ6fmoY4Fg2E1his fECnbzwA==; Received: from sslproxy05.your-server.de ([78.46.172.2]) by www382.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rdb2d-000JX1-Bh for freebsd-virtualization@freebsd.org; Fri, 23 Feb 2024 20:17:03 +0100 Received: from [81.221.201.210] (helo=[192.168.178.48]) by sslproxy05.your-server.de with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rdb2d-000Lbl-8C for freebsd-virtualization@freebsd.org; Fri, 23 Feb 2024 20:17:03 +0100 Message-ID: <163e57a9-0b61-414c-a8f7-109f5ac90f69@durchholz.org> Date: Fri, 23 Feb 2024 20:17:02 +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 Content-Language: en-US To: "freebsd-virtualization@FreeBSD.org" From: Jo Durchholz Subject: Best way to have a FreeBSD VM for automated testing? Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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.49 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; R_SPF_ALLOW(-0.20)[+a]; R_DKIM_ALLOW(-0.20)[durchholz.org:s=default2202]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(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]; MLMMJ_DEST(0.00)[freebsd-virtualization@freebsd.org]; HAS_X_AS(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)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[durchholz.org:+] X-Rspamd-Queue-Id: 4ThKWj6WJfz5213 Hi all, I'm in repeatable build land, working in Linux and developing a FreeBSD appliance. For tests, I need to run a FreeBSD VM, put some Python code and test data into it, run the script, and get the test results back. Repeatability means: Everything done with the VM needs to be scriptable (using a GUI for exploring is okay but things have to translate). Which in turn means that every setup step for a FreeBSD image comes with a pretty high coding and maintenance cost. So my question is: What's the FreeBSD image that has the least number of steps to get the base system up and running? I suppose it's the VM-IMAGES section, but is this correct? Follow-up question: The startup time needs to be as fast as possible. Sub-second would be great ("don't disrupt the developer's thought stream"). I see the boot process from a vanilla VM-IMAGES image takes multiple seconds; can this be sped up to just a few seconds, or do I need to run the setup and create a VM snapshot at which the VM starts for each test run? Regards, Jo