10.4.3. Attaching a virtual machine to secondary user-defined networks by using the CLI

Procedure

1. Edit the VirtualMachine manifest to add the CUDN interface details, as in the following example:

   apiVersion: kubevirt.io/v1
   kind: VirtualMachine
   metadata:
     name: example-vm
     namespace: red
   spec:
     template:
       spec:
         domain:
           devices:
             interfaces:
               - name: secondary_localnet
                 bridge: {}
           machine:
             type: ""
           resources:
             requests:
               memory: 2048M
         networks:
         - name: secondary_localnet
           multus:
             networkName: <localnet_cudn_name>

   • metadata.namespace specifies the namespace in which the VM is located. This value must match a namespace that is associated with the secondary CUDN.
   • spec.template.spec.domain.devices.interfaces.name specifies the name of the secondary user-defined network interface.
   • spec.template.spec.networks.name specifies the name of the network. This value must match the value of the spec.template.spec.domain.devices.interfaces.name field.
   • spec.template.spec.networks.multus.networkName specifies the name of the localnet ClusterUserDefinedNetwork object that you previously created.

2. Apply the VirtualMachine manifest by running the following command:

   $ oc apply -f <filename>.yaml

   where:

   <filename>

   Specifies the name of your VirtualMachine manifest YAML file.

   注記

   When running OpenShift Virtualization on IBM Z®, be aware that certain network interfaces, such as OSA, RoCE, and HiperSockets, only forward network traffic to devices that are registered with the respective interface. As a result, any traffic that is destined for unregistered devices is not forwarded.