bhyve: Unsupported MSI-X configuration: 2/0/0
neelnatu at gmail.com
Sun Nov 30 01:43:51 UTC 2014
On Sat, Nov 29, 2014 at 10:45 AM, Nikos Vassiliadis <nvass at gmx.com> wrote:
> On 11/29/14 18:38, Anish Gupta wrote:
>> >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.
> There are very few setting in the BIOS setup and nothing related to VT-d. My
> CPU and CPU settings are these:
>> CPU: Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz (2394.61-MHz K8-class CPU)
>> Origin = "GenuineIntel" Id = 0x306a9 Family = 0x6 Model = 0x3a
>> Stepping = 9
>> AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
>> AMD Features2=0x1<LAHF>
>> Structured Extended Features=0x281<FSGSBASE,SMEP,ERMS>
>> VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
>> TSC: P-state invariant, performance statistics
> I have attached the output of "acpidump -t" in case you'd like to take a
>> >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?
> When I load the kernel module, I get this:
>> [ 542.919615] cfg80211: Calling CRDA to update world regulatory domain
>> [ 542.932441] wl 0000:00:07.0: can't derive routing for PCI INT A
>> [ 542.932449] wl 0000:00:07.0: PCI INT A: no GSI
>> [ 543.002253] wlan0: Broadcom BCM4727 802.11 Hybrid Wireless Controller
>> 18.104.22.168 (r487574)
Can you provide the output of 'pciconf -lvbc pci0:3:0:0' on the FreeBSD host?
This is assuming pci0:3:0:0 is the wlan device being passed through
based on an earlier email.
> After that, there is a wlan0 device but I am not sure whether it works.
> There are no new kernel warnings or error messages but no matter what I do
> (scan, create an AP etc) there is zero reaction. But that might a
> problematic driver that the VM is using. That's on Linux 3.16.something.
> I have tried to load another driver and there is a complain regarding PCI
> which is common to both drivers:
>> [ 1515.692558] bcma-pci-bridge 0000:00:07.0: can't derive routing for PCI
>> INT A
>> [ 1515.692568] bcma-pci-bridge 0000:00:07.0: PCI INT A: no GSI
> Didnt test further with this driver.
> On FreeBSD, I tried to do the same with an ndis windows driver. It didn't
> get very far because some windows drivers and ndis and amd64 don't like each
> other very much:)
>> >Then I start "bhyve ... -s 10,passthru,2/0/0 ..." and it spits:
>> "Unsupported MSI-X configuration: 2/0/0"
>> and quits.
>>> ppt0 at pci0:2:0:0: class=0x020000 card=0x06471025 chip=0x16b514e4
>>> rev=0x10 hdr=0x00
>> I will try to reproduce the problem if I get hold of this device.
> Great, thank you.
> freebsd-virtualization at freebsd.org mailing list
> To unsubscribe, send any mail to
> "freebsd-virtualization-unsubscribe at freebsd.org"
More information about the freebsd-virtualization