Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI

2018-03-15 Thread Marcelo Araujo 
2018-03-16 9:55 GMT+08:00 Kyle Evans <kev...@freebsd.org>:

> On Thu, Mar 15, 2018 at 8:46 PM, Marcelo Araujo <araujobsdp...@gmail.com>
> wrote:
> >
> >
> > 2018-03-16 7:07 GMT+08:00 Kyle Evans <kev...@freebsd.org>:
> >>
> >> On Thu, Mar 15, 2018 at 5:01 PM, Kyle Evans <kev...@freebsd.org> wrote:
> >> > On Thu, Mar 15, 2018 at 4:09 PM, Peter Grehan <gre...@freebsd.org>
> >> > wrote:
> >> >>> I believe the problem may have been introduced with this commit: > >
> >> >>> https://svnweb.freebsd.org/base/stable/?view=log=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-unsubscr...@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(__)ara...@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-unsubscr...@freebsd.org"

Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI

2018-03-15 Thread 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=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-unsubscr...@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.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI

2018-03-15 Thread Marcelo Araujo 
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=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-
> unsubscr...@freebsd.org"
>

Hi Kyle,

I will do that today and report back as soon as I have something.


Best,
-- 

-- 
Marcelo Araujo(__)ara...@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-unsubscr...@freebsd.org"

Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI

2018-03-15 Thread 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=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-unsubscr...@freebsd.org"

Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI

2018-03-15 Thread Kyle Evans 
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=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.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI

2018-03-15 Thread Kyle Evans 
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=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.
>
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI

2018-03-15 Thread Peter Grehan 

I believe the problem may have been introduced with this commit: > > 
https://svnweb.freebsd.org/base/stable/?view=log=329114
 Any chance of being able to work out where in that list of commits in 
CURRENT the loader stopped working ?


later,

Peter.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots with EFI

2018-03-15 Thread Joe Maloney 
I believe the problem may have been introduced with this commit:

https://svnweb.freebsd.org/base/stable/?view=log=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
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"