Perhaps it's more of a Foreman/API limitation.
In Foreman I provision two interfaces, that in the Foreman UI at least, have an
ordering. Sometimes when they are provisioned in oVirt the "second" interface
has a lower MAC than the "first" interface and so the ordering in Foreman is
different
Hi,
Do I understand it correctly that:
-your OS uses PCI addresses to order NICSs?
-PCI addresses of NICs are in fact non-consistent between VMs?
So you boot VM1 (with NICs vNIC1 and vNIC2) and VM2 (vNIC3 and vNIC4) with same
order in eg. API (->GUI) and you
I don't create the VMs directly in the UI but use the API with Foreman. If I
change the MACs on the NICs I have to go back and update Foreman as well.
My workaround today is unplug the NIC I want to be second, briefly power-up the
VM so the "first" NIC gets assigned a PCI address, shutdown
I think it depends on the mac addresses.
If you see that the MAC addresses are not sequential, delete the NICs and
recreate them in the order you want them to be
it world for us
Guillaume Pavese
Ingénieur Système et Réseau
Interactiv-Group
On Wed, May 24, 2023 at 1:46 AM Alan G wrote:
> Is
It's IBM Spectrum Scale formerly known as GPFS. the limit for files or
filesystems are way beyond any limits within the linux vm so that is definatly
not an issue from the GPFS filesystem.
The disks are formatted as xfs within the VM so that limit should be 500TiB
right?
the funny thing is
5 matches
Mail list logo
