Date: Fri, 23 Mar 2018 04:56:38 -0400 From: Joe Maloney <jmaloney@ixsystems.com> To: "araujo@freebsd.org" <araujo@freebsd.org> Cc: Kyle Evans <kevans@freebsd.org>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI Message-ID: <CAFvkmYMgN%2BCZUX=oPKscX=dNaqTGiqRnjUtmAUHEN3Ncnr7kkw@mail.gmail.com> In-Reply-To: <CAOfEmZgK8_g8pQdrM0kCjspnquVF7K7i2GPwB-60Eb7h5YPD%2BQ@mail.gmail.com> References: <CAFvkmYM=YOAHGqA4H15jX69h2B7vWQ7LrkpcjVUNZri5UCG9aQ@mail.gmail.com> <CAFvkmYMJFJUr38pM=3S4=f%2B=rvL4rXct3YBbqWp8zTJ5JWrBXQ@mail.gmail.com> <dfc20018-3120-704f-7c18-597600f9cdc8@freebsd.org> <CACNAnaHc43PhfsXTLxpcwjede0pQoeGOQUpO3ohTLbos-i_SRw@mail.gmail.com> <CACNAnaGpX9%2BFG-_Y2bNAXON_-03DebudCuYuRQPv4_XBSpvuyg@mail.gmail.com> <CAOfEmZhTrk7jg9SV88BhFw0oLqEPgr9-1yzwQvrFSrz2RqSSRg@mail.gmail.com> <CACNAnaGK66vi5DepZKr9163YykO7%2Bz55dbqbupjXhWjbzUv8FA@mail.gmail.com> <CAOfEmZgK8_g8pQdrM0kCjspnquVF7K7i2GPwB-60Eb7h5YPD%2BQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <araujobsdport@gmail.com> wrote: > 2018-03-16 9:55 GMT+08:00 Kyle Evans <kevans@freebsd.org>: > > > On Thu, Mar 15, 2018 at 8:46 PM, Marcelo Araujo <araujobsdport@gmail.com > > > > wrote: > > > > > > > > > 2018-03-16 7:07 GMT+08:00 Kyle Evans <kevans@freebsd.org>: > > >> > > >> On Thu, Mar 15, 2018 at 5:01 PM, Kyle Evans <kevans@freebsd.org> > wrote: > > >> > On Thu, Mar 15, 2018 at 4:09 PM, Peter Grehan <grehan@freebsd.org> > > >> > 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 <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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFvkmYMgN%2BCZUX=oPKscX=dNaqTGiqRnjUtmAUHEN3Ncnr7kkw>