From owner-freebsd-current@freebsd.org Sat Feb 15 21:27:53 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 D37912491D5 for ; Sat, 15 Feb 2020 21:27:53 +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 48Kjyd1f9kz4J9Z for ; Sat, 15 Feb 2020 21:27:53 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: by mailman.nyi.freebsd.org (Postfix) id 364A72491D4; Sat, 15 Feb 2020 21:27:53 +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 360EE2491D3 for ; Sat, 15 Feb 2020 21:27:53 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward501p.mail.yandex.net (forward501p.mail.yandex.net [77.88.28.111]) (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 48Kjyb29Rnz4J95 for ; Sat, 15 Feb 2020 21:27:50 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from mxback27g.mail.yandex.net (mxback27g.mail.yandex.net [77.88.29.177]) by forward501p.mail.yandex.net (Yandex) with ESMTP id E9F043500308; Sun, 16 Feb 2020 00:27:47 +0300 (MSK) Received: from localhost (localhost [::1]) by mxback27g.mail.yandex.net (mxback/Yandex) with ESMTP id PWK0wmr91n-RlGerurh; Sun, 16 Feb 2020 00:27:47 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfw.ru; s=mail; t=1581802067; bh=S246K+rn7cBviQXmFx2s+wsbFpSC6fV5Rwx3Nd19b6M=; h=Message-Id:Cc:Subject:In-Reply-To:Date:References:To:From; b=e1ud3pGZ/luK97jJkhBcYub12uKReqY+MtgtwphBcXCXt17DUUkeG+V+Ni8nDKXiF u7b2DuPsAz5NfhotluRUQ9EGeepuME3O1/h2RqElb6GseXU0OU6jwc7knkuwWkk1Lv zvihrmUi0bvi1CS35ZDlbeLS6VBSZq83d6VGdfJ4= Received: by vla5-dcf36e533bf7.qloud-c.yandex.net with HTTP; Sun, 16 Feb 2020 00:27:47 +0300 From: Alexander V. Chernikov To: Toomas Soome Cc: "current@FreeBSD.org" In-Reply-To: References: <9999721581797997@iva4-35f072fa8e4e.qloud-c.yandex.net> Subject: Re: 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 21:27:47 +0000 Message-Id: <3620311581802067@vla5-dcf36e533bf7.qloud-c.yandex.net> Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=utf-8 X-Rspamd-Queue-Id: 48Kjyb29Rnz4J95 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ipfw.ru header.s=mail header.b=e1ud3pGZ; dmarc=none; spf=pass (mx1.freebsd.org: domain of melifaro@ipfw.ru designates 77.88.28.111 as permitted sender) smtp.mailfrom=melifaro@ipfw.ru X-Spamd-Result: default: False [-6.28 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[ipfw.ru:s=mail]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:77.88.0.0/18]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[ipfw.ru]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[ipfw.ru:+]; RCPT_COUNT_TWO(0.00)[2]; IP_SCORE(-3.68)[ip: (-9.76), ipnet: 77.88.0.0/18(-4.83), asn: 13238(-3.83), country: RU(0.01)]; FREEMAIL_TO(0.00)[me.com]; RCVD_IN_DNSWL_LOW(-0.10)[111.28.88.77.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13238, ipnet:77.88.0.0/18, country:RU]; RCVD_TLS_LAST(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 21:27:53 -0000 15.02.2020, 20:44, "Toomas Soome" : >>  On 15. Feb 2020, at 22:19, Alexander V. Chernikov wrote: >> >>  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? > > We do not do secure boot. However, there is known issue I am trying to fix. You can try to run from ok prompt: ls and then boot. Got it. thank you for the prompt reply! Any issue/review/code part/etc I can subscribe to get the notifications? I switched the VM to version 16, jumped to the loader prompt, entered "ls", then "boot". The result is still the "The firmware encountered an unexpected exception" message. Do I need to install the latest boot loader/do something else to workaround the issue? I'm not blocked in any way with it, version 15 works just fine, just want to ensure this is the same problem. Thank you! > > rgds, > toomas > >>  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 >> >>  _______________________________________________ >>  freebsd-current@freebsd.org mailing list >>  https://lists.freebsd.org/mailman/listinfo/freebsd-current >>  To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"