Skip to navigationSkip to content
libvirtd docs
InteractiveCommands

Manual nav

Search `/` · tty `~` · g top · G bottom

Portal

  • Manual index
  • Interactive lab
  • Command explorer
Foundations5 sections
  • libvirtd Overview1
  • Host & Installation2
  • Architecture & Concepts6
  • Domains2
  • Domain XML2
Subsystems6 sections
  • Daemons3
  • virsh3
  • Virtual Networking5
  • Virtual Storage4
  • Virtualization Security3
  • Remote libvirt1
Operations5 sections
  • Migration2
  • Snapshots & Backup2
  • Performance3
  • Troubleshooting2
  • Reference2
mannetworkingReviewed August 8, 2026

Bridge design and host uplinks

A Linux bridge is a layer 2 switch in the host. The host address belongs on the bridge, while the physical interface becomes a port of that bridge. Inspect without changing Request path mental model For a libvirt managed

bridgenetworkmanageruplinkvlan

A Linux bridge is a layer-2 switch in the host. The host address belongs on the bridge, while the physical interface becomes a port of that bridge.

Inspect without changing

BASH
ip -br link
ip -br address
bridge link
bridge vlan show
nmcli -f NAME,TYPE,DEVICE,STATE connection show

Request path mental model

For a libvirt-managed guest interface, reason from the management layer toward the workload edge:

TEXT
libvirt control plane
        |
        v
host bridge / uplink
        |
        v
guest network edge

The control plane defines and manages the guest interface relationship. The host bridge is the layer-2 switching handoff. The guest-facing interface is the workload edge of that path. Use the actual bridge name from the host when tracing a real system.

NetworkManager pattern

BASH
nmcli connection add type bridge ifname br0 con-name br0
nmcli connection add type ethernet ifname eno1 master br0 con-name br0-port-eno1

Move the host IP configuration to br0 before activating the new topology. Remote changes can sever management connectivity; use console access, a maintenance window, and an explicit rollback connection profile.

Guest attachment proof

BASH
virsh domiflist guest01
ip link show master br0
bridge fdb show br br0

Do not run host DHCP on a bridge when the upstream network already owns address assignment unless the segments are intentionally isolated.

Field fragment B / 3

A buried recovery channel is watching for knowledge gathered from the manual. This fragment is not an answer to any drill; it proves you reached and read the right subsystem.

Related

  • DHCP, DNS, and libvirt virtual networks
  • Libvirt network modes
  • Network debugging for guests

On this page

  • Inspect without changing
  • Request path mental model
  • NetworkManager pattern
  • Guest attachment proof