From owner-freebsd-virtualization@freebsd.org Thu Mar 15 21:06:33 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 08AC3F538F4 for ; Thu, 15 Mar 2018 21:06:33 +0000 (UTC) (envelope-from jmaloney@ixsystems.com) Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (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 A0E5C78911 for ; Thu, 15 Mar 2018 21:06:32 +0000 (UTC) (envelope-from jmaloney@ixsystems.com) Received: by mail-qk0-x22b.google.com with SMTP id s188so8921099qkb.2 for ; Thu, 15 Mar 2018 14:06:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ixsystems-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=W8nKHsgw8E0VZNKkzNO0EzsWKIeICiCzu/u09OILMR8=; b=hbf7Vv4QVAAUIOeL3m6X5727CBW6CcsHfAet0Hw2rwmv9w5uC/d5z7312B0BqFn1Ho onLEjVj9r9x0VPLLtNMvgMxoVlHYw+duMVLWI7TuKZ0u9xj3hJ7OA1u1IdV+FaQLdQB+ 8jdzppBmyYzqEhHmY5oK4lq6YLFvqKAPSCN71vNavCpyxW5pD2cjJWIrk9QhzpVJ6TKl NzXYjpPiVm2pne16n8pAaonKbocixPnoh8RHWzUVudxz2/XxxkQ5KwYM0Z5TbhqU7gio 3gqfAqCpj8A9FeD/jHlLQ5G5F26ePBULcogYKW8EzPN5sKZcLF9XrlNZ8krCR3NcNHG5 VJ6A== 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=W8nKHsgw8E0VZNKkzNO0EzsWKIeICiCzu/u09OILMR8=; b=uQDML0Cjm94S0SRnoYP2mLlOPd88rcaKO7d/j+K0gh2jlVoTeP5vSUy3mpsmdvdBtS /1jjUtqLRc/gEe2rgkmlIzoU+B3Yg17ysU8EVFTnUWdPu8Iv3XZ6KY9ROEQp75n6qgcx HbqCIi9IBJqtA1pD8fA6LHi4NUBmPaCFpd5P4CTqu9CCP46emYkFS3JpxkbPgLLYAzgX 6ug52XOS4C46RLxLRiikSdHO4kinD72XqnohYP6DdTryYZ6a3hmgGot3CJ1sU8ghnnu+ UA39Phc6uqFKnvvzqEbPanrIkcBA5CecJdnfu53sWeP+h65+4cIKji9duNfyYGJcBlSK gJeg== X-Gm-Message-State: AElRT7HWt2oVXnEiLw24xwlMVhaLYCateySiW/zuHmHxHi5UR11GIk34 C5xcEbMJhPFPkPE4v+fqpqskxKtLkcDsD4eC6i14vb3K X-Google-Smtp-Source: AG47ELtnmJzeygb67hed2hcPxaKTV6bfteg7BOviBX6wpE2muJ8dBlS+hHWq2ortjsiK9DUxg5A/Kz4P32bn22a3Pf0= X-Received: by 10.55.5.8 with SMTP id 8mr15012826qkf.84.1521147991678; Thu, 15 Mar 2018 14:06:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.63.119 with HTTP; Thu, 15 Mar 2018 14:06:31 -0700 (PDT) In-Reply-To: References: From: Joe Maloney Date: Thu, 15 Mar 2018 17:06:31 -0400 Message-ID: Subject: Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI To: freebsd-virtualization@freebsd.org Cc: kevans@freebsd.org, emaste@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:06:33 -0000 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 Unfortunately now something causes that exact same "Failed to start image provided by UFS (14)" error for BHYVE with UEFI. Joe Maloney QA Manager / iXsystems Enterprise Storage & Servers Driven By Open Source 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