Cause. A network adapter of the virtual machine is connected to a network that has no host-bridge backing on the host, so the adapter cannot be attached when the virtual machine starts.
Remedy.
Give the network a host-bridge backing: kyvernon network update <id> --body-file <file>.
Or connect the network adapter to a network that has one, or remove the adapter: Edit settings.
Power the virtual machine on again.
error.network.proxy_uplink
Text in the console
Proxy mode needs an Open vSwitch bridge and the name of the uplink interface (for example eno1).
Meaning for API clients
Proxy mode needs an Open vSwitch bridge and the name of the uplink interface.
the request field that holds the rejected setting, here backing.uplink.
Cause. A host-bridge network was set to proxy mode, which needs an ordinary Open vSwitch bridge and the name of the uplink interface. The interface is missing, has the name of the bridge itself, or is not a valid interface name. A quarantine bridge or a Linux bridge cannot use proxy mode either.
Remedy.
Name the uplink interface of the host, for example eno1, and use an Open vSwitch bridge.
Save the network again: kyvernon network update <id> --body-file <file>.
When the provider does not need proxy mode, choose the bridged mode instead.
error.network.promiscuous_unsupported
Text in the console
Promiscuous mode is not available on host-bridge networks. Use a mirror session instead.
Meaning for API clients
Promiscuous mode is not realised by the host bridge; use a mirror session.
the request field, here backing.policy.security.allow_promiscuous.
Cause. The security policy of a port group allows promiscuous mode. The host bridge does not deliver the traffic of other ports to a virtual machine, so the setting cannot be honoured and is refused rather than ignored.
Remedy.
Leave promiscuous mode off (allow_promiscuousfalse or absent) in the policy of the network.
To see the traffic of other virtual machines, for example for an intrusion detection system, use a mirror session instead.
error.network.shaping_invalid
Text in the console
The traffic shaping value {field} is missing, negative or below the average bandwidth.
Meaning for API clients
The traffic shaping values are incomplete, negative or out of order (field names the value).
the request field with the wrong value, for example backing.policy.shaping.peak_bandwidth.
Cause. The traffic shaping of a port group is on, but a value is missing or does not fit: the average bandwidth is absent or below 1000 bit/s, the peak bandwidth is below the average bandwidth, or a value is negative.
Remedy.
Give the average bandwidth in bit/s, and a peak bandwidth that is at least as high.
Save the network again: kyvernon network update <id> --body-file <file>.
To stop shaping, set enabled to false or clear the policy with "policy": null.
error.network.teaming_invalid
Text in the console
The NIC teaming value {field} is not valid: an unknown policy, an invalid interface name, or a NIC listed twice.
Meaning for API clients
The NIC teaming policy is unknown, or a NIC name is invalid or listed twice.