Comment 8 for bug 838809

Successfully reproduced here on kvm.

Initial testing shows that the open-iscsi init script seems to be the cause of the disconnect and input/output errors.
Removing it from the boot sequence lets me boot and get a shell without storage related errors.

I'm not too familiar with iscsi so I'll now have to dig a bit into open-iscsi and see exactly what it's trying to do at boot time.
As iscsi is already in use for the root device, my hope would be that it would keep it as it's an only initialize any other lun you may need.

Would be great if you could confirm that disabled open-iscsi from your target systems doesn't give you any error and that the system behaves as it should (it seems to be taking quite a bit of time to boot here, no idea if that's normal for iscsi boot).