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
wrote:
> You can activate reordering by using oVirt REST API. Sending POST request
> to http://${engine_address}/vms/${vm_id}/reordermacaddresses URL s
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 vn
Le 01/06/2017 à 12:39, Dan Kenigsberg a écrit :
On Wed, May 31, 2017 at 8:23 PM, Nathanaël Blanchet 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.
On Wed, May 31, 2017 at 8:23 PM, Nathanaël Blanchet 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,
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
5 matches
Mail list logo