Hi all,
> Am 23.03.2018 um 14:19 schrieb Matt Churchyard :
> 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
I can confirm the new firmware does fix the issue for us. Thanks for
the quick resolution. It at least allowed me to script a proper
workaround for our automated tests.It turns out my previous
vm-bhyve workaround was a bad idea, and broke installs. I would
assume vm-bhyve copies the iso to n
On Sat, Mar 24, 2018 at 12:59 AM, Peter Grehan wrote:
> Hi Kyle,
>
>> FYI- I've created PR #2 [1] against the freebsd/uefi-edk2 repository
>> and have confirmed that this fixes the broken-looking firmware along
>> with the booting problem experienced in this thread.
>>
>> [1] https://github.com/fr
Hi Kyle,
FYI- I've created PR #2 [1] against the freebsd/uefi-edk2 repository
and have confirmed that this fixes the broken-looking firmware along
with the booting problem experienced in this thread.
[1] https://github.com/freebsd/uefi-edk2/pull/2
Thanks - merged. I've asked Fabian to update
On Fri, Mar 23, 2018 at 1:34 PM, Kyle Evans wrote:
> On Fri, Mar 23, 2018 at 1:12 PM, Rodney W. Grimes
> wrote:
>>> On Fri, Mar 23, 2018 at 1:04 PM, Rodney W. Grimes
>>> wrote:
>>> > [ Charset UTF-8 unsupported, converting... ]
>>> >> On Fri, Mar 23, 2018 at 9:58 AM, Rodney W. Grimes
>>> >> wro
On Fri, Mar 23, 2018 at 1:12 PM, Rodney W. Grimes
wrote:
>> On Fri, Mar 23, 2018 at 1:04 PM, Rodney W. Grimes
>> wrote:
>> > [ Charset UTF-8 unsupported, converting... ]
>> >> On Fri, Mar 23, 2018 at 9:58 AM, Rodney W. Grimes
>> >> wrote:
>> >> >> On Fri, Mar 23, 2018 at 3:56 AM, Joe Maloney
>
> On Fri, Mar 23, 2018 at 1:04 PM, Rodney W. Grimes
> wrote:
> > [ Charset UTF-8 unsupported, converting... ]
> >> On Fri, Mar 23, 2018 at 9:58 AM, Rodney W. Grimes
> >> wrote:
> >> >> On Fri, Mar 23, 2018 at 3:56 AM, Joe Maloney
> >> >> wrote:
> >> >> > We narrowed the issue down to how vm-bhy
> On Fri, Mar 23, 2018 at 1:04 PM, Rodney W. Grimes
> wrote:
> > [ Charset UTF-8 unsupported, converting... ]
> >> On Fri, Mar 23, 2018 at 9:58 AM, Rodney W. Grimes
> >> wrote:
> >> >> On Fri, Mar 23, 2018 at 3:56 AM, Joe Maloney
> >> >> wrote:
> >> >> > We narrowed the issue down to how vm-bhy
On Fri, Mar 23, 2018 at 1:04 PM, Rodney W. Grimes
wrote:
> [ Charset UTF-8 unsupported, converting... ]
>> On Fri, Mar 23, 2018 at 9:58 AM, Rodney W. Grimes
>> wrote:
>> >> On Fri, Mar 23, 2018 at 3:56 AM, Joe Maloney
>> >> wrote:
>> >> > We narrowed the issue down to how vm-bhyve attaches a nu
[ Charset UTF-8 unsupported, converting... ]
> On Fri, Mar 23, 2018 at 9:58 AM, Rodney W. Grimes
> wrote:
> >> On Fri, Mar 23, 2018 at 3:56 AM, Joe Maloney
> >> wrote:
> >> > We narrowed the issue down to how vm-bhyve attaches a null.iso when
> >> > starting
> >> > the VM.
> >> >
> >>
> >> What
On Fri, Mar 23, 2018 at 9:58 AM, Rodney W. Grimes
wrote:
>> On Fri, Mar 23, 2018 at 3:56 AM, Joe Maloney wrote:
>> > We narrowed the issue down to how vm-bhyve attaches a null.iso when
>> > starting
>> > the VM.
>> >
>>
>> What exactly are the contents of this null.iso? It sounds like we're
>
>
> On Fri, Mar 23, 2018 at 3:56 AM, Joe Maloney wrote:
> > We narrowed the issue down to how vm-bhyve attaches a null.iso when starting
> > the VM.
> >
>
> What exactly are the contents of this null.iso? It sounds like we're
touch "null.iso"
-rw-r--r-- 1 root wheel 0 Dec 3 22:55 /home/vmbhyve
-Original Message-
From: owner-freebsd-virtualizat...@freebsd.org
On Behalf Of Kyle Evans
Sent: 23 March 2018 13:06
To: Joe Maloney
Cc: Warner Losh ; freebsd-virtualization@freebsd.org
Subject: Re: Issue encountered booting FreeBSD STABLE and CURRENT snapshots
with EFI
On Fri, Mar 23
On Fri, Mar 23, 2018 at 3:56 AM, Joe Maloney wrote:
> We narrowed the issue down to how vm-bhyve attaches a null.iso when 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
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 i
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
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: > >
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
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
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 wo
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
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 ?
later,
Peter.
__
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 suspe
23 matches
Mail list logo
