Sorry, please ignore my suggestion. Now I realize that you actually want to avoid re-ordering.

On Wed, Jun 7, 2017 at 2:05 PM, Yevgeny Zaspitsky <yzaspits@redhat.com> wrote:
You can activate reordering by using oVirt REST API. Sending POST request to http://${engine_address}/vms/${vm_id}/reordermacaddresses URL should do the job.
Please note that it would reorder all vnics of the VM that PCI address wasn't assigned to them, in other words the VM wasn't run since the vnic was added to it.

On Thu, Jun 1, 2017 at 2:57 PM, Nathanaël Blanchet <blanchet@abes.fr> wrote:



Le 01/06/2017 à 12:39, Dan Kenigsberg a écrit :
On Wed, May 31, 2017 at 8:23 PM, Nathanaël Blanchet <blanchet@abes.fr> wrote:
Hi all,

I added a new nic on all my vms, but the MAC address pool was too small. So
I extended it from 00:1a:4a:22:1f:00 to 00:1a:4a:22:1f:ff =>
00:1a:4a:22:1e:00 to 00:1a:4a:22:1f:ff.

It was okay but when rebooting some vms, nics are interverted and I couldn't
join my vm on ip!

I noticed nics were ordered now from the smallest MAC address to the
greatest one, so the last plugged nic from the new pool was now the first in
the vm, and all nics were moved at the bottom.

Is it an expected behaviour?
No. As far as I recall, and Yevgeny can add more details, reordering
of vNICs happens only when allocating multiple nics in the initial
definition of a VM; but not on plugging of a nic to an existing VM.

Which version of ovirt-engine do you use?
oVirt Engine Version: 4.1.2.2-1.el7.centos

    

-- 
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5 	
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanchet@abes.fr