"What about the service console? Can it be on the same vswitch as vmotion+management?"
For vsphere 5 and esxi no service console and you can put mangement + vmotion and use separate VLAN, and if you have 4 nics for these it will be waste... so use 2 nics and use rest of the 2 nics for other... like FT
For NFS - the nics will be in Active/standby and this is same for mgmt/vmotion
for ISCSI - the nics will be in ACtive/unused
To your query - "
we maybe also want "virtual iscsi" so that a vm machine can
connect via iscsi initiator to a lun. What would you recommend? "
ISCSI in side the VM is not...a good idea..and if you want disk more than..2TB for a VM then you can go.. for that also.. you can create multiple 2TB VMDK and make a dynamic volume.. for linux any way you dont need...the iscsi in side the vm, the linux LVM just expands as you add more disks.
esxi it self has a very good.. and strong multipathing frame work.... but inside the guest..it is always more overhead. So i recommend just use ESXI iscsi.
"(Simple and redundant, speed is not top priority)" - in a long RUN you will realize the NFS/ISCSI needs more speed. So use jumbo FRAMES for ISCSI and NFS, and add more NICS for the NFS and ISCSI.
Apart from these... your setup is fine... you can proceed