The second phase of RFE #1163365 (https://bugzilla.redhat.com/show_bug.cgi?id=1163365). Upon discovering a problematic configuration (missing IP boot protocol) on a NIC with non-VM roles, the host should become non-operational. That is after in v3.6 we warn the user that such configuration is deprecated and won't be allowed in future version.
What about FCoE?
If an interface cannot support IP configuration it cannot be used for a role bearing network attachement. AFAIK all roles are implemented over IP stack, and the RFE is about to make sure that a role bearing network would function according to the role it bears.
(In reply to Yevgeny Zaspitsky from comment #2) > If an interface cannot support IP configuration it cannot be used for a role > bearing network attachement. > AFAIK all roles are implemented over IP stack, and the RFE is about to make > sure that a role bearing network would function according to the role it > bears. - I'm not sure this is the case with FCoE - honestly don't know - but we need to find out. - I'm not sure this is the case with IB - if we (ever) wish to support migration over IB (RDMA, not IPoIB - see http://wiki.qemu.org/Features/RDMALiveMigration ).
Closing old RFEs, please reopen if still needed. Patches are always welcomed.