Cannot connect to network on virt manager

[ImGGAAVVIINN]

I am unable to get network working when running the VM in virt manager, the mac will always show a no internet icon

I have tried:

• Changing the device model to e1000-82545em or vmxnet3
• Changing Network source to bridge mode

Guest: macOS Sequoia

Host:

• OS: Ubuntu
• Version 22.04 LTS
• ip a:

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether e8:9c:25:e1:5e:0b brd ff:ff:ff:ff:ff:ff
    altname enp8s0
    inet 192.168.8.125/24 brd 192.168.8.255 scope global dynamic noprefixroute eno1
       valid_lft 68890sec preferred_lft 68890sec
    inet6 fdec:3cbb:ac86:a100:e57d:7fb3:9d58:6a44/64 scope global temporary dynamic 
       valid_lft 6852sec preferred_lft 3252sec
    inet6 fdec:3cbb:ac86:a100:4a3:5027:49c2:8a12/64 scope global temporary deprecated dynamic 
       valid_lft 6852sec preferred_lft 0sec
    inet6 fdec:3cbb:ac86:a100:d2ad:fd61:9973:ffc4/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 6852sec preferred_lft 3252sec
    inet6 fe80::94c5:ab05:12f4:e01c/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: wlp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether a8:41:f4:dd:5b:9c brd ff:ff:ff:ff:ff:ff
    inet 192.168.31.179/24 brd 192.168.31.255 scope global dynamic noprefixroute wlp9s0
       valid_lft 40602sec preferred_lft 40602sec
    inet6 fe80::6302:611e:2edd:1e11/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:e2:b3:72 brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.1/24 brd 192.168.100.255 scope global virbr0
       valid_lft forever preferred_lft forever```

[dosubot]

Hi @ImGGAAVVIINN! I'm Dosu and I’m helping the OneClick-macOS-Simple-KVM team.

The default network setup in OneClick-macOS-Simple-KVM uses QEMU's user-mode networking (-netdev user,id=net0) with the vmxnet3 device model, which is simple but does not use bridge mode and may not provide full network functionality or compatibility with all guest OSes, especially macOS Sequoia. The libvirt XML template in the project uses NAT networking, not a bridge, and there is no built-in support or documentation for bridge mode in this setup. If you switch to bridge mode in Virt Manager, you must ensure your host's bridge is correctly configured and that your user has permission to use it. The virbr0 interface on your host is down, which means any VM using it as a bridge will not have connectivity.

For troubleshooting:

• Try switching the network source in Virt Manager to "NAT" or "default" network instead of bridge mode, as this matches the tested configuration in the project.
• If you want to use bridge mode, make sure your bridge interface (e.g., br0) is up and properly configured, and that your physical interface (like eno1) is enslaved to the bridge. The default virbr0 is a NAT network and is down on your system, so it will not work for bridging.
• Stick with the vmxnet3 device model, as this is what the project uses by default.
• If macOS Sequoia is detecting the VM and blocking some functionality, you may need to modify your OpenCore config.plist to disable the hv_vmm_present flag, as discussed in this issue.

There are no existing issues or discussions in the repository directly about Virt Manager network problems, but the project is designed for simplicity and defaults to NAT/user-mode networking, not bridging. If you need full bridge mode, you will have to configure it manually on your host and in Virt Manager, which is outside the scope of the default project setup.

To reply, just mention my name @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[BrattishRat384]

Hey there,
Have you tried running
Sudo virsh network start default
Or something along those lines
Some times virsh doesn't start the network by default, try that and see how you go.

Thanks.

[ImGGAAVVIINN]

Yes, can confirm that the problem still persist even when the virtual network is running

virsh net-list

 Name      State    Autostart   Persistent
--------------------------------------------
 network   active   yes         yes

Net work still won't connect