So we know pytarget can achieve the same as other known to work iscsi targets.
Windows 7 working from cloned system. I've not been able to install Windows 7 to a target - something that has been possible with other Target software I have used. On my most recent test I noticed the following error (displayed multiple times - in the pytarget console) -
WARNING: detect iscsi pdu data invaild, reject request
Windows 8.1 (Update 1) installed successfully to a Target. Cloned system not tested yet.
Windows 10 failed to install to a Target on my test system, however it also failed to install using a different Target software (Kernsafe). Error message during Windows Setup - "Windows installation cannot continue because a required driver could not be installed.
Windows 10 working when cloned to a target (NOTE
- GUI used
). Running iscsicli in the SAN Booted OS -
Microsoft iSCSI Initiator Version 10.0 Build 14393
Error getting node name: The Microsoft iSCSI initiator service is not running. Please start the service and retry.
This is similar to Windows 8.1. As I mentioned in post #25
, running iscsicli in SAN Booted Windows 8.1 resulted in -
Microsoft iSCSI Initiator Version 6.3 Build 9600
Error getting node name: The Microsoft iSCSI initiator service has not been star
Windows 7 output from running iscsicli in SAN Booted Windows 7 (see post #28
Microsoft iSCSI Initiator Version 6.1 Build 7601
[iqn.x200] Enter command or ^C to exit
Not sure if this is a factor in installing Windows 7 to a target. Other factors may be the range of other iSCSI options not being configured (or perhaps incorrectly configured). The pytarget documentation mentions the following options -
<item key="MaxConnections" value="8" />
<item key="InitialR2T" value="Yes" />
<item key="ImmediateData" value="Yes" />
<item key="FirstBurstLength" value="65536" />
<item key="MaxBurstLength" value="262144" />
<item key="DefaultTime2Wait" value="2" />
<item key="DefaultTime2Retain" value="20" />
<item key="MaxOutstandingR2T" value="16" />
<item key="DataPDUInOrder" value="Yes" />
<item key="DataSequenceInOrder" value="Yes" />
<item key="ErrorRecoveryLevel" value="2" />
<item key="MaxRecvDataSegmentLength" value="65536" />
...Pytarget is free, opensource and portable : this goes straight away on my top of the list of "must have softwares" !...
- I agree.
...I am still failing to clone a windows 7 and will therefore wait for your updated gui to restart from scratch...
Not sure what you mean by "...will therefore wait for your updated gui to restart from scratch...
I'm assuming a typo - I certainly won't be updating any gui! Don't let my account details fool you - I'm no developer!!!!
...Good to know the new GUI is working fine (I fixed what I suspected to be a possible bug after your previous report). If you have other suggestions/requests, let me know...
Firstly, thanks for the fix
Secondly, you may regret asking for suggestions/requests!
The first thing that springs to mind is reading the existing config and parsing any target details (including "Disk Image" and "Initiator IQN") to the GUI to avoid having to manually browse for the disk image if it doesn't need to be changed. Also, I noticed that the disk image will not be used if it's manually entered in the "Disk Image" field in the GUI. Attempted this I received the following error -
WARNING: open device FAILED
WARNING: get file() status FAILED.
When using the same settings in the GUI and using the Browse button to select the disk image it worked fine.
At the moment only *.img files can be selected. Can you add an option to open any file type (equivalant to "All Files" option in Notepad) - or add .vhd and .ima?
Can't think of anything else at the moment.
I would like to say a big thank you for all of your hard work on this and your other projects.