From nobody Sun Jan 28 10:55:01 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 4TN7cZ3bYcz58LW4 for ; Sun, 28 Jan 2024 10:55:10 +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 4TN7cY338dz4f6c for ; Sun, 28 Jan 2024 10:55:09 +0000 (UTC) (envelope-from jo@durchholz.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=durchholz.org header.s=default2202 header.b=WWD9kMF7; 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=U6hLjQh257yg3ZnWh2ICSoehvG9gIUtmkGu8tdSObXE=; b=WWD9kMF77i9umbvD5IcVppOnwC RfakyBUbUNsPmgDLqU9Rpb3OFdERNqCkIYlAM4BRfWnypKWBt3mhV7HhBhbHP8ii/bvYmm5VfmWQ2 NvMt1yAk3QlAa1kQAVGOV+mSPTNiDIrmxC83QI8kpeiSRXKbbjYSqnO5VLand6g+WoJ5LkaaL2VPM VC6U/wkw1yOXbFPoNSliWarBTQmqWv2ou3kDxi4d7JOC7YGzdGY/taagiRxg82jPsCDSzu1Gl06rx 0qmUeFoi/pn74w1qUYSh2uTrD0UIGU/jyde/uw9XsAAxn8X5Rt47KJJZPNPqh4hIa1ix7w4ssdvCA fnSLpIqw==; Received: from sslproxy07.your-server.de ([78.47.199.104]) by www382.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rU2oY-0003mX-7z for freebsd-virtualization@FreeBSD.org; Sun, 28 Jan 2024 11:55:02 +0100 Received: from [2003:ed:d721:6600:c6c9:a3c2:50ea:4641] by sslproxy07.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1rU2oY-000FNl-0J for freebsd-virtualization@FreeBSD.org; Sun, 28 Jan 2024 11:55:02 +0100 Message-ID: Date: Sun, 28 Jan 2024 11:55:01 +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 To: "freebsd-virtualization@FreeBSD.org" Content-Language: en-US From: Jo Durchholz Subject: Vagrant images for KVM? 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/27168/Sun Jan 28 10:37:47 2024) X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.48 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.992]; 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: 4TN7cY338dz4f6c Hi all, I see VirtualBox and VmWare images of FreeBSD Stable for VirtualBox and VmWare, but none for KVM. What can I do to make KVM images happen? Apologies if this is the wrong list, just point me in the right direction if it isn't. Disclaimer: I'm not an expert for KVM or Vagrant, though I do have some pretty solid experience with multiple build systems. Regards, Jo ---- TL;DR: Vagrant, because I believe that's the most automatable way to set up a test suite that spins up a FreeBSD VM, injects the code under test (a Python package), and retrieves the test results. Virtual machine, because Python development happens on Linux, as development can't be moved from established Debian infrastructure to FreeBSD (sorry). No VmWare because of expected licensing restrictions. No VirtualBox: The open-source edition would actually be enough, but it is currently sort-of broken on Debian (one could pin Pyton to 3.9 and install old packages to make it work, but that's too intrusive for a project that wishes to attract contributors). KVM seems well-supported across all Linux distros.