From owner-freebsd-current@freebsd.org Wed Sep 18 15:45:15 2019 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 D3EDB12199C for ; Wed, 18 Sep 2019 15:45:15 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 46YPSV6Y6fz4TLq for ; Wed, 18 Sep 2019 15:45:14 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 4B28D21FF3 for ; Wed, 18 Sep 2019 11:45:14 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 18 Sep 2019 11:45:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=B VDrx2DI+9Q8LA17tgBYwJaeCUq/TyiGpmiYetTrYf4=; b=h7vLJKor/BuuqIoTL Q8mVwDEV7VWwrjxoDVhitBHfrx5Pj6dmY5V3m55X54JNuaiHSr1uFB2qpZYpfGa0 MJqt7hz6m6T2xojsdcQyRxklh41QU1L2pIzUL934OJArgE8d7JvWFlyKtIYYrdif vqUghf6B/lL1l/+oYVKDB1KwqEA+bO3YadZOWWhcXJyyczo5aChuWey7axNwT8sD gO7dJ2WM7QPMQ6pmh6jtE8caQ4lpEIqB+KovYNm6KYT/kcwakE9LsE05QDi2mL/u Cj/nawtc9gap7fOEuTrsY1cMwJCRjP5TfNFYWQoUszo7iItRJTL/9X/vKvlMokws 9Go9A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=BVDrx2DI+9Q8LA17tgBYwJaeCUq/TyiGpmiYetTrY f4=; b=D/+1dSn95nd5AsACrwUZOoCjOmy7mdbZCmm2UgQT7jBw11kn+v4Nzyv5V qU5MXUJE0DN0WKB1rQ+ocLLXPJZeeR1M9UDcMnzHCjC6V/EFQ5rKH+cM6X9T1+mF fPAubXsFu6kIkmhdo4c6Pw5TsRIVHZV1ROe15XMJZWdUNMjwSKDlwXkd4DogXzJe dmLTOWrL7luH9Oq9ACYY7+D7hMNEy8S01yO7oCciJEXzNgPrM8B/SYtAWUeas26I F50aqWoCuz1J2qLOoZoLhvMcUh92BH3kIKs+wDUCMpenzayJmRbyhgcd4OqlphTA M40mVIP0BW+3LmZfrdCxTLTRWt+Ag== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudekgdeludcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesthekre dttdefjeenucfhrhhomhepjghurhhiucfrrghnkhhovhcuoeihuhhrihhpvheshihurhhi phhvrdhnvghtqeenucfkphepkeehrddujedvrdehgedruddugeenucfrrghrrghmpehmrg hilhhfrhhomhephihurhhiphhvseihuhhrihhpvhdrnhgvthenucevlhhushhtvghrufhi iigvpedt X-ME-Proxy: Received: from [192.168.1.11] (unknown [85.172.54.114]) by mail.messagingengine.com (Postfix) with ESMTPA id 70984D60062 for ; Wed, 18 Sep 2019 11:45:13 -0400 (EDT) Subject: Re: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO To: freebsd-current References: <3978E5B5-CAB1-4214-AF9B-757BE1BEA923@me.com> From: Yuri Pankov Message-ID: Date: Wed, 18 Sep 2019 18:45:11 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: <3978E5B5-CAB1-4214-AF9B-757BE1BEA923@me.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 46YPSV6Y6fz4TLq X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yuripv.net header.s=fm1 header.b=h7vLJKor; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=D/+1dSn9; dmarc=none; spf=pass (mx1.freebsd.org: domain of yuripv@yuripv.net designates 66.111.4.26 as permitted sender) smtp.mailfrom=yuripv@yuripv.net X-Spamd-Result: default: False [-6.06 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[yuripv.net:s=fm1,messagingengine.com:s=fm3]; RECEIVED_SPAMHAUS_PBL(0.00)[114.54.172.85.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.26:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[yuripv.net]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; IP_SCORE(-3.46)[ip: (-9.73), ipnet: 66.111.4.0/24(-4.85), asn: 11403(-2.68), country: US(-0.05)]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yuripv.net:+,messagingengine.com:+]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[26.4.111.66.list.dnswl.org : 127.0.5.1] 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: Wed, 18 Sep 2019 15:45:15 -0000 Toomas Soome wrote: > > >> On 18 Sep 2019, at 18:01, Yuri Pankov wrote: >> >> I have tested several snapshot ISOs available for download: >> >> FreeBSD-13.0-CURRENT-amd64-20190822-r351363-disc1.iso - OK >> FreeBSD-13.0-CURRENT-amd64-20190829-r351591-disc1.iso - OK >> FreeBSD-13.0-CURRENT-amd64-20190906-r351901-disc1.iso - FAIL >> FreeBSD-13.0-CURRENT-amd64-20190913-r352265-disc1.iso - FAIL >> >> FAIL being VM shutdown after loading kernel/modules and displaying "EFI framebuffer information". Relevant messages in the VM log are rather unhelpful: >> >> 2019-09-18T14:47:12.397Z| vcpu-0| I125: Guest: Firmware has transitioned to runtime. >> 2019-09-18T14:47:12.434Z| vcpu-0| I125: Msg_Post: Error >> 2019-09-18T14:47:12.434Z| vcpu-0| I125: [msg.efi.exception] The firmware encountered an unexpected exception. The virtual machine cannot boot. >> >> Any hints on debugging this further? > > Im not really sure about debugging; I can not tell about early kernel, but I’d check if the kernel/module locations conflict with efi memory map items… > > The same issue can be seen with vmware fusion, it is not 100% repeatable but I’d say, 95%, starting grab_faults, perhaps ls or some other random command, and boot -v may actually start the system up. OK. It's 100% reproducible here, going from 20190829 (which works) to 20190906 (which doesn't), so I was wondering if anything in r351591-r351901 range could be pointed at as a likely offender.