From owner-freebsd-virtualization@FreeBSD.ORG Sat Nov 29 14:44:43 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 13182DE8 for ; Sat, 29 Nov 2014 14:44:43 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 833C0EFB for ; Sat, 29 Nov 2014 14:44:42 +0000 (UTC) Received: from moby.local ([109.193.238.174]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0M97Nh-1XkaG50BbB-00CUkK; Sat, 29 Nov 2014 15:44:40 +0100 Message-ID: <5479DBD8.1090009@gmx.com> Date: Sat, 29 Nov 2014 15:44:40 +0100 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Anish Gupta Subject: Re: bhyve: Unsupported MSI-X configuration: 2/0/0 References: <5478E4C4.3080203@gmx.com> <1B9C5228-5549-412C-AAE9-5053C86EDB9D@gmail.com> In-Reply-To: <1B9C5228-5549-412C-AAE9-5053C86EDB9D@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:MACG0XFEE7cdAAk+A8ecvy/6ilmsxZzNC0xa3LK1k8VoauyVF07 Lt8vnL777BLBmxJ17kjA02M0e1ExCeduzduwnMh/qusFG6sXh1UpqyoH4wHef3tAyQilN+N HR3V4sTZrckss4bTbx0GIzjdHZKaoYER4qn538e7YGLLI3GrjelRnEJA8wGrsTzerlftDxv v+G9+Bvi7r8faW+aknx4Q== X-UI-Out-Filterresults: notjunk:1; Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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: Sat, 29 Nov 2014 14:44:43 -0000 On 11/29/14 06:02, Anish Gupta wrote: >>> bge0@pci0:2:0:0: class=0x020000 card=0x06471025 >>> chip=0x16b514e4 rev=0x10 hdr=0x00 >>> sdhci_pci0@pci0:2:0:1: class=0x080501 card=0x06471025 >>> chip=0x16bc14e4 rev=0x10 hdr=0x00 >>> none2@pci0:2:0:2: class=0x088000 card=0x06471025 >>> chip=0x16be14e4 rev=0x10 hdr=0x00 >>> none3@pci0:2:0:3: class=0x088000 card=0x06471025 >>> chip=0x16bf14e4 rev=0x10 hdr=0x00 > > Passthrough stub driver is part of vmm.ko and if it was present early in > boot, you should see ppt@pciD:B:S:F[Domain:Bus:Slot:Function] in > pciocnf list above. Given that bge driver claimed 2/0/0, most likely > vmm.ko failed to load or probably was not present. Do you have > vmm_load=“YES” in /boot/loader.conf as mentioned in > https://wiki.freebsd.org/bhyve/pci_passthru? Yes. To make testing easier: I removed everything from loader.conf and I removed a few drivers(bge and a few others) that were built-in the kernel, so the host kernel won't use them and now I am testing with kenv and loading and unloading vmm.ko. I always see the correct ppt devices in the dmesg when vmm.ko is loaded. > > If you already have loader.conf configured correctly, you can try to > manually load vmm.ko once system is booted and see dmesg for any problem > in loading it like kernel mismatch, missing symbol[One common I usually > encounter is KTRACE define in sys/modules/vmm/Makefile but kernel config > is missing “option KTRACE”] etc. Everything seems ok here as well, I get nothing but the ppt devices. One thing I noticed and seems different is this: > ppt0 mem 0xb3430000-0xb343ffff,0xb3440000-0xb344ffff irq 16 at device 0.0 on pci2 > ppt1 mem 0xb3400000-0xb340ffff irq 17 at device 0.1 on pci2 > ppt2 mem 0xb3410000-0xb341ffff irq 17 at device 0.2 on pci2 > ppt3 mem 0xb3420000-0xb342ffff irq 17 at device 0.3 on pci2 so ppt0 (the bge device) has two mem ranges... Another thing I should mention is that "acpidump -t | grep DMAR" reports nothing. It is mentioned in the documentation but I didn't see until now.