Date: Tue, 21 May 2019 18:44:45 -0400 From: Nick Principe <nap@ixsystems.com> To: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> Cc: John Baldwin <jhb@freebsd.org>, freebsd-virtualization@freebsd.org Subject: Re: Windows 10 guests fail to boot when attempting to passthrough network card Message-ID: <CA%2Bi9KEyctABBsQoh8VOHsasoJ7h3mfKBBKo3aWkm5%2B_mhkqE4g@mail.gmail.com> In-Reply-To: <201905211704.x4LH4rCb080120@gndrsh.dnsmgr.net> References: <23eb543e-68ca-ba6f-de8f-023dac39e41a@FreeBSD.org> <201905211704.x4LH4rCb080120@gndrsh.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 21, 2019 at 1:05 PM Rodney W. Grimes < freebsd-rwg@gndrsh.dnsmgr.net> wrote: > [ Charset UTF-8 unsupported, converting... ] > > 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. > > Thanks and even more reason to pull those out, IMHO > Using John's patches, the Windows 10 guest can successfully boot and see the NIC ports. I've tested it as far as successfully getting link state change in Windows when I connect the two ports of the NIC to each other. I started putting together a second system to test on where I can actually get 40GbE link to another machine, but am running into separate (probably AMD-related) issues. I can successfully boot the Windows 10 guest (though initial configuration of the NICs generated a reboot, perhaps a panic - didn't catch it in time) but connecting the two ports to each other did not result in a link state change in Windows. For now I'll continue to focus on the Intel-based machine that is working well. I may be able to get a 40GbE link tomorrow to test performance. > > > -- > > John Baldwin > -- > Rod Grimes > rgrimes@freebsd.org > _______________________________________________ > > `nap
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2Bi9KEyctABBsQoh8VOHsasoJ7h3mfKBBKo3aWkm5%2B_mhkqE4g>