Hi, I've got 2 Hyper-V guests; both running the current CoreOS server test install (iso as of latest), and i'm trying to iSCSI boot one from the other (on a CoreOS x86-64 host)
When I try to use the sanboot command on the client I do: sanboot iscsi:172.18.14.178::::iqn.2013-15.com.example:cephrbd.target0 Could not open SAN device: Input/output error (http://ipxe.org/1d704439). Both VMs have 1 net interfaces in 172.18.14.x; the server is 172.18.14.178. I've already dhcp'd OK, if I change any part of the iSCSI device name it gives a device not found error, so it's talking to the server. The 1st one ('master1') is running the 'tgt' iSCSI target stack, and serves a single LUN; here is it's create command: tgtadm --lld iscsi --mode target --op new --tid 1 --targetname iqn.2013-15.com.example:cephtgt.target0 tgtadm --lld iscsi --mode logicalunit --op new --tid 1 --lun 1 --backing-store iscsi-image --bstype rbd tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL and server is started with tgtd -f in it's upstart script. The tgt is happy speaking to Microsoft iSCSI Software Initiator, I can bring up a 3rd VM and it get it to mount the iSCSI device and it can see it. any suggestions are welcome. Jim --
_______________________________________________ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo/ipxe-devel
