From owner-freebsd-virtualization@freebsd.org Fri Mar 23 08:56:40 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 73CF4F5565A for ; Fri, 23 Mar 2018 08:56:40 +0000 (UTC) (envelope-from jmaloney@ixsystems.com) Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::22f]) (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 0FC75680B2 for ; Fri, 23 Mar 2018 08:56:39 +0000 (UTC) (envelope-from jmaloney@ixsystems.com) Received: by mail-qt0-x22f.google.com with SMTP id g5so656090qth.7 for ; Fri, 23 Mar 2018 01:56:39 -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=dDBiRlqKHM/fFoHLWSYEonARB9KLP/nPx3xxpRaTn+o=; b=MGDyZY5TNzUHWOOVCdQgwLDeRKwSK9M013x+bqK7jItM6aM4DLCzorfydZfi/Jostu 0IkHORm71yIy5SGdkzwvmIaK9Eh6Re6/dZVnx0GWX2nT9LOeUU6P8TZAC2IrsRQBGi23 yTMYZ28yFNxfqHjNTbjMl1jFr1YTys58PYQFDYBVtoT254codvZXD6scyQxW+RAbHTLv Wugfb6ntgAAdCIqqP+qfuwWypM5AvAOyW9/p6RhvChLUGKSD+o+9gpMzAGsqL0shNGTQ KfFkGPlOtn3Z55RwWhR5l6TplCDpc8MU2OY6iFtJVyCsbtJiozYCTHclbCLayxI5+KYe 3Dyw== 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=dDBiRlqKHM/fFoHLWSYEonARB9KLP/nPx3xxpRaTn+o=; b=qQqkQ2isRC4HavEe0YIbkBT+SqMJxVIHavbb9LbAzd7bSvV6Wg25Jp2MFKZ9OkDVVY LZKQsleKUikM3wUH/2h4zaarCT3bweIcprVZwnlnDpzt7UkuprwhhuMlrjK+flKjM2Eh 32197xsUXThaaEIMZmiPjzvkoeCbiqZG+VLWQN+cG9ZUtV2HeuhzUsdwAXiegioC3uIc J7tpJTlyRxDVMx5RX/WRGbiSFEp2xlvo5Vm7jHGGy1DJ7BFAfwVDmsaVeD6HRqkxc5z8 QQ7tbXYiHvSrl8ehFSZ8yEh+VQicn4z6fhYv0VkTZhm1Szu3HYCVcI53PYW7zOaFLxvl uW1A== X-Gm-Message-State: AElRT7EIXw1yXxZ2VBVLl4fnr3TXLOiXS/Ki1YVAcdhNwJrGQUgCzAbN ECwo+90shZuqFAH/3aj6Gnik9HRYui4/ob+SsoS+Nw== X-Google-Smtp-Source: AIpwx48rSUWcv8i0q8REOQHqLh15oOJntM/lRGw/hupbWI5dJ04vE2jVRNPICdFbEaLxbPe81QQKXdcacoWmeKUVXh8= X-Received: by 10.237.35.137 with SMTP id j9mr1878865qtc.181.1521795399152; Fri, 23 Mar 2018 01:56:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.63.119 with HTTP; Fri, 23 Mar 2018 01:56:38 -0700 (PDT) In-Reply-To: References: From: Joe Maloney Date: Fri, 23 Mar 2018 04:56:38 -0400 Message-ID: Subject: Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI To: "araujo@freebsd.org" Cc: Kyle Evans , "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Fri, 23 Mar 2018 08:56:40 -0000 We narrowed the issue down to how vm-bhyve attaches a null.iso when starting the VM. For now a hack like so to vm-bhyve can get around the issue: https://github.com/araujobsd/vm-bhyve/commit/29db2d6c6ec4a29578dc111903107f25a78cdf82 This may simply be an issue with vm-bhyve attaching an invalid iso image to the VM, and I would conclude it is odd that it does so. Or there may still be an issue that affects even the latest 03-22-18 snapshots for example if other media is present when booting with bhyve, or natively. I would need to do some more testing at a later date to confirm but just wanted to pass along what was discovered to be the root cause thus far. On Friday, March 16, 2018, Marcelo Araujo wrote: > 2018-03-16 9:55 GMT+08:00 Kyle Evans : > > > On Thu, Mar 15, 2018 at 8:46 PM, Marcelo Araujo > > > wrote: > > > > > > > > > 2018-03-16 7:07 GMT+08:00 Kyle Evans : > > >> > > >> On Thu, Mar 15, 2018 at 5:01 PM, Kyle Evans > wrote: > > >> > On Thu, Mar 15, 2018 at 4:09 PM, Peter Grehan > > >> > wrote: > > >> >>> I believe the problem may have been introduced with this commit: > > > > > >> >>> https://svnweb.freebsd.org/base/stable/?view=log&pathrev=329114 > > >> >> > > >> >> Any chance of being able to work out where in that list of commits > > in > > >> >> CURRENT the loader stopped working ? > > >> >> > > >> > > > >> > Indeed- if you could work out the exact commit in that range from > head > > >> > that caused it, I wouldn't think it to be a tough fix. After tonight > > >> > I'm out until Sunday, but should have time Sunday or Monday to try > and > > >> > diagnose it further. > > >> > > >> Can one of you try this with boot1.efi+loader.efi built from today's > > >> head stand/? I'm not sure what I'm expecting here since these are > > >> among my first times trying bhyve, but this is what I'm seeing now > > >> (vs. from the mentioned head snapshot where I noted similar behavior > > >> as originally mentioned): > > >> > > >> 1.) Get to loader.efi, menu is good > > >> 2.) Break into loader prompt > > >> 3.) `lsdev`- pager is restricted to the line the prompt is on, so the > > >> output is useless > > >> 4.) `boot` > > >> 5.) "Unhandled ps2 mouse command 0xe1" > > >> > > >> At this point, the boot looks screwed until I VNC into it- it booted > > >> fine here, but the console stopped working after the kernel handoff. > > >> > > >> Thanks, > > >> > > >> Kyle Evans > > >> _______________________________________________ > > >> freebsd-virtualization@freebsd.org mailing list > > >> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > > >> To unsubscribe, send any mail to > > >> "freebsd-virtualization-unsubscribe@freebsd.org" > > > > > > > > > Hi Kyle, > > > > > > I will do that today and report back as soon as I have something. > > > > > > > Thanks! If it's still failing, I think capturing the output of "lsdev" > > and "show currdev" prior to a failed boot might be most helpful just > > to make sure there's not something obviously sketchy happening. > > > > Hi, > > I think we had two bad snapshots! > > I just finished the tests with HEAD and 11-STABLE latest snapshots: > 1) HEAD: FreeBSD-12.0-CURRENT-amd64-20180315-r331001-disc1.iso > 2) Stable: FreeBSD-11.1-STABLE-amd64-20180315-r330998-bootonly.iso > > I have installed it using ZFS and tested using AHCI and virtio-blk. > > So everything worked fine. > Seems those broken snapshots have missed some commits related with EFI. > > > Thank you all. > -- > > -- > Marcelo Araujo (__)araujo@FreeBSD.org > \\\'',)http://www.FreeBSD.org \/ \ ^ > Power To Server. .\. /_) > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" > -- Joe Maloney QA Manager / iXsystems Enterprise Storage & Servers Driven By Open Source