mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2025-02-08 09:57:26 +03:00
NEWS: Document recent VLAN ID improvement
After previous commits, the set of NICs that work well with Libvirt was extended. Document this change. Signed-off-by: Dmitrii Shcherbakov <dmitrii.shcherbakov@canonical.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
This commit is contained in:
parent
09cdd16a9b
commit
bf36dcb2a6
14
NEWS.rst
14
NEWS.rst
@ -34,6 +34,20 @@ v8.1.0 (unreleased)
|
|||||||
to parse sysconfig files, in case they are created by the admin and filled
|
to parse sysconfig files, in case they are created by the admin and filled
|
||||||
with the desired key=value pairs.
|
with the desired key=value pairs.
|
||||||
|
|
||||||
|
* virnetdev: Ignore EPERM on implicit clearing of VF VLAN ID
|
||||||
|
|
||||||
|
Libvirt will now ignore EPERM errors on attempts to implicitly clear a
|
||||||
|
VLAN ID (when a VLAN is not explicitly provided via an interface XML
|
||||||
|
using a 0 or a non-zero value) as SmartNIC DPUs do not expose VLAN
|
||||||
|
programming capabilities to the hypervisor host. This allows Libvirt
|
||||||
|
clients to avoid specifying a VLAN and expect VF configuration to work
|
||||||
|
since Libvirt tries to clear a VLAN in the same operation
|
||||||
|
as setting a MAC address for VIR_DOMAIN_NET_TYPE_HOSTDEV devices which
|
||||||
|
is now split into two distinct operations. EPERM errors received while
|
||||||
|
trying to program a non-zero VLAN ID or explicitly program a VLAN ID 0
|
||||||
|
will still cause errors as before so there is no change in behavior
|
||||||
|
in those cases.
|
||||||
|
|
||||||
* **Bug fixes**
|
* **Bug fixes**
|
||||||
|
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user