From owner-freebsd-virtualization@freebsd.org Fri Mar 29 20:08:18 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EBD8D1551024; Fri, 29 Mar 2019 20:08:17 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [65.103.231.193]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D00087784D; Fri, 29 Mar 2019 20:08:16 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 05840C4C00; Fri, 29 Mar 2019 14:09:10 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id U1kDChXJ1Zz0; Fri, 29 Mar 2019 14:09:09 -0600 (MDT) Received: from photon.int.bluestop.org (unknown [65.103.231.197]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Fri, 29 Mar 2019 14:09:09 -0600 (MDT) Subject: Re: Updating uefi-edk2-bhyve To: D Scott Phillips Cc: owner-freebsd-virtualization@freebsd.org, freebsd-virtualization@freebsd.org References: <86muln68ld.fsf@intel.com> <1fe3ca3f-be70-99db-e7c0-35c9194c97e4@bluestop.org> <7e84fd01c3f46268c26f9bab8b9fb9bc@lerctr.org> <33fcf111-fe00-4ec7-8a2f-7c53246d756f@Spark> <86k1gqanx8.fsf@intel.com> <8c63eb87-e3b8-2365-2eaf-a6e36424407c@bluestop.org> <86ftremzar.fsf@intel.com> <4fb370c4-0358-8ca7-67ee-c98fd83d2740@bluestop.org> <86ftra7gza.fsf@intel.com> From: Rebecca Cran Message-ID: <276871db-ef2c-9a5c-2d59-8797e03d241c@bluestop.org> Date: Fri, 29 Mar 2019 14:08:14 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: D00087784D X-Spamd-Bar: ------ X-Spamd-Result: default: False [-6.96 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bluestop.org:s=mail]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-2.97)[ip: (-9.85), ipnet: 65.100.0.0/14(-4.89), asn: 209(-0.04), country: US(-0.07)]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: mail.bluestop.org]; DKIM_TRACE(0.00)[bluestop.org:+]; DMARC_POLICY_ALLOW(-0.50)[bluestop.org,quarantine]; NEURAL_HAM_SHORT(-0.98)[-0.983,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:209, ipnet:65.100.0.0/14, country:US]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Mar 2019 20:08:18 -0000 On 3/29/19 12:29 PM, Rebecca Cran via freebsd-virtualization wrote: > On 3/25/19 3:59 PM, D Scott Phillips wrote: >> >> Yep, makes sense to me. For either of these changes we would want to get >> test converage on basically all functionality, so might as well take >> both changes at once. > > > One thing I noticed is that the SMBIOS information claims it's BHYVE > BIOS v1.00 released 3/14/2014. It would be nice if we could update that. I ran the SCT 2.6 against the updated Bhyve firmware and uploaded the results to https://bluestop.org/files/Summary.log . I'm not sure how the failures compare with either the current firmware or OVMF though, so I'm not sure how useful it is. I've tested FreeBSD, Ubuntu and Windows Server 2016 and all worked, though for some reason the Windows ISO kept hanging during boot for a while, until it just started working. -- Rebecca Cran