From owner-freebsd-virtualization@freebsd.org Tue May 21 22:45:24 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C5AE5159277D for ; Tue, 21 May 2019 22:45:24 +0000 (UTC) (envelope-from nap@ixsystems.com) Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 95080853B0 for ; Tue, 21 May 2019 22:45:23 +0000 (UTC) (envelope-from nap@ixsystems.com) Received: by mail-ed1-x532.google.com with SMTP id m4so696781edd.8 for ; Tue, 21 May 2019 15:45:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ixsystems-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+rb1eTOIf0Pm/b/yuwbUAZWDekxBGQrnxRQ5DDuW8cI=; b=v/7WQ4CBp68jt/i+AGrfeViKRaIM0PPqC60p92SK2UjujCdxZgrQKA8By36C9B55VK jEvMBYL3B2P/6M5cn6NOaB/kiGdNKcquhM5MvGz/yVsST8tq71QOVdTL2H5u0pFwoitA ca7lRSnqZKFwFTEhTpVnwqeveJW77T49QMWdLZQbWk61azlY2uDvXaCiPYnIYJ8vNuW2 p+Zp+lvBqqMRCnCz+y+QV1jdQxAf2og9rwvT/g2Biqb99YdM1lPtugOiYOgdEBQ/azge +ykLXxQy8T6h7+I8ZxtpzH4Diq5FfmzwFHvwLt/HtGs717v0crZJQiHWCgrhTp0z3cr2 Qaew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+rb1eTOIf0Pm/b/yuwbUAZWDekxBGQrnxRQ5DDuW8cI=; b=I+BJyPihP8L5G1RCZBO5jmrRv1axagsPd1gquPc9DuWUkquZIC5rbIDTAHiUli4HqS UIyT5PQZFj9voQoj2IsERVSpeoL43pBAW8OTXbHC7K2dO8S9ehd5go7F6B+p/jCyEJ+0 vEO/VL8HBDXQKggw9ohFL2gC+fFCxwyHxUHFFsn0RRo5cTCKeqIj0kQNWk4BtuElmvMr 3lWERP4wgYqMvdVvE0/4j33L+kSZG/D9zrwVYagFc2izkTipb7ksMcnqOWCGTW8uJEnS /zZWcx7QY8fH3d1bH1igSonGiWqQ2L3JPmJaBfNX/0pibZbcQXS3qpGpWlc1iWWRoJYL KUkQ== X-Gm-Message-State: APjAAAWCnfHsaqRNQDWDT0tR4BV4YPnjX9ZiJQPQ4jHtCj66uQAGfzCY 5v/nLVopRv9AdUav1qsIv8v6fTWrhmzc2jrqvOPynQ== X-Google-Smtp-Source: APXvYqwHWNxqPZeVtoSgZsqm1qXhHILZgaiWZn7JrcPeJRbyI3cMHrhde4uCzjh8zRLQ+qWszaNuwtyHZH8nYVMpZ18= X-Received: by 2002:a17:907:2131:: with SMTP id qo17mr19964198ejb.220.1558478721285; Tue, 21 May 2019 15:45:21 -0700 (PDT) MIME-Version: 1.0 References: <23eb543e-68ca-ba6f-de8f-023dac39e41a@FreeBSD.org> <201905211704.x4LH4rCb080120@gndrsh.dnsmgr.net> In-Reply-To: <201905211704.x4LH4rCb080120@gndrsh.dnsmgr.net> From: Nick Principe Date: Tue, 21 May 2019 18:44:45 -0400 Message-ID: Subject: Re: Windows 10 guests fail to boot when attempting to passthrough network card To: "Rodney W. Grimes" Cc: John Baldwin , freebsd-virtualization@freebsd.org X-Rspamd-Queue-Id: 95080853B0 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ixsystems-com.20150623.gappssmtp.com header.s=20150623 header.b=v/7WQ4CB; dmarc=pass (policy=none) header.from=ixsystems.com; spf=pass (mx1.freebsd.org: domain of nap@ixsystems.com designates 2a00:1450:4864:20::532 as permitted sender) smtp.mailfrom=nap@ixsystems.com X-Spamd-Result: default: False [-6.72 / 15.00]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; DKIM_TRACE(0.00)[ixsystems-com.20150623.gappssmtp.com:+]; MX_GOOD(-0.01)[cached: ALT3.ASPMX.L.GOOGLE.com]; DMARC_POLICY_ALLOW(-0.50)[ixsystems.com,none]; NEURAL_HAM_SHORT(-1.00)[-0.998,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; IP_SCORE(-2.71)[ip: (-9.01), ipnet: 2a00:1450::/32(-2.20), asn: 15169(-2.27), country: US(-0.06)]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[ixsystems-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2.3.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 May 2019 22:45:25 -0000 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