running FreePBX SNG7 Official Distro

[Victor Sudakov]

Dear Colleagues,

Has anyone tried to run FreePBX under bhyve? That's what I get trying to
start the vm after a successful automatic install from the ISO image:

Boot Failed. EFI DVD/CDROM
Failed to set MokListRT: Invalid Parameter
Failed to open \EFI\BOOT\grubx64.efi - Not Found
Failed to load image \EFI\BOOT\grubx64.efi: Not Found
start_image() returned Not Found
Boot Failed. EFI Misc Device
.

The vm config:

uefi="yes"
cpu=1
memory=2G
network0_type="virtio-net"
network0_switch="main"
disk0_type="virtio-blk"
disk0_name="disk0"
disk0_dev="zvol"
graphics="yes"
graphics_wait="no"
graphics_res="1280x720"
graphics_port="5909"
graphics_listen="192.168.4.1"
xhci_mouse="yes"
uuid="4c1871cb-56f1-11e9-bdbf-5404a6b49a66"
network0_mac="58:9c:fc:0b:85:76"


-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
2:5005/49@fidonet http://vas.tomsk.ru/


signature.asc
Description: PGP signature

[Bug 235856] FreeBSD freezes on AWS EC2 t3 machines

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235856

--- Comment #5 from Alex Dupre  ---
Created attachment 203370
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203370=edit
dmesg with crash on t3.xlarge

I've changed the instance from a t3.large to a t3.xlarge, and this is the
latest crash I got. This time it wasn't a freeze, the machine rebooted.

No issues on my c5 machines in the last month.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
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: Bhyve with UEFI edk2-stable201903 and CSM support - debugging the crash

[Rodney W. Grimes]

> 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 something like 0x0 to 0x4cf00, but is 0-0 instead.

Since your building a bios there should be a table some
place in some header or c file that builds the EBDA and
puts a pointer to it at 0x40E.  This should be someplace
in the CSM legacy support stuff since the EBSA is a legacy
bios thingy.

You may want to look at the prior port of UEFI/CSM and see
how this was done in that code, it may be a hard coded hack.

> E820[ 0]: 0x?? 0  0x?? 0, Type = 0x1
> E820[ 1]: 0x?? 0  0x?? A, Type = 0x2
> E820[ 2]: 0x?? E  0x? 10, Type = 0x2
> E820[ 3]: 0x? 10  0x? 406000, Type = 0x1
> 
> ...
> 
> 
> As an aside, I'm working on a patch to submit upstream to fix the output 
> so it pads with zeros instead of spaces.
> 
> 
> I've also found that as was probably pretty obvious the system is 
> crashing when trying to call into the CSM to initialize it. It gets as 
> far as calling AsmThunk16 (AsmThunk.nasm), but never appears to reach 
> CsmMain in BhyveCsm16.c. I'll see if I can work on it some more to 
> narrow down the error.

Well I would think if the legacy memory region table is bogus
that would be a good start point to fix.

> 
> Another thing: the GNUmakefile in OvmfPkg/Csm/BhyveCsm16 has "CC ?= 
> gcc", but it appears the build system already sets CC to "cc", which 
> uses the system's clang compiler, which can't compile the assembly code.
> 
> I don't know if we might want to either hard-code CC to "gcc" for now, 
> or have users create a 'cc' symlinks in BaseTools/Bin/FreeBSD-amd64 ?

I would firmcode it, if CC=cc then CC=gcc, this would allow a person
to override CC with something else and still have all the other stuff
work out, except for this specific point that does infact need gcc.

> Rebecca Cran
-- 
Rod Grimes rgri...@freebsd.org
___
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"