OVM 3 Generic Storage Plugin. Acess Group configuration causes server crash

Question

Our iSCSI management is currently entirely done manually at the servers console, because we still don't have a SAN Equallogic storage plugin.
At OVM Manager interface, what we thought being just useless in our case (SAN Access Group), is the actual iSCSI connection (and disconnection..) management for servers.
Following the upgrade to 3.2.1, setting up the SAN did nothing more than what we do manually. But undoing part of it caused the crash.
All over OVM Manager, any operation/setup that could impact running VMs is denied... Except there, at the real root of everything.
Removing a iSCSI initiator from that panel disconnects abruptly the iSCSI disk, !!!! without warning !!!!.
Then, after the 60s timetout, the physical server reboots.
It is still not clear if we get a benefice to setup that "Access Group" of the SAN or not. At least, once setup, we know that we'd better keep it...

Answer 1

Updating OVM 3 host to use "brbond0" vs "xend" managed bridge to allow direct hosting of OVM Manager VM.
Update "ifcfg-bond0",
[root@ovm322 ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond0
DEVICE=bond0
BONDING_OPTS="mode=1 miimon=250 use_carrier=1 updelay=500 downdelay=500 primary=eth0"
ONBOOT=yes
BRIDGE=brbond0
Create "ifcfg-brbond0",
[root@ovm322 ~]# cat /etc/sysconfig/network-scripts/ifcfg-brbond0
DEVICE=brbond0
BOOTPROTO=bridge
ONBOOT=yes
IPADDR=A.B.C.D                                                       # IP address of ovm322
NETMASK=255.255.254.0
NETWORK=A.B.C.0
GATEWAY=A.B.C.1
Update  "/etc/xen/xend-config.sxp",
# Enable network-bridge, JAP 20120618
# Disable network-bridge, JAP 20131223
#(network-script network-bridge)
Update  "vif" for OVM Manager 3 "vm.cfg",
[root@ovm322 ~]# grep ^vif /etc/xen/auto/ovm322-m
vif = ['type=netfront, bridge=brbond0']