From owner-freebsd-xen@freebsd.org Tue Jan 14 14:43:03 2020 Return-Path: Delivered-To: freebsd-xen@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EB1911ED022 for ; Tue, 14 Jan 2020 14:43:03 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from mail.kronometrix.org (mail.kronometrix.org [95.85.46.90]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail.kronometrix.org", Issuer "mail.kronometrix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47xtVH0lMYz4Df9; Tue, 14 Jan 2020 14:43:02 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from [192.168.1.172] (82-203-141-23.bb.dnainternet.fi [82.203.141.23]) (authenticated bits=0) by mail.kronometrix.org (8.15.2/8.15.2) with ESMTPSA id 00EEgt1I090401 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 14 Jan 2020 14:42:56 GMT (envelope-from sparvu@kronometrix.org) X-Authentication-Warning: mail.kronometrix.org: Host 82-203-141-23.bb.dnainternet.fi [82.203.141.23] claimed to be [192.168.1.172] From: Stefan Parvu Message-Id: Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\)) Subject: Re: FreeBSD 12.1 hypervisor management tools Date: Tue, 14 Jan 2020 16:42:49 +0200 In-Reply-To: <20200114110125.GM11738@Air-de-Roger> Cc: freebsd-xen@freebsd.org, "" To: =?utf-8?Q?Roger_Pau_Monn=C3=A9?= References: <69EDA7BA-EC3C-4C21-9AF6-12723CFAFBFF@kronometrix.org> <20200113140839.GJ11738@Air-de-Roger> <20200114110125.GM11738@Air-de-Roger> X-Mailer: Apple Mail (2.3608.40.2.2.4) X-Rspamd-Queue-Id: 47xtVH0lMYz4Df9 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of sparvu@kronometrix.org designates 95.85.46.90 as permitted sender) smtp.mailfrom=sparvu@kronometrix.org X-Spamd-Result: default: False [0.56 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.19)[-0.193,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; HAS_XAW(0.00)[]; DMARC_NA(0.00)[kronometrix.org]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.02)[-0.025,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(0.58)[ip: (0.35), ipnet: 95.85.0.0/18(0.95), asn: 14061(1.66), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:14061, ipnet:95.85.0.0/18, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jan 2020 14:43:04 -0000 > The first step should be to report those errors, and figure out > whether someone has interest in getting libvirt working on FreeBSD/Xen > and maintaining it in a sane state. If there's no interest we should > drop the Xen option from the libvirt port to not give users false > expectations. Right. Makes sense. I will handle that in next days and make a short = report about it. If libvirt is not an option I would still like to see how Xen compares = with bhyve and kvm for some of our applications and usage.=20 Stefan=