This patch http://gerrit.ovirt.org/#/c/35782/ broke one of automation tests
Also it's not good idea to cancel cpu pinning validation, because now if you enter incorrect pinning information and run vm, vm will failed and you will receive libvirt error in vdsm log, that not desire behavior at all.

simple fix is MODIFIED in 3.5.z (ovirt-3.5 branch)

Due to the fundamental differences in the various architectures, we need to error on allowing an admin to use a good configuration.  For this purpose, I am favoring passing through invalid configurations to libvirt vs. blocking potentially good configurations from running at all.

(reply to comment #9):
Added this RFE:
bug 1184890 - "[RFE] Expand cpu pinning error messages."

Verified on rhevm-3.5.1-0.1.el6ev.noarch
Run vm with pinning 0#152 success on host with next cpu topology:
Architecture:          ppc64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Big Endian
CPU(s):                160
On-line CPU(s) list:   0,8,16,24,32,40,48,56,64,72,80,88,96,104,112,120,128,136,144,152
Off-line CPU(s) list:  1-7,9-15,17-23,25-31,33-39,41-47,49-55,57-63,65-71,73-79,81-87,89-95,97-103,105-111,113-119,121-127,129-135,137-143,145-151,153-159
Thread(s) per core:    1
Core(s) per socket:    5
Socket(s):             4
NUMA node(s):          4
Model:                 8247-22L
CPU max MHz:           3690.0000
CPU min MHz:           2061.0000
L1d cache:             64K
L1i cache:             32K
L2 cache:              512K
L3 cache:              8192K
NUMA node0 CPU(s):     0,8,16,24,32
NUMA node1 CPU(s):     40,48,56,64,72

If this bug requires doc text for errata release, please provide draft text in the doc text field in the following format:

Cause:
Consequence:
Fix:
Result:

The documentation team will review, edit, and approve the text.

If this bug does not require doc text, please set the 'requires_doc_text' flag to -.

Setting the doc text flag to - as did not hear back on the need info.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0888.html