Random MAC addresses are allocated to VM's vNICs, causing in-guest randomness Description of problem: When a VM with multiple vNICs is created, cloned or imported, its vNICs acquire random MAC addresses. This causes the guest OS to allocate interface names in an unpredictable manner, making it impossible for the guest to guess which network is an interface connected to. Version-Release number of selected component (if applicable): RHEV 2.2 and 3.Y How reproducible: Almost always (MAC addresses may happen to match vNIC entity names). More information: http://wiki.ovirt.org/Feature/Predictable_vNIC_Order
This patches handles the NIC ordering when creating or importing a VM, as follows: 1. When creating a VM from template a. If the template has PCI addresses, then sort the NICs according to that, allocating MAC addresses with the same ordering b. If the template doesn't contain PCI addresses, allocate MAC addresses with an ordering identical to the naming of the NICs 2. When creating a VM from snapshot a. Follow logic in 1a. b. If the snapshot doesn't contain PCI addresses, but it does contain the MAC addresses, allocate new MAC addresses with the same ordering as in the original snapshot c. If no PCI and no MAC addresses are available, order by the NIC name 3. When importing a VM - same as VM creation (but no template in this case, just the exported VM is the reference to compare to). In the add VM use-case, when the user the user adds more NICs in addition to the templated ones, we do the following ordering: 1. All templated NICs that have a PCI address are left as is. 2. All the remaining NICs (both from the template or new ones) are given MAC addresses with the same NIC name ordering.
oVirt 3.4.0 alpha has been released including the fix for this issue.
verified https://tcms.engineering.redhat.com/run/117231/?from_plan=12034
This is an automated message: moving to Closed CURRENT_RELEASE since oVirt 3.4.0 has been released.
After this one again https://bugzilla.redhat.com/show_bug.cgi?id=1108926