Date: Sat, 29 Nov 2014 09:38:19 -0800 From: Anish Gupta <akgupt3@gmail.com> To: Nikos Vassiliadis <nvass@gmx.com> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: bhyve: Unsupported MSI-X configuration: 2/0/0 Message-ID: <F12259D8-55EF-44FF-BFB6-DB7DCBF486AD@gmail.com> In-Reply-To: <5479DBD8.1090009@gmx.com> References: <5478E4C4.3080203@gmx.com> <CAG=rPVfSXAxeJ3bB0ughSej2uv2-iQTqv-7Yp6PtBZo05RTUvw@mail.gmail.com> <1B9C5228-5549-412C-AAE9-5053C86EDB9D@gmail.com> <5479DBD8.1090009@gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>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 <nvass@gmx.com> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F12259D8-55EF-44FF-BFB6-DB7DCBF486AD>