I'm just getting started using bhyve (on a 13-CURRENT host from Oct 28), and
for the work I'm doing need to use UEFI. However, I'm finding that when booting
FreeBSD 12.0-BETA4 the screen goes blank as FreeBSD takes over the console
after the loader is finished.
The command I'm running is:
sudo
On November 13, 2018 at 8:36:34 AM, Rodney W. Grimes
(freebsd-...@pdx.rh.cn85.dnsmgr.net) wrote:
Since you are using uefi and specifying a graphics console with tcp=,wait
your vm is waiting for a vnc connection to port 5900 to display the
console.
But I connect to VNC, see the loader and
On Tuesday, 13 November 2018 18:57:25 MST Kyle Evans wrote:
> However, because loader-land is funny in a not-ha-ha kind of way, can
> you try replacing loader.efi on your guest VM with the Forth-flavored
> version to rule that out or narrow it down, please?
That didn't help.
As probably expected,
On November 14, 2018 at 2:18:04 PM, Subbsd
(sub...@gmail.com(mailto:sub...@gmail.com)) wrote:
>
> My current host: FreeBSD 13.0-CURRENT r340319 and the problem is
> still present.
Rod was asking about the guest OS version, not the host though.
__
On Wednesday, 14 November 2018 19:56:56 MST Warner Losh wrote:
> What is the ConOut evifar look like? We set serial when the UEFI env says
> to do so.
Booting with:
sudo bhyve -A -P -c 2 -H -m 4G -s 0:0,hostbridge -s 31:0,lpc -s 2,ahci-
cd,FreeBSD-12.0-BETA4-amd64-disc1.iso -s
29,fbuf,tcp=0.0.
On Saturday, 17 November 2018 09:29:34 MST Subbsd wrote:
> Thus, perhaps the root of this problem should be sought in
> uefi-edk2-bhyve the package. Latest CBSD release (12.0.1) fixed this
> problem by disabling serial console. However, CBSD uses an alternative
> boot method for bhyve ( uefi-edk2
This is awesome! Updating to a newer edk2 has been on my todo list for a while.
However I don’t see a BhyvePkg in the first link you posted. And could you
confirm that you got HTTP boot working on FreeBSD as well as Linux and Windows?
I thought loader changes were needed for that to work, to ena
On 3/21/19 6:44 PM, D Scott Phillips wrote:
Hi freebsd-virtualization,
Recently I wanted to be able to do UEFI HTTP Boot in bhyve, so I've
rebased the bhyve firmware up to the latest upstream tag,
edk2-stable201903. You can find the firmware here:
https://gitlab.com/scott-ph/edk2/tree/wip/2019-
On Mar 21, 2019, 9:54 PM -0600, Larry Rosenman , wrote:
> out of curiosity, is there any work being done to move this to later
> LLVM/CLANG?
That’s something else I’m hoping to work on, since gcc 4.8 is very outdated
now. It seems to build fine using gcc 7, but I need to test that it still runs
On 3/22/19 10:12 AM, D Scott Phillips wrote:
You're seeing this firmware triple fault in the DEBUG build of this new
firmware? It seems to be functioning properly for me. Do you get any
serial output before the fault?
I do get quite a bit of output before the fault. I'm running 13-CURRENT
(
On 3/22/19 2:25 PM, D Scott Phillips wrote:
Hmm, I guess it might be some diference in the code generation between
gcc 4.8 and gcc 5.
I've just tested switching from gcc 4.8 to 8.3.0 and everything seems to
work fine - both build and runtime - so I think it may be more
productive to upgrade
On 3/22/19 4:29 PM, Rebecca Cran via freebsd-virtualization wrote:
On 3/22/19 2:25 PM, D Scott Phillips wrote:
Hmm, I guess it might be some diference in the code generation between
gcc 4.8 and gcc 5.
I've just tested switching from gcc 4.8 to 8.3.0 and everything seems
to work fine -
On 3/25/19 3:59 PM, D Scott Phillips wrote:
For either of these changes we would want to get
test converage on basically all functionality, so might as well take
both changes at once.
What testing are you thinking is needed at this point? I guess
installing and running FreeBSD, Linux and Win
On 3/25/19 3:59 PM, D Scott Phillips wrote:
Yep, makes sense to me. For either of these changes we would want to get
test converage on basically all functionality, so might as well take
both changes at once.
One thing I noticed is that the SMBIOS information claims it's BHYVE
BIOS v1.00 rele
On 3/29/19 12:29 PM, Rebecca Cran via freebsd-virtualization wrote:
On 3/25/19 3:59 PM, D Scott Phillips wrote:
Yep, makes sense to me. For either of these changes we would want to get
test converage on basically all functionality, so might as well take
both changes at once.
One thing I
On 3/29/19 9:29 PM, Rodney W. Grimes wrote:
That, iirc, would be the SMBIOS version of ed2k, which yes should
be updated if infact the newer ed2k has a new SBIOS implementation,
if it is still 1.00 implementaton then this needs to be left
alone.
Under OVMF "smbiosview -t 0" shows:
Vendor:
On 3/29/19 2:08 PM, Rebecca Cran via freebsd-virtualization wrote:
I ran the SCT 2.6 against the updated Bhyve firmware and uploaded the
results to https://bluestop.org/files/Summary.log .
I'm not sure how the failures compare with either the current firmware
or OVMF though, so I'
On 3/30/19 1:08 AM, Rodney W. Grimes wrote:
I do not know what the above is, could you elaborate for me?
What is OVMF and what is its relation to bhyve?
OVMF is the Open Virtual Machine Firmware: it's open source (BSD
licensed) firmware for virtual machines. Currently, that means Qemu/KVM.
On 3/30/19 2:37 PM, Rodney W. Grimes wrote:
On 3/30/19 1:08 AM, Rodney W. Grimes wrote:
So it is a edk2 implementation, and can you point me at
the bhyve version of it? The Qemu/KVM version is rather
not relavent to this discussion as that would not work due
to core vmm implementation differ
I was wondering, has anyone done any work on supporting debugging UEFI
code under Bhyve? If not, I can take a look at adapting DebugPkg
(https://code.bluestop.org/w/tianocore/debugging-with-gdb/).
--
Rebecca Cran
___
freebsd-virtualization@freebsd
I've spent some time trying to figure out where and why the UEFI 2.70
firmware is crashing when built with CSM support under Bhyve.
The first thing I noticed is that the code that builds the E820 table
doesn't appear to be finding the location of the EBDA at 0x40E: the
first entry should be so
21 matches
Mail list logo
