mrjrt
commented
8 years ago sigh scratch most of that. I've just wasted a large part of my day...very frustrating.
At some point earlier today I tested the original aoe32 driver WinVBlk was based on (to confirm it doesn't work in text mode) - and I disabled the WvBlk32.sys driver whilst doing so...and forgot to re-enable it afterwards. I could have sworn that it didn't error last time I tried the latest revision of of yours, it just didn't seem to do anything.
Anyway. Having re-enabled WvBlk32.sys I have returned to the behaviour I was expecting - no debug messages about the AoE code, nothing, just sits there waiting on the SAN disk.
I've just reverted back to revision 72ed1550a16c0740ce91a7fba41a0b2b36c96d64 (Date: 22/09/2011 06:39:45), and it too just seems to sit there, but I at least get messages suggesting it's not picking up responses?
g:\temp\coding\winvblock\src\aoe\driver.c @ 275: T[81BB0020]: DriverEntry(): Entry
g:\temp\coding\winvblock\src\aoe\registry.c @ 61: T[81BB0020]: AoeRegSetup(): Entry
g:\temp\coding\winvblock\src\aoe\driver.c @ 290: T[81BB0020]: DriverEntry(): Registry updated
g:\temp\coding\winvblock\src\aoe\protocol.c @ 168: T[81BB0020]: Protocol_Start(): Entry
g:\temp\coding\winvblock\src\aoe\protocol.c @ 204: T[81BB0020]: Protocol_Start(): Exit
g:\temp\coding\winvblock\src\winvblock\libbus\libbus.c @ 65: T[81BB0020]: WvlBusAddNode_(): Adding PDO 81A277D0 to bus FBF2AF34.
g:\temp\coding\winvblock\src\aoe\protocol.c @ 726: T[81A27978]: Protocol_BindAdapter(): Adapter: Ethernet Controller
g:\temp\coding\winvblock\src\aoe\protocol.c @ 728: T[81A27978]: Protocol_BindAdapter(): Device Name: \DEVICE\{4DB30059-46A5-4F69-B52A-C67B3DE4C8A3}
g:\temp\coding\winvblock\src\aoe\protocol.c @ 753: T[81A27978]: Protocol_BindAdapter(): Mac: 00:0c:29:d2:ea:f9
g:\temp\coding\winvblock\src\aoe\protocol.c @ 776: T[81A27978]: Protocol_BindAdapter(): MTU: 1500
g:\temp\coding\winvblock\src\aoe\bus.c @ 344: T[81BB0020]: AoeBusCreate(): Exit
g:\temp\coding\winvblock\src\aoe\driver.c @ 1228: T[81A26020]: AoeThread_(): Entry
g:\temp\coding\winvblock\src\aoe\driver.c @ 1560g:\temp\coding\winvblock\src\aoe\driver.c @ 1265: T[81A26020]: AoeThread_(): Sends: 0 Resends: 0 ResendFails: 0 Fails: 0 AoePendingTags_: 0 RequestTimeout: 0
: T[81BB0020]: AoeProcessAbft_(): Found aBFT at segment: 0x9e3c
g:\temp\coding\winvblock\src\aoe\driver.c @ 1791: T[81BB0020]: AoeDiskCreatePdo_(): Creating AoE disk PDO...
g:\temp\coding\winvblock\src\aoe\driver.c @ 1833: T[81BB0020]: AoeDiskCreatePdo_(): New PDO: 81A27A28
g:\temp\coding\winvblock\src\aoe\driver.c @ 1596: T[81BB0020]: AoeProcessAbft_(): Attaching AoE disk from client NIC 00:0c:29:d2:ea:f9 to major: 0 minor: 0
g:\temp\coding\winvblock\src\aoe\driver.c @ 1084: T[81A26020]: aoe__reply(): Major: 0 minor: 0 found on server 00:11:43:26:ca:65
g:\temp\coding\winvblock\src\aoe\driver.c @ 1154: T[FC1B9E20]: aoe__reply(): Got MaxSectorsPerPacket 2 at size of 1024. MTU of 1500 reached
g:\temp\coding\winvblock\src\aoe\driver.c @ 669: T[81BB0020]: AoeDiskInit_(): Disk size: 10240M cylinders: 1305 heads: 255sectors: 63 sectors per packet: 2
g:\temp\coding\winvblock\src\aoe\bus.c @ 369: T[81BB0020]: AoeBusAddDev(): Entry
g:\temp\coding\winvblock\src\winvblock\libbus\libbus.c @ 65: T[81BB0020]: WvlBusAddNode_(): Adding PDO 81A27A28 to bus FBFF79D8.
g:\temp\coding\winvblock\src\aoe\bus.c @ 382: T[81BB0020]: AoeBusAddDev(): Exit
g:\temp\coding\winvblock\src\aoe\driver.c @ 401: T[81BB0020]: DriverEntry(): Exit
g:\temp\coding\winvblock\src\winvblock\libbus\pnp.c @ 335: T[81BB0020]: WvlBusPnp(): IRP_MN_QUERY_DEVICE_RELATIONS
Waiting for SAN system disk (attempt 1)
System disk is <unknown>, boot disk is <unknown>
g:\temp\coding\winvblock\src\aoe\driver.c @ 1265: T[81A26020]: AoeThread_(): Sends: 3 Resends: 0 ResendFails: 0 Fails: 0 AoePendingTags_: 0 RequestTimeout: 200000
g:\temp\coding\winvblock\src\winvblock\driver.c @ 149: T[81BB0020]: WvDriverReinitialize(): Called
g:\temp\coding\winvblock\src\winvblock\driver.c @ 158: T[81BB0020]: WvDriverReinitialize(): Exiting...
Waiting for SAN system disk (attempt 2)
System disk is <unknown>, boot disk is <unknown>
g:\temp\coding\winvblock\src\aoe\driver.c @ 1265: T[81A26020]: AoeThread_(): Sends: 0 Resends: 0 ResendFails: 0 Fails: 0 AoePendingTags_: 0 RequestTimeout: 200000
Waiting for SAN system disk (attempt 3)
...etc...as mentioned above, this works in earlier revisions of the code. I'll have to try and find where this breaks...again. sigh
Sha0
Long story short, I've been tinkering with this for a week or so now, and I'm not really informed enough to fix the code myself, sadly. My use case is to use iPXE to hook an AoE disk to BIOS drive 0x81, then boot a USB stick with GRUB4DOS on it, and use that to load an ISO into RAM, then boot from that. This enables me to install XP from an ISO to an AoE target.
My testbed for all of this is a VMWare host with a floppy image of iPXE (sanhook -d 0x81 aoe:e0.0), my USB stick mapped as a physical IDE drive (VMWare doesn't do USB booting), and the Win32 build of VBlade acting as AoE target.
Now, revision 2ebc053a0152f98013281bbe94f8dd07888398f4 (Date: 24/12/2010 15:30:09) is the newest revision of WinVBlock that works for me - I am able to install XP end to end using that code (abet I have to load the ISO into memory though). Beyond that point though I suffer a variety of BSODs until a point after revision: ebc715894c51d5a0b770718ee5e4a8a7d1b5a006 (Date: 04/01/2011 08:34:53), where it no longer crashes, but I instead get errors about firstly being unable to add the AoE bus to the WinVBlock bus, and a bit later (Revision: bb6f3afd661b714d7df0b26697f3e032c6658c6d - Date: 07/01/2011 06:50:16), being unable to create the AoE bus PDO, and this persists to the most recent revision (7eed6ad5a72fb7d35e93031de36022816c00400f - Date: 25/01/2016 00:31:00).
Aside from this, I ideally want to be able to use sector-mapped ISOs. I have this working fine with Firadisk, but this does not seem to work so well with the old revision of WinVBlock that AoE works with...but works fine in the latest revisions, as far as I can tell. My next attempted workaround for the time being is going to be to try disabling WinVBlock's GRUB4DOS handling in a branch from revision 2ebc053a0152f98013281bbe94f8dd07888398f4 so I can use Firadisk for the mappings and WinVBlock for AoE, as I figure disabling stuff is a lot more likely to work than trying to fix something you don't understand!
I created my own fork on Github and have grabbed full debug logs (edited into the notes for each commit) and tagged revisions I've tested. Dunno if you would find that information useful, but I'll push it up at some point.