Date: Fri, 23 Mar 2018 13:19:30 +0000 From: Matt Churchyard <matt.churchyard@userve.net> To: Kyle Evans <kevans@freebsd.org>, Joe Maloney <jmaloney@ixsystems.com> Cc: Warner Losh <imp@freebsd.org>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: RE: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI Message-ID: <096c805a0aa84bf3bcff3256b9a22a14@SERVER.ad.usd-group.com> In-Reply-To: <CACNAnaFp5VLjF_XWtZTcD2k9VxDBrsXPGv%2BnXbuJx2rMV_m15Q@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> <CAFvkmYMgN%2BCZUX=oPKscX=dNaqTGiqRnjUtmAUHEN3Ncnr7kkw@mail.gmail.com> <CACNAnaFp5VLjF_XWtZTcD2k9VxDBrsXPGv%2BnXbuJx2rMV_m15Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----Original Message----- From: owner-freebsd-virtualization@freebsd.org <owner-freebsd-virtualizatio= n@freebsd.org> On Behalf Of Kyle Evans Sent: 23 March 2018 13:06 To: Joe Maloney <jmaloney@ixsystems.com> Cc: Warner Losh <imp@freebsd.org>; freebsd-virtualization@freebsd.org Subject: Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots= with EFI On Fri, Mar 23, 2018 at 3:56 AM, Joe Maloney <jmaloney@ixsystems.com> wrote= : > We narrowed the issue down to how vm-bhyve attaches a null.iso when=20 > starting the VM. > >What exactly are the contents of this null.iso? It sounds like we're just = ultimately choosing the wrong partition to boot with the null.iso attached.= I'd be interested to see if a loader.efi built with >D13784 [1] applied re= solves this both replacing /boot/loader.efi initially then while installed = on the ESP. >Do note that I'm pretty sure we still had some small outstanding issues wi= th D13784's loader.efi being installed as /boot/loader.efi (with console ha= ndling), so it may not be a good long-term solution, >but this should hopef= ully land in the not-so-distant future. >[1] https://reviews.freebsd.org/D13784 The original reason for null.iso was due to notes on the bhyve wiki https://wiki.freebsd.org/bhyve/Windows " The install.iso is only required for the first boot of Windows Server and= must be removed from the bhyve command after the first boot. Desktop editi= ons of Windows require that a null install.iso file remains and it can be c= reated with touch install.iso" At the time the UEFI support was primarily used for loading Windows guests,= and some desktop versions apparently needed an empty iso file to boot. I w= as not able to verify which guests needed this file and so it was supplied = to all, as it seemed to have no ill effects on the server versions of Windo= ws I was testing with. As mentioned above is this more an issue with the boot process? If bhyve at= some point allows an "empty" cd device to be attached, with the ability to= insert an iso on the fly, like many other hypervisors do, would that trigg= er the same issue? Matt > For now a hack like so to vm-bhyve can get around the issue: > > https://github.com/araujobsd/vm-bhyve/commit/29db2d6c6ec4a29578dc11190 > 3107f25a78cdf82 > > This may simply be an issue with vm-bhyve attaching an invalid iso=20 > image to the VM, and I would conclude it is odd that it does so. Or=20 > there may still be an issue that affects even the latest 03-22-18=20 > snapshots for example if other media is present when booting with=20 > bhyve, or natively. I would need to do some more testing at a later=20 > date to confirm but just wanted to pass along what was discovered to be t= he 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=20 >> > <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=20 >> > >> > <grehan@freebsd.org> >> > >> > wrote: >> > >> >>> I believe the problem may have been introduced with this commit= : >> > >> >>> > > >> > >> >>> https://svnweb.freebsd.org/base/stable/?view=3Dlog&pathrev=3D32= 9 >> > >> >>> 114 >> > >> >> >> > >> >> Any chance of being able to work out where in that list of=20 >> > >> >> commits >> > in >> > >> >> CURRENT the loader stopped working ? >> > >> >> >> > >> > >> > >> > Indeed- if you could work out the exact commit in that range=20 >> > >> > from head that caused it, I wouldn't think it to be a tough=20 >> > >> > fix. After tonight I'm out until Sunday, but should have time=20 >> > >> > Sunday or Monday to try and diagnose it further. >> > >> >> > >> Can one of you try this with boot1.efi+loader.efi built from=20 >> > >> today's head stand/? I'm not sure what I'm expecting here since=20 >> > >> these are among my first times trying bhyve, but this is what=20 >> > >> I'm seeing now (vs. from the mentioned head snapshot where I=20 >> > >> 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,=20 >> > >> 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=20 >> > >> booted fine here, but the console stopped working after the kernel = handoff. >> > >> >> > >> Thanks, >> > >> >> > >> Kyle Evans >> > >> _______________________________________________ >> > >> freebsd-virtualization@freebsd.org mailing list=20 >> > >> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualizatio >> > >> n To unsubscribe, send any mail to=20 >> > >> "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=20 >> > 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=20 >> 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 > _______________________________________________ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/m= ailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebs= d.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?096c805a0aa84bf3bcff3256b9a22a14>