hi all, got question about using wifi (wpi) with xen. from doc i understand that the nic in dom0 must be based on GLDv3. I''ve got two bge and wpi. # dladm show-dev wpi0 link: down speed: 0Mb duplex: unknown bge0 link: up speed: 100Mb duplex: full # dladm show-link bge0 type: non-vlan mtu: 1500 device: bge0 the wpi is also GLDv3 based, but I can get it work. is there any another issue with wifi? thank you, -danjo Sep 7 06:05:03 sunosxen xpv_psm: [ID 803547 kern.info] xen_psm: pciex8086,4222 (wpi) instance 0 vector 0x11 ioapic 0x2 intin 0x11 is bound to cpu 1 Sep 7 06:05:03 sunosxen mac: [ID 469746 kern.info] NOTICE: wpi0 registered Sep 7 06:05:09 sunosxen wpi: [ID 514036 kern.warning] WARNING: wpi_config(): failed to set txpower Sep 7 06:05:09 sunosxen wpi: [ID 913098 kern.warning] WARNING: wpi_init(): failed to configure device Sep 7 06:05:12 sunosxen wpi: [ID 514036 kern.warning] WARNING: wpi_config(): failed to set txpower Sep 7 06:05:12 sunosxen wpi: [ID 913098 kern.warning] WARNING: wpi_init(): failed to configure device Sep 7 06:05:14 sunosxen wpi: [ID 133862 kern.warning] WARNING: wpi_init(): timeout waiting for firmware init Sep 7 06:05:17 sunosxen wpi: [ID 514036 kern.warning] WARNING: wpi_config(): failed to set txpower Sep 7 06:05:17 sunosxen wpi: [ID 913098 kern.warning] WARNING: wpi_init(): failed to configure device Sep 7 06:05:19 sunosxen wpi: [ID 133862 kern.warning] WARNING: wpi_init(): timeout waiting for firmware init Sep 7 06:05:22 sunosxen wpi: [ID 514036 kern.warning] WARNING: wpi_config(): failed to set txpower Sep 7 06:05:22 sunosxen wpi: [ID 913098 kern.warning] WARNING: wpi_init(): failed to configure device Sep 7 06:05:25 sunosxen wpi: [ID 133862 kern.warning] WARNING: wpi_init(): timeout waiting for firmware init Sep 7 06:05:28 sunosxen wpi: [ID 514036 kern.warning] WARNING: wpi_config(): failed to set txpower Sep 7 06:05:28 sunosxen wpi: [ID 913098 kern.warning] WARNING: wpi_init(): failed to configure device Sep 7 06:05:31 sunosxen wpi: [ID 133862 kern.warning] WARNING: wpi_init(): timeout waiting for firmware init Sep 7 06:05:34 sunosxen wpi: [ID 514036 kern.warning] WARNING: wpi_config(): failed to set txpower Sep 7 06:05:34 sunosxen wpi: [ID 913098 kern.warning] WARNING: wpi_init(): failed to configure device Sep 7 06:05:36 sunosxen wpi: [ID 133862 kern.warning] WARNING: wpi_init(): timeout waiting for firmware init Sep 7 06:05:39 sunosxen wpi: [ID 514036 kern.warning] WARNING: wpi_config(): failed to set txpower Sep 7 06:05:39 sunosxen wpi: [ID 913098 kern.warning] WARNING: wpi_init(): failed to configure device Sep 7 06:05:45 sunosxen wpi: [ID 133862 kern.warning] WARNING: wpi_init(): timeout waiting for firmware init Sep 7 06:05:48 sunosxen wpi: [ID 514036 kern.warning] WARNING: wpi_config(): failed to set txpower Sep 7 06:05:48 sunosxen wpi: [ID 913098 kern.warning] WARNING: wpi_init(): failed to configure device Sep 7 06:56:26 sunosxen wpi: [ID 133862 kern.warning] WARNING: wpi_init(): timeout waiting for firmware init Sep 7 06:56:29 sunosxen wpi: [ID 514036 kern.warning] WARNING: wpi_config(): failed to set txpower Sep 7 06:56:29 sunosxen wpi: [ID 913098 kern.warning] WARNING: wpi_init(): failed to configure device Sep 7 06:56:31 sunosxen wpi: [ID 133862 kern.warning] WARNING: wpi_init(): timeout waiting for firmware init Sep 7 06:56:34 sunosxen wpi: [ID 514036 kern.warning] WARNING: wpi_config(): failed to set txpower Sep 7 06:56:34 sunosxen wpi: [ID 913098 kern.warning] WARNING: wpi_init(): failed to configure device Sep 7 06:56:34 sunosxen ip: [ID 153875 kern.error] wpi0: DL_ATTACH_REQ failed: DL_SYSERR (errno 1) Sep 7 06:56:34 sunosxen ip: [ID 713268 kern.error] wpi0: DL_BIND_REQ failed: DL_OUTSTATE Sep 7 06:56:34 sunosxen ip: [ID 466048 kern.error] wpi0: DL_PHYS_ADDR_REQ failed: DL_OUTSTATE Sep 7 06:56:34 sunosxen ip: [ID 972295 kern.error] wpi0: DL_UNBIND_REQ failed: DL_OUTSTATE Sep 7 08:02:22 sunosxen wpi: [ID 133862 kern.warning] WARNING: wpi_init(): timeout waiting for firmware init Sep 7 08:02:25 sunosxen wpi: [ID 514036 kern.warning] WARNING: wpi_config(): failed to set txpower Sep 7 08:02:25 sunosxen wpi: [ID 913098 kern.warning] WARNING: wpi_init(): failed to configure device Sep 7 08:02:27 sunosxen wpi: [ID 133862 kern.warning] WARNING: wpi_init(): timeout waiting for firmware init Sep 7 08:02:30 sunosxen wpi: [ID 514036 kern.warning] WARNING: wpi_config(): failed to set txpower Sep 7 08:02:30 sunosxen wpi: [ID 913098 kern.warning] WARNING: wpi_init(): failed to configure device Sep 7 08:02:32 sunosxen wpi: [ID 133862 kern.warning] WARNING: wpi_init(): timeout waiting for firmware init Sep 7 08:02:35 sunosxen wpi: [ID 514036 kern.warning] WARNING: wpi_config(): failed to set txpower Sep 7 08:02:35 sunosxen wpi: [ID 913098 kern.warning] WARNING: wpi_init(): failed to configure device Sep 7 08:02:37 sunosxen wpi: [ID 133862 kern.warning] WARNING: wpi_init(): timeout waiting for firmware init Sep 7 08:02:40 sunosxen wpi: [ID 514036 kern.warning] WARNING: wpi_config(): failed to set txpower Sep 7 08:02:40 sunosxen wpi: [ID 913098 kern.warning] WARNING: wpi_init(): failed to configure device Sep 7 08:02:42 sunosxen wpi: [ID 133862 kern.warning] WARNING: wpi_init(): timeout waiting for firmware init Sep 7 08:02:45 sunosxen wpi: [ID 514036 kern.warning] WARNING: wpi_config(): failed to set txpower Sep 7 08:02:45 sunosxen wpi: [ID 913098 kern.warning] WARNING: wpi_init(): failed to configure device Sep 7 08:02:47 sunosxen wpi: [ID 133862 kern.warning] WARNING: wpi_init(): timeout waiting for firmware init Sep 7 08:02:50 sunosxen wpi: [ID 514036 kern.warning] WARNING: wpi_config(): failed to set txpower Sep 7 08:02:50 sunosxen wpi: [ID 913098 kern.warning] WARNING: wpi_init(): failed to configure device This message posted from opensolaris.org
On Fri, Sep 07, 2007 at 12:24:31AM -0700, Jacob wrote:> the wpi is also GLDv3 based, but I can get it work. is there any > another issue with wifi?Yes. There are two (or three) problems: 1. The VNIC layer we use assumes that the mac device it will use is "pure" DL_ETHER. Wifi links are not "pure" - they require the headers of packets to be cooked and uncooked on transmit and receive. The VNIC layer doesn''t know that it should do this. (Alternatively, it could properly re-present the lower mac type upward and expect clients to do the work, but that would still require changes to xnb, as it also currently assumes a "pure" DL_ETHER link). 2. Many (most, all?) Wifi devices don''t allow the transmission of packets with a MAC address different to that of the device when in client mode. For MAC address based VNICs to work, being able to do so is a requirement. Because of (2) I''ve made a change such that VNIC creation (and hence domain creation) will fail if the NIC specified is not "pure" DL_ETHER, but this change isn''t in the public bits. dme.