WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Atheros AR9287 PCI passthrough issue

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Atheros AR9287 PCI passthrough issue
From: Etienne FLYE SAINTE MARIE <etn@xxxxxxx>
Date: Tue, 25 Jan 2011 17:14:07 +0100 (CET)
Delivery-date: Tue, 25 Jan 2011 08:15:28 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <11893164.6.1295215331740.JavaMail.root@xxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I just tried to compile and use last compat-wireless-2.6 build from wireless.kernel.org and i still have the issue.

Is there a way to identify if it's a xen issue or an ath9k module issue?

Thanks for your help

Etienne



De: "Etienne FLYE SAINTE MARIE" <etn@xxxxxxx>
À: xen-users@xxxxxxxxxxxxxxxxxxx
Envoyé: Dimanche 16 Janvier 2011 23:02:11
Objet: [Xen-users] Atheros AR9287  PCI passthrough issue

Hi,
i'm trying to use PCI passthrough feature on Xen 4.0 but it fails on my Wireless card.

I use Xen 4.0 on a Debian 6.0 (package from repo) and try to passthrough the following PCI device
root@omega:~# dpkg -l | grep xen
ii  libxenstore3.0                      4.0.1-1                     Xenstore communications library for Xen
ii  linux-image-2.6.32-5-xen-amd64      2.6.32-30                   Linux 2.6.32 for 64-bit PCs, Xen dom0 support
ii  xen-hypervisor-4.0-amd64            4.0.1-1                     The Xen Hypervisor on AMD64
ii  xen-qemu-dm-4.0                     4.0.1-2                     Xen Qemu Device Model virtual machine hardware emulator
ii  xen-tools                           4.2-1                       Tools to manage Xen virtual servers
ii  xen-utils-4.0                       4.0.1-1                     XEN administrative tools
ii  xen-utils-common                    4.0.0-1                     XEN administrative tools - common files
ii  xenstore-utils                      4.0.1-1                     Xenstore utilities for Xen

root@omega:~# lspci
(...)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
03:00.0 Network controller: Atheros Communications Inc. AR9287 Wireless Network Adapter (PCI-Express) (rev 01)

root@omega:~# cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet xen-pciback.permissive xen-pciback.hide=(01:00.0)(03:00.0) pci=resource_alignment=01:00.0;03:00.0"
GRUB_CMDLINE_LINUX=""

root@omega:~# xm pci-list-assignable-devices
0000:03:00.0
0000:01:00.0

the LAN device works perfectly on the DomU configured with it but it fails on the WLAN one:


root@omega:~# cat /etc/xen/AccessPoint.cfg
#
# Configuration file for the Xen instance AccessPoint, created
# by xen-tools 4.2 on Fri Jan 14 17:37:08 2011.
#

#
#  Kernel + memory size
#
kernel      = '/boot/vmlinuz-2.6.32-5-xen-amd64'
ramdisk     = '/boot/initrd.img-2.6.32-5-xen-amd64'

vcpus       = '1'
memory      = '256'

#
#  Disk device(s).
#
root        = '/dev/xvda2 ro'
disk        = [
                  'phy:/dev/lvg-xen/AccessPoint-disk,xvda2,w',
                  'phy:/dev/lvg-xen/AccessPoint-swap,xvda1,w',
              ]


#
#  Physical volumes
#


#
#  Hostname
#
name        = 'AccessPoint'

#
#  Networking
#
vif         = [ 'ip=192.168.42.5,mac=00:16:3E:1E:88:3E' ]

pci=['03:00.0']
#
#  Behaviour
#

on_reboot   = 'restart'
on_crash    = 'restart'


On the DomU:

root@AccessPoint:~# lspci
00:00.0 Network controller: Atheros Communications Inc. AR9287 Wireless Network Adapter (PCI-Express) (rev 01)

root@AccessPoint:~# ifconfig wlan0 up
[   51.254777] ADDRCONF(NETDEV_UP): wlan0: link is not ready

root@AccessPoint:~# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:off/any 
          Mode:Managed  Access Point: Not-Associated   Tx-Power=16 dBm  
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
         
root@AccessPoint:~# iwlist scan
lo        Interface doesn't support scanning.

eth0      Interface doesn't support scanning.

[   86.863546] ath: ffff88000dd95be0
[   86.863553] ath: ffff88000dd95c00
[   86.874968] ath: ffff88000dd95bc0
[   86.944314] ath: ffff88000dd95bc0
[   86.944364] ath: ffff88000dd95bf0
[   86.955778] ath: ffff88000dd95be0
[   86.955783] ath: ffff88000dd95c00
[   86.967241] ath: ffff88000dd95bc0
[   87.036195] ath: ffff88000dd95bc0
[   87.036243] ath: ffff88000dd95bf0
[   87.108346] ath: ffff88000dd95bc0
[   87.108395] ath: ffff88000dd95bf0
[   87.119864] ath: ffff88000dd95be0
[   87.119870] ath: ffff88000dd95c00
[   87.131275] ath: ffff88000dd95bc0
[   87.200197] ath: ffff88000dd95bc0
[   87.200245] ath: ffff88000dd95bf0
[   87.272314] ath: ffff88000dd95bc0
[   87.272363] ath: ffff88000dd95bf0
[   87.283832] ath: ffff88000dd95be0
[   87.283837] ath: ffff88000dd95c00
[   87.295239] ath: ffff88000dd95bc0
[   87.364314] ath: ffff88000dd95bc0
[   87.364363] ath: ffff88000dd95bf0
[   87.375829] ath: ffff88000dd95be0
[   87.375835] ath: ffff88000dd95c00
[   87.387240] ath: ffff88000dd95bc0
[   87.456364] ath: ffff88000dd95bc0
[   87.456414] ath: ffff88000dd95bf0
[   87.467821] ath: ffff88000dd95be0
[   87.467826] ath: ffff88000dd95c00
[   87.479286] ath: ffff88000dd95bc0
[   87.548195] ath: ffff88000dd95bc0
[   87.548243] ath: ffff88000dd95bf0
[   87.620314] ath: ffff88000dd95bc0
[   87.620363] ath: ffff88000dd95bf0
[   87.631776] ath: ffff88000dd95be0
[   87.631781] ath: ffff88000dd95c00
[   87.643240] ath: ffff88000dd95bc0
[   87.712209] ath: ffff88000dd95bc0
[   87.712257] ath: ffff88000dd95bf0
[   87.784329] ath: ffff88000dd95bc0
[   87.784378] ath: ffff88000dd95bf0
[   87.795844] ath: ffff88000dd95be0
[   87.795849] ath: ffff88000dd95c00
[   87.807263] ath: ffff88000dd95bc0
[   87.947540] ath: ffff88000dd95be0
[   87.947546] ath: ffff88000dd95c00
[   87.959001] ath: ffff88000dd95bc0
[   88.099529] ath: ffff88000dd95be0
[   88.099535] ath: ffff88000dd95c00
[   88.110942] ath: ffff88000dd95bc0
[   88.251550] ath: ffff88000dd95c40
[   88.251555] ath: ffff88000dd95c60
[   88.263024] ath: ffff88000dd95c20wlan0     No scan results


WLAN Card can't see any ssid whereas this command works on Dom0 if i unhide the device.

Do you any idea why it fails on it? If you have any idea on configuration side, i'm listenning ;)

Thanks a lot

Etienne


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>