|
|
Log in / Subscribe / Register

Libvirt v11.0.0 released

Version 11.0.0 of the libvirt virtualization API has been released. Notable changes in this release include the ability to export virtiofs filesystems in read-only mode, the addition of support for vlan tagging and trunking of network interfaces with the network, qemu, and lxc drivers, as well as a number of bug fixes.



to post comments

Vlan tagging

Posted Jan 16, 2025 17:17 UTC (Thu) by lindi (subscriber, #53135) [Link] (2 responses)

Vlan tagging sounds awesome! I guess this means I no longer need to create separate bridge devices for each VLAN?

Vlan tagging

Posted Jan 16, 2025 19:39 UTC (Thu) by bof (subscriber, #110741) [Link]

It is sure awesome.

I figured out a hacky way to do that 9 years ago, with a libvirt qemu startup hook doing the "bridge vlan add" dance behind the scenes while the VM starts up. Never looked back to the many-bridges times. Only had to touch the hack once in between, when the hook started to run as non-root, and I had to make it even more hacky by it kindly asking a socket activated root running thingie to do the actual dance on its behalf.

Looking forward to drop that shit in a year or two.

Vlan tagging

Posted Jan 18, 2025 18:32 UTC (Sat) by lsl (subscriber, #86508) [Link]

Note that Libvirt always supported this functionality for Open vSwitch bridges: https://libvirt.org/formatdomain.html#setting-vlan-tag-on...

I don't know whether the newly introduced Linux bridge support creates the necessary per-VLAN bridge devices for you. Probably not. I wouldn't be surprised if this feature required the VLAN-aware flavor of Linux bridges and didn't work at all with "traditional mode" Linux bridges (those that require a separate bridge device per VLAN).


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds