Hi,
> > Do we have already some code for ROM BAR somewhere?
> Henrik Gulbrandsen was working on expansion ROM support last July
> (CC'd).
> He posted his work up on https://www.gulbra.net/freebsd-bhyve/.
Wow! Great news, this is definitely good source to accelerate things!
Have to look at these
On 2020-03-19 11:19, Robert Crowston wrote:
Do we have already some code for ROM BAR somewhere?
Henrik Gulbrandsen was working on expansion ROM support last July
(CC'd). He posted his work up on
https://www.gulbra.net/freebsd-bhyve/.
Yeah, I'm still on the list. I'm just keeping a low profi
> This solved all the problems with BAR allocation.
Nice!
> Do we have already some code for ROM BAR somewhere?
Henrik Gulbrandsen was working on expansion ROM support last July (CC'd). He
posted his work up on https://www.gulbra.net/freebsd-bhyve/.
‐‐‐ Original Message ‐‐‐
On Thursday,
Hello,
You are right about mapping 64-bit BARs.
=== (1) ===
The initial value of PCI_EMUL_MEMBASE64 is 0xD0 and it
corresponds to the 64-bit mmio window set by QWordMemory(...)
in DSDT from pci_bus_write_dsdt(), so guest VM gets from
UEFI BIOS this 64-bit window:
0x00D0-0x0
I suggest you map the BAR into the 32 bit address space, unless you have so
many PCI devices that this is not feasible. Just raise the limit of the special
64 bit handling to 1 GB or something big.
- Many/most(?) consumer BIOS/UEFIs map 64 bit bars into the 32 bit address
space by default, so th
Hello,
Some new findings to share.
1) Changing PCI_EMUL_MEMBASE64 from 0xD0 to any value
*below 0x044000* makes bhyve fail when starting VM with message:
bhyve: failed to initialize BARs for PCI 1/0/0
device emulation initialization error: Cannot allocate memory
2) Having PCI_EM
Hello Peter,
Many thanks for your insight!
Changing PCI_EMUL_MEMBASE64
from 0xD0 to 0x044000 (16Gb guest memory limit)
and PCI_EMUL_MEMLIMIT64
from 0xFD to 0x07 (32Gb host memory limit)
still fails.
From guest dmesg:
...
[mem 0xc000-0x] available for P
Hi Alex,
dmesg | grep "no compatible bridge window"
pci :00:01.0: can't claim BAR 1 [mem 0xd0-0xd00fff 64bit
pref]: no compatible bridge window
...> From what I can read from all the info above,
somehow the requested memory space for BAR1 for that device is
0xd0-0xd0