16.06.24 12:55, Mario Marietto:
I've zipped and uploaded my boot directory to my google drive
https://drive.google.com/file/d/1MIw0G4LqducG86rtwSm9GjEWFyuCA-Vx/view?usp=sharing
Try to exchange your boot files with those files. Anyway I'm using the
kernel of FreeBSD 14.0--RELEASE p6 for my cpu /Intel/® /Core/™
/i9/-/9900K + GPU = Nvidia RTX 2080 ti. You can try the default kernel
shipped with FreeBSD 14.0-RELEASE p6 to make it easier. /
This explains all. I am using latest current ))
15.06.24 13:47, Mario Marietto:
Ciao Oleksandr.
I can't produce patches,I'm not a programmer. But I conduct
experiments every day,changing parameters,system files between
different FreeBSD versions,operating systems and tools.
Can't you use virtio-net instead of passing through the physical
network interface,like this for example : -s 13,virtio-net,tap18 \ in
your bhyve guest ?
You can try these bhyve versions : (try both)
https://drive.google.com/drive/folders/14OMOjdyS5NPQ75ISatcpCWegU0udzG0r?usp=sharing
Unfortunately both of your vmm.ko modules fail to load on my system:
KLD vmm.ko: depends on kernel - not available or version mismatch
On Sat, Jun 15, 2024 at 9:17 AM Oleksandr Kryvulia
<[email protected]> wrote:
14.06.24 10:50, Peter Grehan:
>> I don't know why bhyve validates the BAR size. The commit
adding this
>> check is old [1] and doesn't explain it. What bhyve could do is
>> rounding up the BAR size to a full page size when allocating
memory for
>> the BAR.
>>
>> [1] https://github.com/freebsd/freebsd-
>> src/commit/7a902ec0eccc752c9c38533ed123121eaaea1225
>
> At the time, BIOSs would often place device BARs of less than
a page
> size in the same physical page. Since EPT only gives page
granularity,
> this would result in all those devices being available to the
guest
> even if they hadn't been passed through.
>
Peter, can you explain how can I use this device in a guest without
passing through?
--
Mario.
