Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 13 Mar 2020 12:51:21 +0900
From:      Wanpeng Qian <wanpengqian@gmail.com>
To:        Peter Grehan <grehan@freebsd.org>
Cc:        FreeBSD virtualization <freebsd-virtualization@freebsd.org>
Subject:   Re: Passthru a VF to Windows guest cause BSOD, chelsio T520BT, SR-IOV
Message-ID:  <CANBJ%2BxQ9uMyPbKwn6JOjarW8S5TcKGmSyAUrrxeMM25UsxSABw@mail.gmail.com>
In-Reply-To: <8357fd6d-d02d-76bb-712a-e5c330ecf434@freebsd.org>
References:  <CANBJ%2BxRrBw%2BFJ_NPfopnRygH3xVhQ4OzQ0as6d3AdowH7NJsmA@mail.gmail.com> <8357fd6d-d02d-76bb-712a-e5c330ecf434@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Peter

>   Can you try disabling APIC acceleration (which should be available on
> that Xeon E5) ? This can be done on the fly using kenv and
> unloading/reloading vmm.ko (or loader.conf and rebooting)

After disabling tpr_shadowing, the Windows 10 1909 client boots
without the IRQL_NOT_LESS_OR_EQUAL BSoD,
(Windows 10 is very slow without tpr shadowing)

But the driver didn't work.
With Windows 10 built in driver, device status is :

Windows is still setting up the class configuration for this device. (Code 56)

When installing chelsio driver, cause BSoD,
which is SYSTEM_THREAD_EXCEPTION_NOT_HANDLE (chnetx64.sys)

I also try Windows 2012, same as Windows 10, BSoD while installing driver.

And Windows 7 Pro, the chelsio driver didn't have a valid digial signed,
not working.

Thanks

Qian

On Fri, Mar 13, 2020 at 11:06 AM Peter Grehan <grehan@freebsd.org> wrote:
>
> > When I pass the same VF1 to Windows 10 guest, ver 1909, the guest got
> > BSOD during installation. I also try to add VF1 post installation.
> > also got BSOD.
> > the message is IRQL_NOT_LESS_OR_EQUAL.
> > I also try Windows server 2012, during installation of Chelsio Driver, BSOD too.
> >
> > Any suggestions? driver issue or bhyve issue?
>
>   Can you try disabling APIC acceleration (which should be available on
> that Xeon E5) ? This can be done on the fly using kenv and
> unloading/reloading vmm.ko (or loader.conf and rebooting)
>
> kenv hw.vmm.vmx.use_tpr_shadowing=0
> kldunload vmm
> kldload vmm
>
> later,
>
> Peter.
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANBJ%2BxQ9uMyPbKwn6JOjarW8S5TcKGmSyAUrrxeMM25UsxSABw>