Posted this question to the General/Using VirtualBox forum at virtualbox.org, but it didn't elicit any replies so I thought I'd ask here:
Using the old iscsitgt method, getting VB to use multiple ISCSI targets worked pretty well. But iscsitgt has been obsoleted by COMSTAR, which allows multiple LUNs per target. Is there a way to get VB to use specific LUNs in this mode? By default it always seems to use the lowest LUN. Trying to set up VB 3.0.8 on AMD64/Fedora C10 to boot three ISCSI disks (ZFS, NTFS, EXT4) exported from a ZFS pool on Solaris SXCE snv125. Without using Target Groups to effectively force COMSTAR into using a single LUN per target, AFAICS there doesn't seem to be a way to do this, but setting up tgs seems so complicated for such a simple task. The alternative of actually mounting the disks and using them as raw volumes is undoubtedly discouraged :-). A related question: iscsitgt doesn't seem to stay disabled, at least after a reboot. The shareiscsi attribute is still set to on for the above mentioned targets. Should this be set off if one is using COMSTAR? Not sure if this is the right forum to ask this, but when a ZFS rpool uses an ISCSI disk itself hosted on a ZFS mirrored pool, what risk is there if wcd=true and the root pool is used only for the os image (all data at risk is mounted via NFS)? Without wcd=true, booting from and paging to the ISCSI rpool is painfully slow. Same applies to NTFS and EXT4 - used only for the os-images - well, they would be if and when the multiple LUNs per target question is resolved :-). In other words, is there any likelihood of being unable to boot from any of these after a (rare) crash of the ZFS host with wcd=true? Presumably the risk is low for a read- mostly file system (other than swap and /var (or equivalent)). Thanks _______________________________________________ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
