From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 30 01:43:51 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 9C2B633C for ; Sun, 30 Nov 2014 01:43:51 +0000 (UTC) Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (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 2D31AB9 for ; Sun, 30 Nov 2014 01:43:51 +0000 (UTC) Received: by mail-wi0-f175.google.com with SMTP id l15so21537031wiw.2 for ; Sat, 29 Nov 2014 17:43:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6odazPFO7RjG6wVZziBEk/5LtxR7G7BZXFkdCFO82LA=; b=c7HbeY4TJg7GcUeChGRn4LopYozCdrGAMaMrTQWovGqOyZGz8C3t1Y6rLFfMuxSkDt jY45wfRk+iRcRThKpjmf+RXvAj6gOjfRD9LI9hx2sMqx4P5krEL1aWCoq9NKNbjEiJ2j MZ3syLd6LMZACRUKmY36xlRAjWx8MsB+BA2ifW+Gd4/DZDY5lSsysGB+a2Y6eDF6Qv71 OcZIGmeMIodfBtq+hUkkMORqoIlzf664pJgDeyxpVIRFCv9uyRL2QqGeTlIZmp4w0Hos z1WaohPWOmKoA0qYkVGihQtpuCGuZj+DbX9U29CIDk1nhWFcyazWwplr4IGSglIOgOWU 4L/w== MIME-Version: 1.0 X-Received: by 10.180.75.237 with SMTP id f13mr71469207wiw.69.1417311829520; Sat, 29 Nov 2014 17:43:49 -0800 (PST) Received: by 10.27.12.168 with HTTP; Sat, 29 Nov 2014 17:43:49 -0800 (PST) In-Reply-To: <547A1454.2030901@gmx.com> References: <5478E4C4.3080203@gmx.com> <1B9C5228-5549-412C-AAE9-5053C86EDB9D@gmail.com> <5479DBD8.1090009@gmx.com> <547A1454.2030901@gmx.com> Date: Sat, 29 Nov 2014 17:43:49 -0800 Message-ID: Subject: Re: bhyve: Unsupported MSI-X configuration: 2/0/0 From: Neel Natu To: Nikos Vassiliadis Content-Type: text/plain; charset=UTF-8 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: Sun, 30 Nov 2014 01:43:51 -0000 Hi Nikos, On Sat, Nov 29, 2014 at 10:45 AM, Nikos Vassiliadis 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 >> >> Features=0xbfebfbff >> >> Features2=0x3dbae3bf >> AMD Features=0x28100800 >> AMD Features2=0x1 >> Structured Extended Features=0x281 >> 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 > look. > >> >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 >> 6.30.223.248 (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. best Neel > > 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@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@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscribe@freebsd.org"