[ipxe-devel] Windows bootup problems after successfull wimboot-iscsi setup

Ivan Krutskikh stein.hak at gmail.com
Mon Nov 10 10:44:50 UTC 2014


Thou this is not technically speaking a ipxe question, but I think this is
an appropriate place to get some help with it.

So I am developing a Linux/Windows diskless boot system based on ipxe,
zfsonlinux and python. Linux part works like a bliss with multiple distros,
different hardware e.t.c.

At first I made some progress with windows 7 too, using pure cd-rom setup
for single station ( a supposed to be  a Microsoft supported scenario) and
a ccboot client v2.0 for injecting multiple nic drivers for different

I used the same booting script for both:


set keep-san 1
set netX/gateway
sanboot iscsi:

But after some time ( maybe some windows updates as well, hard to tell) the
whole windows booting sequence broke and I cannot fix it or reproduce it
with fresh install. All windows bootups end with hang windows logo followed
bsod 7e and a reboot. As far as I can tell, this is because windows
couldn't find the driver for main hdd storage. ( basically, it is the lan
driver + msicsi)

After some experiments with never ccboot versions, I tried a different
approach based on http://ipxe.org/howto/winpe. So I made a custom 3.0
winpe, booted it with ipxe script:


set netX/gateway
sanhook  iscsi:
initrd BCD
initrd boot.sdi
initrd boot.wim

My nic was perfectly recognized and configured, windows 7 setup was able to
see my iscsi drive and installed windows just like it would on a local hdd.
But after reboot- same old story. Bootup hangs, BSoD 7e. Tried launching a
local VM from the same media, which was used to provide iscsi target- setup
finished succesfull, new desktop welcomed me.

At this point I'm out of ideas. What differs installing windows by winpe to
iscsi from the same scenario with cdrom? Not to mention there are a number
of tutorials on the internet suggesting the second method for client

What am I doing wrong here?

Thanks in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20141110/0d03ea22/attachment.htm>

More information about the ipxe-devel mailing list