Re: [ipxe-devel] Windows 8 ISCSI Boot
Hello, Are anyone of you managed to successfully boot a Windows 8 installation over ISCSI with a Realtek nic? Regards, Marc Hammer ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
Re: [ipxe-devel] Windows 8 ISCSI Boot
On Fri, Jun 7, 2013 at 3:47 PM, Marc Hammer marcham...@arcor.de wrote: Hello, Are anyone of you managed to successfully boot a Windows 8 installation over ISCSI with a Realtek nic? Regards, Marc Hammer ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel Hello Marc, I'm almost certain that I have... but I can't say that I'm 100% sure. I can offer to test it against the Realtek NIC in my desktop. What are the PCI DEV/VEN IDs for your NIC? Also, what iSCSI target are you using?--I've never seen that matter, but information is always good! -Andrew ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
Re: [ipxe-devel] Windows 8 ISCSI Boot
On Thu, May 30, 2013 at 3:02 PM, Marc Hammer marcham...@arcor.de wrote: Hello, I try to boot Windows 8 (x86) over ISCSI on a system with a Realtek RTL 8111C onboard nic. The first setup step with loading the boot.wim with wimboot works fine. The Realtek nic is installed in the PE and the Windows setup write the os image to the iscsi target. After the first reboot, the Windows boot hangs and displays the INACCESABLE_BOOT_DEVICE error after some time. Is there anything I can try to debug or resolve the INACCESABLE_BOOT_DEVICE boot error? Other combinations I successfully tested: - Use a Intel Pro/1000 PT QP Nic instead of the onboard Realtek for the Windows 8 boot. - Use Windows 7 with the onboard Realtek nic. Regards, Marc Hammer it would be useful to see your .ipxe configuration for doing the boot from iSCSI is the client connecting to the iSCSI LUN ? ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
Re: [ipxe-devel] Windows 8 ISCSI Boot
Am 30.05.2013 16:08, schrieb shouldbe q931: On Thu, May 30, 2013 at 3:02 PM, Marc Hammer marcham...@arcor.de wrote: Hello, I try to boot Windows 8 (x86) over ISCSI on a system with a Realtek RTL 8111C onboard nic. The first setup step with loading the boot.wim with wimboot works fine. The Realtek nic is installed in the PE and the Windows setup write the os image to the iscsi target. After the first reboot, the Windows boot hangs and displays the INACCESABLE_BOOT_DEVICE error after some time. Is there anything I can try to debug or resolve the INACCESABLE_BOOT_DEVICE boot error? Other combinations I successfully tested: - Use a Intel Pro/1000 PT QP Nic instead of the onboard Realtek for the Windows 8 boot. - Use Windows 7 with the onboard Realtek nic. Regards, Marc Hammer it would be useful to see your .ipxe configuration for doing the boot from iSCSI is the client connecting to the iSCSI LUN ? iPXE configuration: #!ipxe set net0/gateway 192.168.178.5 sanboot iscsi:192.168.178.5:::0:BootServer:0024 I set the gateway to the iscsi target because the client and the server are on the same subnet and the iSCSI Boot Initiator creates a static route to the gateway (http://support.microsoft.com/kb/960104). iPXE is connecting to the iSCSI LUN but I can not see any session from Windows itself # cat /proc/net/iet/session tid:1 name:BootServer:0024 sid:53564314872 initiator:iqn.2010-04.org.ipxe:----00241d53ff5a cid:0 ip:192.168.178.136 state:active hd:none dd:none I only see the Windows 8 boot logo and after some time a INACCESABLE_BOOT_DEVICE error screen. Regards, Marc Hammer ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
Re: [ipxe-devel] Windows 8 ISCSI Boot
On May 30, 2013, at 10:34 AM, Marc Hammer marcham...@arcor.de wrote: Am 30.05.2013 16:08, schrieb shouldbe q931: On Thu, May 30, 2013 at 3:02 PM, Marc Hammer marcham...@arcor.de wrote: Hello, I try to boot Windows 8 (x86) over ISCSI on a system with a Realtek RTL 8111C onboard nic. The first setup step with loading the boot.wim with wimboot works fine. The Realtek nic is installed in the PE and the Windows setup write the os image to the iscsi target. After the first reboot, the Windows boot hangs and displays the INACCESABLE_BOOT_DEVICE error after some time. Is there anything I can try to debug or resolve the INACCESABLE_BOOT_DEVICE boot error? Other combinations I successfully tested: - Use a Intel Pro/1000 PT QP Nic instead of the onboard Realtek for the Windows 8 boot. - Use Windows 7 with the onboard Realtek nic. Regards, Marc Hammer it would be useful to see your .ipxe configuration for doing the boot from iSCSI is the client connecting to the iSCSI LUN ? iPXE configuration: #!ipxe set net0/gateway 192.168.178.5 sanboot iscsi:192.168.178.5:::0:BootServer:0024 I set the gateway to the iscsi target because the client and the server are on the same subnet and the iSCSI Boot Initiator creates a static route to the gateway (http://support.microsoft.com/kb/960104). Hello Marc, You might be on to something here... Try clearing the value of net0/gateway instead. That's what I do as my workaround for that goofy static route stuff, then access the net with a second NIC. -Andrew iPXE is connecting to the iSCSI LUN but I can not see any session from Windows itself # cat /proc/net/iet/session tid:1 name:BootServer:0024 sid:53564314872 initiator:iqn.2010-04.org.ipxe:----00241d53ff5a cid:0 ip:192.168.178.136 state:active hd:none dd:none I only see the Windows 8 boot logo and after some time a INACCESABLE_BOOT_DEVICE error screen. Regards, Marc Hammer ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
Re: [ipxe-devel] Windows 8 ISCSI Boot
Am 30.05.2013 19:32, schrieb Andrew Bobulsky: iPXE configuration: #!ipxe set net0/gateway 192.168.178.5 sanboot iscsi:192.168.178.5:::0:BootServer:0024 I set the gateway to the iscsi target because the client and the server are on the same subnet and the iSCSI Boot Initiator creates a static route to the gateway (http://support.microsoft.com/kb/960104). Hello Marc, You might be on to something here... Try clearing the value of net0/gateway instead. That's what I do as my workaround for that goofy static route stuff, then access the net with a second NIC. -Andrew I changed the iPXE configuration to the following: #!ipxe clear net0/gateway sanboot iscsi:192.168.178.5:::0:BootServer:0024 I still get the INACCESABLE_BOOT_DEVICE boot error. If I try to reinstall Windows I see that the gateway is not reset in the PE setup step, so Windows PE could not access the LUN. This was working with the previous setting. Is there anything other I can try ? Any idea if I can activate some kind of logging to debug the boot process? Regards, Marc Hammer ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
