Re: bhyve passthru problem
- Reply: Mario Marietto : "Fwd: bhyve passthru problem"
- In reply to: Mario Marietto : "Re: bhyve passthru problem"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 16 Jun 2024 08:12:50 UTC
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 > <shuriku@shurik.kiev.ua> 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.