Ubuntu 24.04 LTS – libvirt default network inactive and VMs have no connectivity – Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Guest VMs boot but cannot obtain DHCP lease or reach external networks.

Environment & Reproduction

Ubuntu 24.04 LTS with libvirt and qemu-kvm where default network was not autostarted.

Root Cause Analysis

libvirt network definition exists but bridge and dnsmasq components are not active.

Quick Triage

Run virsh net-list –all and systemctl status libvirtd to inspect network lifecycle state.

Step-by-Step Diagnosis

Review virsh net-dumpxml default and verify nftables forwarding rules for virbr0.

Solution – Primary Fix

Start and autostart default network using virsh net-start default and virsh net-autostart default.

Solution – Alternative Approaches

Create a custom bridge network if routed or VLAN-backed guest networking is required.

Verification & Acceptance Criteria

Guests receive IP addresses and pass outbound connectivity checks.

Rollback Plan

Destroy custom network and reactivate default NAT network if new topology fails.

Prevention & Hardening

Include virsh network autostart checks in post-provision validation tasks.

Related Errors & Cross-Refs

dnsmasq port conflicts and host firewall forwarding drops can cause similar failures.

Related tutorial: View the step-by-step tutorial for Ubuntu 24.04 LTS.

View all Ubuntu 24.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Libvirt networking documentation for Ubuntu environments.