Thread: [Aoetools-discuss] Dropped winaoe config requests
Brought to you by:
ecashin,
elcapitansam
From: Sven U. <sv...@if...> - 2008-08-23 23:00:03
|
I'm trying to boot windows xp over aoe using gpxe, vblade+aoe on the server and the winaoe driver on the client. gpxe works fine, and starts booting the winxp image, but when windows gets to DRIVERS\aoe32.sys, it hangs forever. What happens is that the driver starts sending config request broadcasts that look like this: (if lines are mangled, see http://pastebin.ca/1182682) Ethernet II, Src: Intel_c3:20:c2 (00:0e:0c:c3:20:c2), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Destination: Broadcast (ff:ff:ff:ff:ff:ff) Source: Intel_c3:20:c2 (00:0e:0c:c3:20:c2) Type: ATA over Ethernet (0x88a2) ATAoverEthernet Version: 1 Flags: Request .... 0... = Response flag: Request .... .0.. = Error flag: No error Major: 0xffff Minor: 0xff Command: Query Config Information (1) Tag: 0x00000000 Raw data, including ethernet frame: 0000 ff ff ff ff ff ff 00 0e 0c c3 20 c2 88 a2 10 00 .......... ..... 0010 ff ff ff 01 00 00 00 00 00 00 00 00 00 00 00 00 ................ In the aoe kernel module, aoenet.c (aoe6-64) line 187--190: 187 h = (struct aoe_hdr *) skb->data; 188 n = be32_to_cpu(get_unaligned(&h->tag)); 189 if ((h->verfl & AOEFL_RSP) == 0 || (n & 1<<31)) 190 goto exit; ..the config request is dropped because the incoming h->verfl is 0x10 (AOEFL_RSP is 0x8), and n (the tag) is 0x00000000 (ANDed with 0x80000000) => goto exit; Changing this to only exit if receiving a query with a zero tag: 189 if ((h->verfl & AOEFL_RSP) == 0 && n != 0) ..gets me a bit further, but I end up in aoecmd.c, aoecmd_cfg_rsp() line 1349: printk(KERN_INFO "aoe: e%ld.%d: broadcast shelf number invalid\n", ..since the major and minor are obviously invalid. Is there something missing? Possibly the info handover from gpxe to winaoe? sven |
From: Sven U. <sv...@if...> - 2008-09-10 19:01:26
|
Sven Ulland wrote: > I'm trying to boot windows xp over aoe using gpxe, vblade+aoe on the > server and the winaoe driver on the client. > > gpxe works fine, and starts booting the winxp image, but when > windows gets to DRIVERS\aoe32.sys, it hangs forever. What happens is > that the driver starts sending config request broadcasts that look > like this: This turned out to be a problem with the nforce/forcedeth ethernet card, probably due to a missing service. Rumors (sorry, no references) say that the nforce card needs an additional service running to work properly, in addition to the main NVENETFD service. Putting in a 3com 905c or an Intel PRO/1000 GT (82541PI) in stead, resolved the problem flawlessly. sven |