From owner-freebsd-virtualization@FreeBSD.ORG Sat Nov 29 17:38:23 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 05203445; Sat, 29 Nov 2014 17:38:23 +0000 (UTC) Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C254B90; Sat, 29 Nov 2014 17:38:22 +0000 (UTC) Received: by mail-pa0-f42.google.com with SMTP id et14so8496473pad.29 for ; Sat, 29 Nov 2014 09:38:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=VaSGUFtiU5uviQBvBQQg4CofXwavvUzHEn28gsy+384=; b=GtyPXe/5pCKKFBCUMlvBYGzhxQqWuZuP8WcX70UiZ+RvQXWQ6fsnLbQXjlDAmsCGvU u4mpbueUIrO3iCYjdraTPjybaZf5y9f/QN5/KchJBSk7ybnflH1TOtLK3WCgOoBtfw41 U6fgjFKHOKxD4bxS92U798JD3WURcaehASOOUcsH9MN4EOKgl4GNT4RKHnj6NJd4Ackq ecUriQwmgJB6Bidj6Cq7X/LddEa+hfiyORD68/9exsIaMyab1uvj4qeVr1p7Cn0Zb6Bp 4Ob0tiZZtyzTEZYdnic8BaNX+Ojc4JHooCoeLz1rQx/kcNxLeyhTMvsYC6a22jRCiDVX CtBA== X-Received: by 10.66.161.197 with SMTP id xu5mr23721362pab.3.1417282702417; Sat, 29 Nov 2014 09:38:22 -0800 (PST) Received: from [192.168.1.3] ([98.248.138.12]) by mx.google.com with ESMTPSA id oc16sm839120pdb.41.2014.11.29.09.38.20 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 29 Nov 2014 09:38:21 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: bhyve: Unsupported MSI-X configuration: 2/0/0 From: Anish Gupta In-Reply-To: <5479DBD8.1090009@gmx.com> Date: Sat, 29 Nov 2014 09:38:19 -0800 Message-Id: References: <5478E4C4.3080203@gmx.com> <1B9C5228-5549-412C-AAE9-5053C86EDB9D@gmail.com> <5479DBD8.1090009@gmx.com> To: Nikos Vassiliadis X-Mailer: Apple Mail (2.1993) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-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 17:38:23 -0000 >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. DMAR/VT-d has been supported for sometime now by Intel chipset. You want = to check your BIOS set-up to enable VT-d. >Actually my goal is to use the wifi adapter from a VM. The bge device = is just testing and I thought I should report it/ask about it. What is the error you see in VM for enabling wifi adapter? Is the = corresponding driver getting attached to WiFi adapter? >Then I start "bhyve ... -s 10,passthru,2/0/0 ..." and it spits: "Unsupported MSI-X configuration: 2/0/0" and quits. > ppt0@pci0:2:0:0: class=3D0x020000 card=3D0x06471025 = chip=3D0x16b514e4 rev=3D0x10 hdr=3D0x00 I will try to reproduce the problem if I get hold of this device. -Anish > On Nov 29, 2014, at 6:44 AM, Nikos Vassiliadis wrote: >=20 >=20 >=20 > On 11/29/14 06:02, Anish Gupta wrote: >>>> bge0@pci0:2:0:0: class=3D0x020000 card=3D0x06471025 >>>> chip=3D0x16b514e4 rev=3D0x10 hdr=3D0x00 >>>> sdhci_pci0@pci0:2:0:1: class=3D0x080501 card=3D0x06471025 >>>> chip=3D0x16bc14e4 rev=3D0x10 hdr=3D0x00 >>>> none2@pci0:2:0:2: class=3D0x088000 card=3D0x06471025 >>>> chip=3D0x16be14e4 rev=3D0x10 hdr=3D0x00 >>>> none3@pci0:2:0:3: class=3D0x088000 card=3D0x06471025 >>>> chip=3D0x16bf14e4 rev=3D0x10 hdr=3D0x00 >>=20 >> 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=3D=E2=80=9CYES=E2=80=9D in /boot/loader.conf as mentioned in >> https://wiki.freebsd.org/bhyve/pci_passthru? >=20 > 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 >=20 > 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. >=20 >>=20 >> 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 =E2=80=9Coption KTRACE=E2=80=9D] etc. >=20 > Everything seems ok here as well, I get nothing but the ppt devices. >=20 > 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 >=20 > so ppt0 (the bge device) has two mem ranges... >=20 > 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.