As the title suggests, I'm looking for something that will help me to boot
windows7 over iscsi with different NIC.
Here's the current situation,
I've iscsi set-up on ubuntu server edition with dhcp server up and running on
it. All the settings related with the dhcp configuration have been taken care of
(You can be sure of this).
Windows 7 has been installed on the iscsi disk thr' some particular machine
(it's basically a thin-client, let's say x1). It has drivers corresponding to
NIC of this machine. So this way I have a windows7 iscsi image and I can
diskless boot from this image from the machine (x1) as many times as I want to
without any problem and everything works fine.
Problem is when I try to boot from some completely different machine (say,
thin-client, x2-with different NIC than x1), then the booting process halts at
"Starting Windows" windows logo and eventually produces BSOD STOP 0x0000007B: INACCESSIBLE_BOOT_DEVICE.The microsft hotfix works when ALL the NICs going to be used to boot from iSCSI are present in computer. How to add NIC when it's different brand (the one which was not present during iSCSI installation)?
You can consider the scenario where 2nd machine is just a clone of 1st machine.
And while booting from 2nd machine I'm just changing the NIC thr' hypervisor
settings. Do I need to write some driver which will enable me achieve this? If
yes, what its functionality should be? Have there been any previous successful
attempts at this? (As per my research, there haven't been any, not counting the
I've gone thr' following links while searching for the solution:
I wonder if anybody has ever successfully managed to create sort of universal image using the section "Installing Target NIC" mentioned in above link. The import-export of .REG file eventually hard codes the Instance-Id for the NIC whereas Instance-Id is something that is generated on the fly. Obviously when iSCSI booted, it looks up the Instance-Id for the new NIC under "Enum" and it doesn't find one and hence the problem persists.
suggests that this problem might go away by adding reg entry for this new NIC inside "Critical Device Database". However doing some research on net suggests that it does not hold true when it comes to NIC. Nonetheless, would like to know how to add reg entry inside CDDB given the .INF file. Is there tool/utility out there which does this job?
So do you guys have any idea how to get around this?