From nobody Sun Jun 16 10:41:01 2024 X-Original-To: virtualization@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4W28gr3NQRz5NXF5 for ; Sun, 16 Jun 2024 10:41:12 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Received: from mail.flex-it.com.ua (mail.flex-it.com.ua [193.239.74.7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4W28gr0yTlz4mfs for ; Sun, 16 Jun 2024 10:41:12 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Authentication-Results: mx1.freebsd.org; none Received: from 93.183.208.50.ipv4.datagroup.ua ([93.183.208.50] helo=[192.168.200.135]) by mail.flex-it.com.ua with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.97.1 (FreeBSD)) (envelope-from ) id 1sInJr-000000009y0-3f9b; Sun, 16 Jun 2024 13:41:07 +0300 Content-Type: multipart/alternative; boundary="------------nhFy8XKPvZrE0RAOk43dzaMr" Message-ID: Date: Sun, 16 Jun 2024 13:41:01 +0300 List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-virtualization@freebsd.org Sender: owner-freebsd-virtualization@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Fwd: bhyve passthru problem To: marietto2008@gmail.com References: <38c9656c26fc3cee7ba733168c0fa2cdd01209d9.camel@FreeBSD.org> <92b37bf8-7ef9-4abd-8617-af12fbb35e13@shurik.kiev.ua> <86822716-b32d-4663-9b73-87d7c977b70a@shurik.kiev.ua> Content-Language: uk-UA Cc: virtualization@freebsd.org From: Oleksandr Kryvulia In-Reply-To: X-ACL-Warn: SPF failed. 93.183.208.50 is not allowed to send mail from shurik.kiev.ua. X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:35297, ipnet:193.239.72.0/22, country:UA] X-Rspamd-Queue-Id: 4W28gr0yTlz4mfs This is a multi-part message in MIME format. --------------nhFy8XKPvZrE0RAOk43dzaMr Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 >> 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. > --------------nhFy8XKPvZrE0RAOk43dzaMr Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit 16.06.24 12:55, Mario Marietto:
I've zipped and uploaded my boot directory to my google drive


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)


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.


--------------nhFy8XKPvZrE0RAOk43dzaMr--