From owner-freebsd-virtualization@freebsd.org  Sun Feb 28 15:17:20 2016
Return-Path: <owner-freebsd-virtualization@freebsd.org>
Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5CAE3AB7DD8
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Sun, 28 Feb 2016 15:17:20 +0000 (UTC)
 (envelope-from richard@bader-muenchen.de)
Received: from gate1.bader-muenchen.de (gate1.bader-muenchen.de
 [213.179.151.243])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id E5D0D1749
 for <freebsd-virtualization@freebsd.org>; Sun, 28 Feb 2016 15:17:19 +0000 (UTC)
 (envelope-from richard@bader-muenchen.de)
Received: from [IPv6:::1] (gate.bader.loc [192.168.16.3])
 by gate1.bader-muenchen.de (8.15.2/8.15.2) with ESMTP id u1SFH7m7009764;
 Sun, 28 Feb 2016 16:17:08 +0100 (CET)
 (envelope-from richard@bader-muenchen.de)
Subject: Re: ath0 (wlan0) not working in virtulised guest with bhyve
To: Neel Natu <neelnatu@gmail.com>
References: <56D173DC.9040805@bader-muenchen.de>
 <CAFgRE9FAQvDt7JzD22L+2AU3E20whyrSDz28Y=Tuxjp4WyByBw@mail.gmail.com>
Cc: richard@bader-muenchen.de,
 "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>
From: richard bader <richard@bader-muenchen.de>
Message-ID: <56D30F9F.4050005@bader-muenchen.de>
Date: Sun, 28 Feb 2016 16:17:51 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CAFgRE9FAQvDt7JzD22L+2AU3E20whyrSDz28Y=Tuxjp4WyByBw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Feb 2016 15:17:20 -0000

Hey Neel,
> I suspect that the ath0 controller does not support MSI/MSI-x
> interrupts. The output of 'pciconf -lvbc' on the host will confirm if
> this is the case.
>
thanks for the hint. The controller should support MSI interrupts.

root@test10:/usr/src/sys # pciconf -lvbc

ath0@pci0:5:0:0:        class=0x028000 card=0x30a4168c chip=0x002e168c 
rev=0x01 hdr=0x00
     vendor     = 'Atheros Communications Inc.'
     device     = 'AR9287 Wireless Network Adapter (PCI-Express)'
     class      = network
     bar   [10] = type Memory, range 64, base 0xf7100000, size 65536, 
enabled
     cap 01[40] = powerspec 3  supports D0 D1 D3  current D0
     cap 05[50] = MSI supports 1 message
     cap 10[60] = PCI-Express 2 legacy endpoint max data 128(128) link 
x1(x1)
                  speed 2.5(2.5) ASPM L0s/L1(L0s/L1)
     ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected
     ecap 0002[140] = VC 1 max VC0
     ecap 0003[160] = Serial 1 001517ffff241412
     ecap 0004[170] = Power Budgeting 1


But as I read in https://wiki.freebsd.org/dev/ath_hal%284%29/AR9300, MSI 
interrupts are not supported before AR9300 HAL.

So i'll buy an other card and try again.

But it would be a good idea to add the check for supported MSI/MSI-x 
interrupts to the https://wiki.freebsd.org/bhyve/pci_passthru .

thanks

richard