Hide Forgot
Version 3.6 introduced support for pinning a VM to multiple VMs, preserving the previous capability to pin to only one CPU. In 4.0 we should remove the old mechanism, as the new one is a super-set.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Note that this has been removed from version 4 of the API, but preserved in version 3.
Verified on rhevm-4.0.0.2-0.1.el7ev.noarch Update VM placement policy under v3: <vm> <placement_policy> <host id="d4579633-f6a0-4e20-9e56-e5e58b403f4c"/> </placement_policy> </vm> PASS v4: <vm> <placement_policy> <host id="d4579633-f6a0-4e20-9e56-e5e58b403f4c"/> </placement_policy> </vm> FAILED
oVirt 4.0.0 has been released, closing current release.