From owner-freebsd-virtualization@freebsd.org Thu Mar 15 21:11:35 2018 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 72F34F53F2B for ; Thu, 15 Mar 2018 21:11:35 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-lf0-f43.google.com (mail-lf0-f43.google.com [209.85.215.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DC51C78CDA; Thu, 15 Mar 2018 21:11:34 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-lf0-f43.google.com with SMTP id g13-v6so1324323lfe.10; Thu, 15 Mar 2018 14:11:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=UGhDUlqR7PD7JDnP0Qb3gnnNLHF0HQNFhwFFysWdNXE=; b=cV7lZXCErvqhgio8gZSEISwvUGScM9yUX0RTyNvidPXiMWkRNX8B8VO5RrietYObOC Dt7brCN22kPPqfgDzVQ4X9bWPSaP1vx9FZWOqg6MXayRSnHmx7qvNM7ohaBQrRQZyoZg BKsEbcZ9dzGgIPD+E5Z8l9XfpS2RnlgOiyT/3g3mwBdiArtwu2ucg9hoXrnCg/9LG9jT xh/zUIsM/95U86i84/mzo5wZQ0HDoOG1nQfe36K6qvgU07jn85pPcx97zpG7qRSbi0ib lTAFYXt8WHnwQVssZbascCRtYWF30gNnrjSUnBJXej3U02HzP5w+DdEsJiDJ/VnmUPt3 jgZA== X-Gm-Message-State: AElRT7G41NknqU1Qj7EYgv/RL4Lwq9auZPvseFjjcExi9B9qYthCu5BR J5zGEVZd7VcQsjXGY4/QqD5fDbKtxYE= X-Google-Smtp-Source: AG47ELtv3UcQaHHv4CE3vjJU4HA26m6FXV9bSRjjdV6EZI1Q5EPN7rfqXsRsSuSVSKKe3R4VNpd9wg== X-Received: by 10.46.7.80 with SMTP id i16mr7110952ljd.78.1521148286692; Thu, 15 Mar 2018 14:11:26 -0700 (PDT) Received: from mail-lf0-f53.google.com (mail-lf0-f53.google.com. [209.85.215.53]) by smtp.gmail.com with ESMTPSA id 63-v6sm1381829lfr.61.2018.03.15.14.11.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Mar 2018 14:11:26 -0700 (PDT) Received: by mail-lf0-f53.google.com with SMTP id e5-v6so8269681lfb.7; Thu, 15 Mar 2018 14:11:26 -0700 (PDT) X-Received: by 2002:a19:9e95:: with SMTP id h143-v6mr7812178lfe.129.1521148286171; Thu, 15 Mar 2018 14:11:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.54.1 with HTTP; Thu, 15 Mar 2018 14:11:05 -0700 (PDT) In-Reply-To: References: From: Kyle Evans Date: Thu, 15 Mar 2018 16:11:05 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI To: Joe Maloney Cc: freebsd-virtualization@freebsd.org, Ed Maste , tsoome@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 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: Thu, 15 Mar 2018 21:11:35 -0000 On Thu, Mar 15, 2018 at 4:06 PM, Joe Maloney wrote: > On Wed, Mar 14, 2018 at 5:55 PM, Joe Maloney wrote: >> Hello everyone, >> Today after we attempted to merge the latest 11-STABLE into FreeNAS we >> found an issue with EFI boot during the testing process. >> >> To narrow done the issue I have tested the following images: >> https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180307-r330606-disc1.iso >> https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/11.1/FreeBSD-11.1-STABLE-amd64-20180307-r330605-disc1.iso >> >> To summarize I setup a bhyve VM with EFI, and graphics. Install with >> UFS, and ZFS work. >> >> After install during the boot the following message appears if ZFS is used: >> Failed to start image provided by ZFS (14) >> >> If UFS is used during the install here is what the message looks like >> on first boot: >> Failed to start image provided by UFS (14) >> >> Here is a screenshot showing the issue for ZFS: >> https://imgur.com/a/rQRck >> >> If bhyveload is used there is no issue booting. From what I can tell >> it is only if the EFI firmware is used even with graphics mode off. >> This has affected both CURRENT, and the latest 11-STABLE snapshot >> which are linked above. >> >> I will be out of office at the end of the week for several weeks, and >> may be unable to respond to further replies right away. Either way I wanted to >> make the project aware while others at iX look into this Thanks. >> >> Joe Maloney >> QA Manager / iXsystems >> Enterprise Storage & Servers Driven By Open Source > > I believe the problem may have been introduced with this commit: > > https://svnweb.freebsd.org/base/stable/?view=log&pathrev=329114 > > I can build an 11-STABLE image prior to that commit, and I do not > exhibit the booting issues with bhyve using EFI. That r329114 commit > does not build at all so I suspect it, or something after it involving > loader work based on feedback from other iX engineers. > > What led me to start looking at this time period was this bug which > references a large merge that address the same issue for RPI3: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216940 Given how that PR went, CC'ing tsoome@ who diagnosed the RPi3 problem -- he's good at these kind of things. =) > > Unfortunately now something causes that exact same "Failed to start > image provided by UFS (14)" error for BHYVE with UEFI. >