Hello, I'm trying to set up Windows 8.1 diskless PC environment by using iPXE, ietd on Ubuntu 12.04. Everything works fine except slow speed at Windows logo display stage.
Boot speed after pxe stage is about 1 minute (not that bad, I know), but I figured out that communication between ipxe and iscsi target takes too long. Once if Windows iscsi initiator takes over, it will take only a few secs to boot up. So I think I can make it very fast if I can reduce ipxe<->target communication time.
Below is debug logs from DEBUG=iscsi,scsi.
Code:
192.168.0.109 ipxe: Waiting for link-up on net0...... ok
192.168.0.109 ipxe: Configuring (net0 c0:3f:d5:fd:14:0b)...... ok
pctg ipxe: iSCSI 0x1f5b4 initiator iqn.1991-05.com.abc:daniel-win8
pctg ipxe: iSCSI 0x1f5b4 target 192.168.0.23 iqn.2003-01.org.linux-iscsi.dkim-dev-ubuntu.x8664:sn.80300f64002e
pctg ipxe: iSCSI 0x1f5b4 entering security negotiation
pctg ipxe: SCSI 0x1fa24 created for LUN 0000-0000-0000-0000
pctg ipxe: iSCSI 0x1f5b4 ignoring TargetPortalGroupTag=1
pctg ipxe: iSCSI 0x1f5b4 handling AuthMethod=None
pctg ipxe: iSCSI 0x1f5b4 entering operational negotiation
pctg ipxe: iSCSI 0x1f5b4 ignoring HeaderDigest=None
pctg ipxe: iSCSI 0x1f5b4 ignoring DataDigest=None
pctg ipxe: iSCSI 0x1f5b4 ignoring MaxConnections=1
pctg ipxe: iSCSI 0x1f5b4 ignoring InitialR2T=Yes
pctg ipxe: iSCSI 0x1f5b4 ignoring ImmediateData=No
pctg ipxe: iSCSI 0x1f5b4 ignoring MaxBurstLength=262144
pctg ipxe: iSCSI 0x1f5b4 ignoring DefaultTime2Wait=2
pctg ipxe: iSCSI 0x1f5b4 ignoring DefaultTime2Retain=0
pctg ipxe: iSCSI 0x1f5b4 ignoring MaxOutstandingR2T=1
pctg ipxe: iSCSI 0x1f5b4 ignoring DataPDUInOrder=Yes
pctg ipxe: iSCSI 0x1f5b4 ignoring DataSequenceInOrder=Yes
pctg ipxe: iSCSI 0x1f5b4 ignoring ErrorRecoveryLevel=0
pctg ipxe: iSCSI 0x1f5b4 entering full feature phase
pctg ipxe: SCSI 0x1fa24 waiting for unit to become ready
pctg ipxe: SCSI 0x1fa24 tag 18ae0002 status 02 sense 70 key 00 additional 2900
pctg ipxe: SCSI 0x1fa24 tag 18ae0002 failed: Input/output error (http://ipxe.org/1d704039)
pctg ipxe: SCSI 0x1fa24 tag 18ae0002 retrying (retry 1)
pctg ipxe: SCSI 0x1fa24 tag 18ae0002 is now tag 18ae0003
pctg ipxe: SCSI 0x1fa24 unit is ready
pctg ipxe: Registered SAN device 0x80
pctg ipxe: Booting from SAN device 0x80
pctg ipxe: iSCSI 0x1f5b4 start data out DataSN 0x0 len 0x200
pctg ipxe: iSCSI 0x1f5b4 start data out DataSN 0x0 len 0x200
pctg ipxe: iSCSI 0x1f5b4 start data out DataSN 0x0 len 0x200
pctg ipxe: iSCSI 0x1f5b4 start data out DataSN 0x0 len 0x200
pctg ipxe: iSCSI 0x1f5b4 start data out DataSN 0x0 len 0x200
pctg ipxe: iSCSI 0x1f5b4 start data out DataSN 0x0 len 0x200
pctg ipxe: iSCSI 0x1f5b4 start data out DataSN 0x0 len 0x200
pctg ipxe: iSCSI 0x1f5b4 start data out DataSN 0x0 len 0x200
pctg ipxe: iSCSI 0x1f5b4 start data out DataSN 0x0 len 0x200
pctg ipxe: iSCSI 0x1f5b4 start data out DataSN 0x0 len 0x200
pctg ipxe: iSCSI 0x1f5b4 start data out DataSN 0x0 len 0x200
pctg ipxe: iSCSI 0x1f5b4 start data out DataSN 0x0 len 0x200
pctg ipxe: iSCSI 0x1f5b4 start data out DataSN 0x0 len 0x200
pctg ipxe: iSCSI 0x1f5b4 start data out DataSN 0x0 len 0x200
I also dump packet from tcpdump and found 66 bytes packet frame is repeated and it causes boot delay at Windows logo stage.
Once if Windows iscsi initiator takes over, only a few secs to boot up as below.
Is there any way to reduce communication time between ipxe<->iscsi target?
Thanks in advance.