Date: Tue, 21 May 2019 09:55:18 -0700 From: John Baldwin <jhb@FreeBSD.org> To: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> Cc: Robert Crowston <crowston@protonmail.com>, freebsd-virtualization@FreeBSD.org Subject: Re: Windows 10 guests fail to boot when attempting to passthrough network card Message-ID: <23eb543e-68ca-ba6f-de8f-023dac39e41a@FreeBSD.org> In-Reply-To: <201905211648.x4LGm5eW079975@gndrsh.dnsmgr.net> References: <201905211648.x4LGm5eW079975@gndrsh.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/21/19 9:48 AM, Rodney W. Grimes wrote: >> On 5/19/19 6:24 AM, Rodney W. Grimes wrote: >>>> Does the card have multiple BARs? Can you send us the output of pciconf -lvb for the card? >>>> >>>> There is a bug in bhyve where if the OS assigns the 0xffffffff sentinel to more than one BAR simultaneously it is not compatible with bhyve?s memory model for the guest. >>> >>> The "we talked" below is myself and Nick talking about exactly that >>> which came from jhb@ pointing out to me in a hall wall >>> conversation here at BSDCan that this is the cause of this >>> problem and is a known issue. >>> >>> Does anyone have fixes for this issue? >> >> I have not tested this at all, but I have a candidate patch to fix the root >> issue at https://github.com/freebsd/freebsd/compare/master...bsdjhb:bhyve_passthrough_barsize > > Could you please factor out the white space changes and do that > seperately and sooner, it clouds the S/N in this review a bit. I can pull those out, but this is just a testing patch still, not yet a commit candidate. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?23eb543e-68ca-ba6f-de8f-023dac39e41a>