From owner-freebsd-current@freebsd.org Sat Feb 15 20:20:04 2020 Return-Path: Delivered-To: freebsd-current@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 05E0924769B for ; Sat, 15 Feb 2020 20:20:04 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 48KhSM3dpHz3P1M for ; Sat, 15 Feb 2020 20:20:03 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: by mailman.nyi.freebsd.org (Postfix) id 7AC7F24769A; Sat, 15 Feb 2020 20:20:03 +0000 (UTC) Delivered-To: current@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 79609247699 for ; Sat, 15 Feb 2020 20:20:03 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward100o.mail.yandex.net (forward100o.mail.yandex.net [37.140.190.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 48KhSK4DXWz3P10 for ; Sat, 15 Feb 2020 20:20:00 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from mxback5o.mail.yandex.net (mxback5o.mail.yandex.net [37.140.190.19]) by forward100o.mail.yandex.net (Yandex) with ESMTP id 0A79A4AC195C for ; Sat, 15 Feb 2020 23:19:58 +0300 (MSK) Received: from localhost (localhost [::1]) by mxback5o.mail.yandex.net (mxback/Yandex) with ESMTP id hE4uEficPt-JvLiMcSn; Sat, 15 Feb 2020 23:19:57 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfw.ru; s=mail; t=1581797997; bh=q47FFgi/vVv3II/2lqiWQyFxuagk3PvChGUECFS8IXo=; h=Message-Id:Date:Subject:To:From; b=rzB4C7Ouz4V2Ijj6pLRw5hxjzHynVQI4GFXO+GChCqCHQVOFiL2kW4kM8unQwuKJD OJTfg1ETyZ/cVaLKi4Tbmun40heATHfhXccQWHH0S3pRS26ydWKzRDaY4+BuXBehZa /X+GjrB3hvjeN0/FASPpEmdWecENrI/GSy4yIgzk= Received: by iva4-35f072fa8e4e.qloud-c.yandex.net with HTTP; Sat, 15 Feb 2020 23:19:57 +0300 From: Alexander V. Chernikov To: "current@FreeBSD.org" Subject: current does not boot on vmware fusion 11 MIME-Version: 1.0 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sat, 15 Feb 2020 20:19:57 +0000 Message-Id: <9999721581797997@iva4-35f072fa8e4e.qloud-c.yandex.net> Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Rspamd-Queue-Id: 48KhSK4DXWz3P10 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ipfw.ru header.s=mail header.b=rzB4C7Ou; dmarc=none; spf=pass (mx1.freebsd.org: domain of melifaro@ipfw.ru designates 37.140.190.180 as permitted sender) smtp.mailfrom=melifaro@ipfw.ru X-Spamd-Result: default: False [-6.25 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[ipfw.ru:s=mail]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:37.140.128.0/18]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; DMARC_NA(0.00)[ipfw.ru]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; IP_SCORE(-3.65)[ip: (-9.57), ipnet: 37.140.128.0/18(-4.87), asn: 13238(-3.83), country: RU(0.01)]; DKIM_TRACE(0.00)[ipfw.ru:+]; TO_DN_EQ_ADDR_ALL(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[180.190.140.37.list.dnswl.org : 127.0.5.1]; RWL_MAILSPIKE_POSSIBLE(0.00)[180.190.140.37.rep.mailspike.net : 127.0.0.17]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13238, ipnet:37.140.128.0/18, country:RU]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Feb 2020 20:20:04 -0000 Hi folks, I upgraded vmware fusion to version 11 recently and noticed that my -amd64 VM stops booting immediately after printing EFI framebuffer information. VM pops up a message stating that "The firmware encountered an unexpected exception. The virtual machine cannot boot." Further digging revealed that the fusion upgrade bumped vmware virtual HW version to 16. Downgrading it to version 15 enabled VM to work again as expected. Description of HWv16 include "UEFI Secure Boot" as one of the declared features, which looks like the potential candidate reason. The full feature list is available below. How can I debug this further? Details: Host: macbook pro 2017, Intel core i7, Mojave 10.14.6 VM: r357812, amd64. Vmware Fusion 11.5.1 (15018442) Full VM output before the error: Loading kernel... /boot/kernel/kernel text=0x1562084 data=0xe0 data=0x1b5158+0x449ea8 syms=[0x8+0x 174e70+0x8+0x19408f] Loading configured modules... can't find I/boot/entropy' Start @ 0xffffffff80369000 ... EFI framebuffer information: adds, size 0xf0000000, 0x300000 dimensions 1024 x 768 stride 1024 masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000 - HWv16 description from https://blogs.vmware.com/teamfusion : Included in HWv16 are: Improved Virtual NVMe Device Performance Important Security Fixes (Spectre, Meltdown and L1TF) Virtual Trusted Platform Module UEFI Secure Boot IOMMU VBS Support (guest only) /Alexander