Re: running FreePBX SNG7 Official Distro
Rodney W. Grimes wrote: [dd] > > > > root@mfsbsd:~ # find /mnt/ -name grubx64.efi > > /mnt/EFI/centos/grubx64.efi > > > > Who is to blame, bhyve or FreePBX's installer? > > > > How can I tell bhyve's UEFI loader to look for grubx64.efi in a > > different place? Or look for a different loader? > > > > Who says that the image to load should be "\EFI\BOOT\grubx64.efi" and > > not "\EFI\BOOT\BOOTX64.EFI" for example? > > I can not quickly answer that, but lets try the short quick fix > and simply copy this file to the right place and see if that > gets you up and running. Yes, copying grubx64.efi to "\EFI\BOOT\" does get the guest up and running (I used mfsbsd from a different VM to manipulate the EFI partition). Moreover, I waited (for a long time!) for the EFI interactive shell prompt and with a few commands: Shell> fs0 FS0:\> cd \EFI\centos FS0:\EFI\centos\> grubx64.efi I also managed to boot the guest OS all right. But naturally, the latter fix worked till next reboot only, I don't know how to save the new EFI setup in the guest's configuration. The hardware UFI BIOSes I've seen so far (not many, I must admit) permitted me to save which efi binary I would prefer to boot next time. > That would also tell us that we have > what is actually a common efi system failure problem in that > stuff looks in the wrong place. It seems so. > I have read many an install > instruction that just says copy this file to these too places > as some bioses look for it in one place and others look for it > someplace else. I would very much appreciate a link to some such instruction about uefi-edk2-bhyve: namely how and where it looks for what on boot, and if I can create a menu for example, or change its startup procedure. I can guess that it looks for a FAT16 partition in the GPT with the type "efi" but the rest is a mystery for me. Why is it trying to find "grubx64.efi" and not the default "boot64.efi" (which is present), for example? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ signature.asc Description: PGP signature
Re: emulated PCI device BAR size
> On Sat, Mar 23, 2019 at 6:44 PM Jason Tubnor wrote: > > > > > > > > On Sun., 24 Mar. 2019, 6:35 am Chuck Tuffli, wrote: > >> > >> On Mon, Mar 18, 2019 at 10:15 AM Chuck Tuffli wrote: > >> > >> > > >> > So my question is how to best fix this. The easiest would be to add a > >> > check to the BAR size calculation in pci_nvme.c along the lines of: > >> > #define NVME_MMIO_SPACE_MIN(1 << 14) > >> > ... > >> > pci_membar_sz = MAX( , > >> > NVME_MMIO_SPACE_MIN); > >> > >> I went down this route and have a patch up for review > >> (https://reviews.freebsd.org/D19676) if anyone is interested. > >> > >> --chuck > > > > > > I've built and installed this patch on FreeBSD > > 12.0-STABLE-amd64-20190314-r345117. Testing occurred against Windows 10 > > Pro guest with a presented NVMe bhyve device and all IO transactions worked > > without issue. > > > > Can this be committed to head and MFD to 12-STABLE. Thanks! > > Committed with r345956. MFC in 2 weeks if nothing pops up. Thanks > again for all your testing! A small prod Chuck you should of mentioned Jason in the commit message for his testing work. I know it is easy to forget this, but it is the right thing to do. Jason, I'll thank you here, in a more personal maner, for working with Chuck on getting this fixed. Thanks, -- 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"
Re: running FreePBX SNG7 Official Distro
-- Start of PGP signed section. > Victor Sudakov wrote: > > > > 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 > > Below are the partitions the automatic installer has created (looking at > them from another vm): > > root@mfsbsd:~ # gpart show vtbd1 > => 34 41942973 vtbd1 GPT (20G) > 34 2014 - free - (1.0M) > 2048186368 1 efi (91M) > 188416 4096000 2 ms-basic-data (2.0G) >4284416 37654528 3 linux-lvm (18G) > 41938944 4063 - free - (2.0M) > > If I "mount_msdosfs /dev/vtbd1p1 /mnt/" I see that grubx64.efi is not > where bhyve expects to find it: > > root@mfsbsd:~ # find /mnt/ -name grubx64.efi > /mnt/EFI/centos/grubx64.efi > > Who is to blame, bhyve or FreePBX's installer? > > How can I tell bhyve's UEFI loader to look for grubx64.efi in a > different place? Or look for a different loader? > > Who says that the image to load should be "\EFI\BOOT\grubx64.efi" and > not "\EFI\BOOT\BOOTX64.EFI" for example? I can not quickly answer that, but lets try the short quick fix and simply copy this file to the right place and see if that gets you up and running. That would also tell us that we have what is actually a common efi system failure problem in that stuff looks in the wrong place. I have read many an install instruction that just says copy this file to these too places as some bioses look for it in one place and others look for it someplace else. -- 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"
Re: emulated PCI device BAR size
On Sat, Mar 23, 2019 at 6:44 PM Jason Tubnor wrote: > > > > On Sun., 24 Mar. 2019, 6:35 am Chuck Tuffli, wrote: >> >> On Mon, Mar 18, 2019 at 10:15 AM Chuck Tuffli wrote: >> >> > >> > So my question is how to best fix this. The easiest would be to add a >> > check to the BAR size calculation in pci_nvme.c along the lines of: >> > #define NVME_MMIO_SPACE_MIN(1 << 14) >> > ... >> > pci_membar_sz = MAX( , >> > NVME_MMIO_SPACE_MIN); >> >> I went down this route and have a patch up for review >> (https://reviews.freebsd.org/D19676) if anyone is interested. >> >> --chuck > > > I've built and installed this patch on FreeBSD > 12.0-STABLE-amd64-20190314-r345117. Testing occurred against Windows 10 Pro > guest with a presented NVMe bhyve device and all IO transactions worked > without issue. > > Can this be committed to head and MFD to 12-STABLE. Thanks! Committed with r345956. MFC in 2 weeks if nothing pops up. Thanks again for all your testing! --chuck https://svnweb.freebsd.org/changeset/base/345956 ___ 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: running FreePBX SNG7 Official Distro
Victor Sudakov wrote: > > 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 Below are the partitions the automatic installer has created (looking at them from another vm): root@mfsbsd:~ # gpart show vtbd1 => 34 41942973 vtbd1 GPT (20G) 34 2014 - free - (1.0M) 2048186368 1 efi (91M) 188416 4096000 2 ms-basic-data (2.0G) 4284416 37654528 3 linux-lvm (18G) 41938944 4063 - free - (2.0M) If I "mount_msdosfs /dev/vtbd1p1 /mnt/" I see that grubx64.efi is not where bhyve expects to find it: root@mfsbsd:~ # find /mnt/ -name grubx64.efi /mnt/EFI/centos/grubx64.efi Who is to blame, bhyve or FreePBX's installer? How can I tell bhyve's UEFI loader to look for grubx64.efi in a different place? Or look for a different loader? Who says that the image to load should be "\EFI\BOOT\grubx64.efi" and not "\EFI\BOOT\BOOTX64.EFI" for example? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ signature.asc Description: PGP signature
