Please fill in the following information:

Issue description: Feedback from bmerot@redhat.com :

: In chapter 4.3, the name of the new bridge interface defined in the VirtualMachine CR is "nic-0". But later in the same chapter, the cloud-init example for the same VirtualMachine CR configures a network interface named eth1. I believe the names should be the same throughout the example.

"In the examples given to had a secondary interface attached to a host
bridge device to access the LAN outside of the OpenShift OVN Pod network,
this two YAML snippets are present:

apiVersion: kubevirt.io/v1
kind: VirtualMachine
metadata:
name: rhel8-vm
spec:
template:
spec:
domain:
devices:
interfaces:

• • masquerade: {}*
    name: default
  • bridge: {}*
    name: nic-0 [image: 1]
    model: virtio
    *...output omitted...*
    networks:
  • name: default*
    pod: {}
  • name: nic-0 [image: 2]*
    multus:
    networkName: br1-bridge-network [image: 3]...output omitted...**

and to assign it a static IP address instead of using DHCP:

kind: VirtualMachine
spec:...output omitted...**
volumes:

• • cloudInitNoCloud:*
    networkData: |
    version: 2
    ethernets:
    eth1: [image: 1]
    addresses:
  • 192.168.51.150/24*

The drawing in this chapter uses the name "net1" for the secondary
interface on the VM's Pod that is attached to a bridge device. So either
the YAML CR should use "net1" instead of "nic-0".

Benjamin Merot , RHCE

Senior Account Solutions Architect "

Steps to reproduce:

Workaround:

Expected result: